FACE Profile for UAF Avatar
  1. OMG Specification

FACE Profile for UAF — Open Issues

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

Issues Descriptions

Missing type declarations for ownedAttributes in emof file

  • Key: FACE-23
  • Status: open  
  • Source: MITRE ( 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
  • Updated: Wed, 5 May 2021 04:17 GMT

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

  • Key: FACE-20
  • Status: open  
  • Source: MITRE ( 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
  • Updated: Wed, 5 May 2021 00:08 GMT
  • Attachments:

FACE URI does not resolve in emof

  • Key: FACE-15
  • Status: open  
  • Source: MITRE ( 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
  • Updated: Wed, 5 May 2021 00:08 GMT

Incorrect Namespace specifications in XMI file