Records Management Service Avatar
  1. OMG Specification

Records Management Service — Open Issues

  • Acronym: RMS
  • Issues Count: 9
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

No need for RecordCreator

  • Key: RMS11-41
  • Legacy Issue Number: 15685
  • Status: open  
  • Source: Auxilium Technology Group ( John Butler [X] (Inactive))
  • Summary:

    Managed Record should just have an association to Party to show which party created the record.

  • Reported: RMS 1.0b2 — Tue, 5 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

document.id type is “string”, it should be “ID”.

  • Key: RMS11-43
  • Legacy Issue Number: 15678
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    document.id type is “string”, it should be “ID”.

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

AttributeValue.partyID in the PIM should be an association… it would be a partyID in the PSM

  • Key: RMS11-45
  • Legacy Issue Number: 15674
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    We list a party ID as an attribute in the style of a foreign key in the PIM. Generally we explicitly model associations in the PIM. It would however remain a foreign key in the PSM XSD.

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Are W3C ID’s globally unique, or are there further qualifications we need to put on our ID’s

  • Key: RMS11-46
  • Legacy Issue Number: 15673
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    We presume global uniqueness in our ID scheme. Is that assured by the W3C type or do we require further clarification of intent of identifiers.

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Between DataProfileAttrDefn and AttributableClassType, the role names are misleading

  • Key: RMS11-25
  • Legacy Issue Number: 15672
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    For example “type” should be “attributableClassType”; all the “definition” (4 of them) should be “attributeDefinition

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Navigability will dictated in the PIM. We must revisit the navigability of each association

  • Key: RMS11-42
  • Legacy Issue Number: 15677
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    This will determine the manner in which Sparx EA will traverse the UML graph to produce the XSD

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

There is no linkage in the XSD between DocumentType and DataProfileAttrDefn

  • Key: RMS11-44
  • Legacy Issue Number: 15676
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    The link is needed in order to require attribution based on DocumentType; which is the intent

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Many” multiplicity is not accommodated by the XSD

  • Key: RMS11-47
  • Legacy Issue Number: 15675
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    For example, an AttributeClassType can have many DataProfileAttrDefn’s (maxoccurs=”unbounded”, which is the default).

  • Reported: RMS 1.0b2 — Sun, 3 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

RecordKeepers and Suspensions Services no longer exist but their ports are in the specification and the XMI file

  • Key: RMS11-6
  • Legacy Issue Number: 15879
  • Status: open  
  • Source: Object Management Group ( Larry Johnson [X] (Inactive))
  • Summary:

    Title: RecordKeepers and Suspensions Services no longer exist but their ports are in the specification and the XMI file.

    Descr: Removing the ports will resolve problems of untyped ports in the XMI.

    RMS-FTF: We have the solution for the issue (discovered in Monday’s AB Meeting) and will apply it. A ballot will be issued as soon as we verify that we have clean XMI, and again, I will be asking for a quick turnaround. We need to have this fixed to go through the AB on Thursday

  • Reported: RMS 1.0b2 — Tue, 7 Dec 2010 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT