FACE Profile for UAF Avatar
  1. OMG Specification

FACE Profile for UAF — All Issues

  • Acronym: FACE
  • Issues Count: 4
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

Missing type declarations for ownedAttributes in emof file

  • Key: FACE-23
  • Status: closed  
  • Source: MITRE ( Ms. Sarah Douglass)
  • Summary:

    (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.

  • Reported: FACE 1.0b1 — Wed, 7 Apr 2021 21:08 GMT
  • Disposition: Resolved — FACE 1.0
  • Disposition Summary:

    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

  • Updated: Mon, 4 Oct 2021 17:10 GMT

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

  • Key: FACE-20
  • Status: closed  
  • Source: MITRE ( Ms. Sarah Douglass)
  • Summary:

    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.

  • Reported: FACE 1.0b1 — Mon, 5 Apr 2021 15:58 GMT
  • Disposition: Resolved — FACE 1.0
  • Disposition Summary:

    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"

  • Updated: Mon, 4 Oct 2021 17:10 GMT
  • Attachments:

FACE URI does not resolve in emof

  • Key: FACE-15
  • Status: closed  
  • Source: MITRE ( Ms. Sarah Douglass)
  • Summary:

    (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.

  • Reported: FACE 1.0b1 — Fri, 2 Apr 2021 20:18 GMT
  • Disposition: Closed; No Change — FACE 1.0
  • Disposition Summary:

    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.”

  • Updated: Mon, 4 Oct 2021 17:10 GMT

Incorrect Namespace specifications in XMI file

  • Key: FACE-5
  • Status: closed  
  • Source: MITRE ( Ms. Sarah Douglass)
  • Summary:

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

  • Reported: FACE 1.0b1 — Wed, 30 Sep 2020 17:26 GMT
  • Disposition: Resolved — FACE 1.0
  • Disposition Summary:

    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.

  • Updated: Mon, 4 Oct 2021 17:10 GMT
  • Attachments: