(from Pete Rivett) There are many properties (ownedAttributes with xmi:type=”uml:Property”) that do not have types assigned to them in the .emof file. That is mandatory.

Add type declarations to ownedAttributes for which there are no types declared

Change the UML URL at the top of the file from "https" to "http"

Add (as appropriate) type declarations for attributes in the normative emof file. Type declarations are of the style:
<type href="http://www.omg.org/spec/UML/20161101/PrimitiveTypes.xmi#Boolean"/>
and valid types are: Boolean, Integer, Real, String, UnlimitedNatural

Look for comments marked "<!-- FACE-23" to find changes
79 changes made in file

Short Version: The mofext tags at the end of the emof file are incorrect. The existing namespace prefix (nsPrefix) declarations need to be corrected and also need to be supplemented with additional mofext that include namespace URI (nsURI) declarations. Also consider changing the format of the FACE 3.0 namespaces to use the "#" separator, e.g. http://www.opengroup.us/face/3.0#platform

Details:
(from Pete Rivett) The URI property represents the identifier of the metamodel. This URI property, though it’s used by default for the interchange namespace, can be overridden to specify the namespace used for interchange. If you want to keep the opengroup website for the XML namespace, that is specified using the nsURI MOF tag I mentioned. It accompanies the tags you’re already using for the nsPrefix, which appear at the end of the file:, though they are currently wrong - the nsPrefix name must be itself prefixed org.omg.xmi. as shown below.

You’d need to declare a nsURI (namespace URI) for each nsPrefix (namespace prefix, you have 6), I just show the first, the others will just differ in the last line for the element and the value.

<!--- Original Text at end of emof file --->
<mofext:Tag xmlns:mofext="http://www.omg.org/spec/MOF/20131001" xmi:type="mofext:Tag"
xmi:id="_19_0_2_157603d2_1581698299484_395395_5638_nsPrefix" name="nsPrefix"
element="datamodel-platform" value="platform"/>

<!--- This is the recommended replacement text from Pete. --->
<mofext:Tag xmlns:mofext="http://www.omg.org/spec/MOF/20131001" xmi:type="mofext:Tag"
xmi:id="_19_0_2_157603d2_1581698299484_395395_5638_nsPrefix" name="org.omg.xmi.nsPrefix"
element="datamodel-platform" value="platform"/>

<mofext:Tag xmlns:mofext="http://www.omg.org/spec/MOF/20131001" xmi:type="mofext:Tag"
xmi:id="_19_0_2_157603d2_1581698299484_395395_5638_nsURI" name="org.omg.xmi.nsURI"
element="datamodel-platform" value=" http://www.opengroup.us/face/3.0/platform"/>

<!--- (you may instead want to use # as final separator) --->
value=" http://www.opengroup.us/face/3.0#platform"

Correct nsPrefix tags and add nsURI tags per Pete Rivett recommendation

Correct nsPrefix tags and add nsURI tags per Pete's recommendation.

No change to the URLs for the FACE namespaces, as this is a translation of the normative MOF 2.0 EMOF metamodel in the FACE Technical Standard, Edition 3.0 to MOF 2.5.1. Any changes in the resulting file format or contents due to the translation of the EMOF metamodel would violate the FACE Technical Standard.

Related to FACE-13. Modify the FACE Profile for UAF XMI to have the comments that reference the FACE technical standard use the same uniform string (FACE Technical Standard, Edition 3.0) as was applied to the standard document in proposal FACE-19.

Modify machine-readable FACE Profile for UAF for FACE Std Name Consistency

Change all descriptions that reference the "FACE 3.0 technical standard", "FACE 3.0 Technical Specification", or "FACE 3.0 standard" to instead refer to the "FACE Technical Standard, Edition 3.0"

(From Pete Rivette) Other Normative References Put the explanation about the 3.0 and 2.1 versions of the standard IN THE DOCUMENT where the two standards are listed as normative

Put explanation about both FACE versions 3.0 and 2.1 in Section 3.2

Added explanations about the reason for both the FACE Technical Standard editions 3.0 and 2.1 to be referenced into section 3.2 Other Normative References.

To find the modified text, see changes commented with FACE-12 markings in the attached file.

(From Pete Rivette) Version numbers are confusing. Clarify that FACE Profile for UAF 1.0 is a representation of the FACE Tech Standard 3.0

Add reference to FACE-UAF profile version and additional references to FACE tech std version

See attached file in proposal

In Scope / background section, explicitly state that the FACE Profile for UAF v1.0 specification defines a profile to express ... Technical Standard, Edition 3.0. In this and subsequent sections, amplify references to the FACE Technical Standard to read "FACE Technical Standard, Edition 3.0".

Adding an explicit edition indicator was appropriate for most, but not all references to the FACE Technical Standard. To find all the places where a change was made, look for comments marked "FACE-11".

Also changed some existing "FACE 3.0 Technical Standard" strings to "FACE Technical Standard, Edition 3.0" for consistency.

(From Pete Rivette) Use same naming conventions for FACE Technical Standard throughout document (some inconsistencies)

Use "FACE Technical Standard" uniformly

Ensure that all references to the "FACE 3.0 Technical Standard" are replaced with "FACE Technical Standard, Edition 3.0" and that all references to "FACE Technical Specification" are changed to reference "FACE Technical Standard".

This is a PERVASIVE change that includes changes to headings. Although not reflected in the attached file, the Table of Contents will also need to be regenerated. See attached file to view changes. To find all the locations that were changed, look for comments marked FACE-13. There were 33 changes in all.

(From Pete Rivette at June 22, 2020 AB review) FACE30metamodel.emof is incorrect for FACE – fix the namespace.

In discussion with Pete, he stated that the issue is that the URIs listed for the FACE metamodel schema in the FACE30metamodel.emof are faulty because they do not resolve to a "live" URL.

Discard/No Action: FACE URI does not resolve in emof

Discard this issue / Resolve with no action. There is no requirement for namespace URIs to resolve to "live" sites.

The XMI 2.5.1 specification (https://www.omg.org/spec/XMI/2.5.1/PDF), page 16, section 7.8.1 states, "“There is no requirement or expectation by the XML Namespace specification that the logical URI be resolved or dereferenced during processing of XML documents.”

There are two FACE Metamodel files in this submission. One is the FACE Metamodel as it appears in the FACE Technical Standard, Edition 3.0, and uses the XMI 2.0 notation. The other is not an official product of The Open Group, but is a derivative product that represents the FACE Metamodel (Edition 3.0) using XMI 2.5.1. This file was generated in response to OMG review comments that the older version of XMI was not acceptable for a Normative file. Because the FACE Metamodel file is normative per the FACE Technical Standard it should remain Normative. The derivative file that uses XMI 2.5.1 is not official and should therefore be marked as Informative.

Add clarifications to descriptions of FACE Metamodel Files

Make the following changes to Table 1-1:

• Add a new row to Table 1-1 describing the normative FACE metamodel file.
• Change all instances of "normative" in the row referencing the FACE Metamodel EMOF 2.5.1 File to "informative".
• Change the name of the referenced FACE Metamodel EMOF 2.5.1 File to "FACE metamodel 3.0 EMOF 2.5.1.emof"

(From Pete Rivette) Add explicit acknowledgement that FACE is a trademark of The Open Group

FACE Trademark ownership already indicated in footnote

In section 1. Scope, there is a footnote after the first reference to the trademarked FACE reference on the first line of the paragraph. The corresponding footnote at the bottom of page 2 states "FACE™ is a trademark of The Open Group®."

The emof file c4i-20-05-05 has an old UML namespace instead of https://www.omg.org/spec/UML/20161101

Replace UML URL to reference (current) UML 2.5.1 xmi

Replace "http://www.omg.org/spec/UML/20131001" with "http://www.omg.org/spec/UML/2016110"

(From JD Baker) I’m not sure how I feel about issues to be discussed as part of the specification. At the least this section needs to be flagged as non-normative

Mark Design Considerations as Non-Normative

Response to comment received at AB prior to FTF formation.

See Section 8. Design Considerations, page 201 for changes.

(From JD Baker) I’m not sure how I feel about issues to be discussed as part of the specification. At the least this section needs to be flagged as non-normative

(Sarah Douglass remarks) This section was added to respond to "Issues to Discuss" in the RFP. The standard did not include responses to these issues anywhere else. The Issues To Discuss topics are mostly discussion of the value of the standard, with some additional discussion about the approaches implementers might take to address OCL correctness of FACE data as described in the specification and the FACE 3.0 standard.

(from JD Baker) Section 3.1 – several OMG documents are not the latest versions. Is this intentional and if so, why?
Unified Modeling Language UML® 2.5.1 formal December 2017
Meta Object Facility MOF™ 2.5.1 formal October 2016
Diagram Definition DD™ 1.1 formal August 2015
Unified Architecture Framework UAF 1.1 formal April 2020

Fix incorrect references to normative OMG Documents

Response to comment received at AB review prior to formation of FTF.

See Section 3.1 OMG Documents (Normative References), page 5 for changes.

Original comment:
(from JD Baker) Section 3.1 – several OMG documents are not the latest versions. Is this intentional and if so, why?
Unified Modeling Language UML® 2.5.1 formal December 2017
Meta Object Facility MOF™ 2.5.1 formal October 2016
Diagram Definition DD™ 1.1 formal August 2015
Unified Architecture Framework UAF 1.1 formal April 2020

(Original comment from JD Baker) Table 1.3 has OMG document numbers that have a high likelihood of changing in the formalization process. Please remove them in the FTF.

There is no Table 1.3. Interpreting to mean Table 1-1 in section 1.3.

Remove related document numbers from section 1.3

Response to comment received at Proposal review prior to FTF charter.
See section 1.3 Related Documents on page 3 for changes.

(Original comment from JD Baker) Table 1.3 has OMG document numbers that have a high likelihood of changing in the formalization process. Please remove them in the FTF.
(Sarah Douglass) There is no Table 1.3. Interpreting to mean Table 1-1 in section 1.3.

The XMI file c4i-20-05-06 has the old name space for UML and the standard profile namespace is wrong.

Replace UML URL to reference (current) UML 2.5.1 xmi

Replace all instances of "http://www.omg.org/spec/UML/20131001" with "http://www.omg.org/spec/UML/20161101"
192 replacements in total

Original references were the result of generating XML file using MagicDraw Strict UML XMI Exporter v17.0 SP2. No action taken with Dessault/NoMagic to resolve the underlying cause of the issue.