This is an OASIS Committee Draft listing errata for the OASIS ebXML Registry Information Model Standard produced by the ebXML Registry Technical Committee. The standard was approved by the OASIS membership on 2 May 2005.

Status:

This document was last revised or approved by the ebXML Registry TC on the above date. The level of approval is also listed above. Check the “Latest Version” or “Latest Approved Version” location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/regrep/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/regrep/ipr.php.

Notices

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The name "OASIS", are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1 Issues Addressed. 4

1.1 Terminology. 4

1.2 Normative References. 4

2 Missing Figures. 5

2.1 Figure 3: Example of RegistryObject Association. 5

2.2 Figure 4: Example of Intramural Association. 6

2.3 Figure 5: Example of Extramural Association. 7

2.4 Figure 9: Context Sensitive Classification. 8

2.5 Figure 11: Organization to RegistryObject Association Instance Diagram.. 9

2.6 Figure 14: Federation Information Model 10

2.7 Figure 15: Instance Diagram for Abstract Access Control Information Model 11

A. Acknowledgements. 13

B. Revision History. 14

1 Issues Addressed

The following issues related to the ebXML Registry Information Model version 3.0 have been addressed in this document:

Missing figures:

Figure 3: Example of RegistryObject Association, page 28

Figure 4: Example of Intramural Association, page 29

Figure 5: Example of Extramural Association, page 30

Figure 9: Context Sensitive Classification, page 37

Figure 11: Organization to RegistryObject Association Instance Diagram, page 42

Figure 14: Federation Information Model, page 55

Figure 15: Instance Diagram for Abstract Access Control Information Model, page 61

Text in Section 2.5.6 Attribute lid needs to be clarified to indicate that it is the original version of a RegistryObject that is being assigned a lid attribute and that this must be a globally unique URN.

1.1 Terminology

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].

1.2 Normative References

[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.

2 Missing Figures

2.1 Figure 3: Example of RegistryObject Association

Insert Figure 3 on page 28, line 746:

Figure 3: Example of RegistryObject Association

2.2 Figure 4: Example of Intramural Association

Insert Figure 4 on page 29, line 768:

Figure 4: Example of Intramural Association

2.3 Figure 5: Example of Extramural Association

Insert Figure 5 on page 30, line 782:

Figure 5: Example of Extramural Association

2.4 Figure 9: Context Sensitive Classification

Insert Figure 9 on page 37, line 979:

Figure 9: Context Sensitive Classification

2.5 Figure 11: Organization to RegistryObject Association Instance Diagram

Insert Figure 11 on page 42, line 1085:

Figure 11: Organization to RegistryObject Association Instance Diagram

2.6 Figure 14: Federation Information Model

Insert Figure 14 on page 55, line 1431:

Figure 14: Federation Information Model

2.7 Figure 15: Instance Diagram for Abstract Access Control Information Model

Insert Figure 15 on page 61, line 1577:

Figure 15: Instance Diagram for Abstract Access Control Information Model

3 Typographical/Editorial Errors

3.1 Section 2.5.6 Attribute lid

Line 561 original text:

Each RegistryObject instance MUST have a lid (Logical Id) attribute . The lid is used to refer to a logical RegistryObject in a version independent manner. All versions of a RegistryObject MUST have the same value for the lid attribute. Note that this is in contrast with the id attribute that MUST be unique for each version of the same logical RegistryObject. The lid attribute MAY be specified by the submitter when creating the original version of a RegistryObject. If the submitter assigns the lid attribute, she must guarantee that it is a globally unique URN. A registry MUST honor a valid submitter supplied LID. If the submitter does not specify a LID then the registry MUST assign a LID and the value of the LID attribute MUST be identical to the value of the id attribute of the first (originally created) version of the logical RegistryObject.

Replace with new text:

Each RegistryObject instance MUST have a lid (Logical Id) attribute . The lid is used to refer to a logical RegistryObject in a version independent manner. All versions of a RegistryObject MUST have the same value for the lid attribute. Note that this is in contrast with the id attribute that MUST be unique for each version of the same logical RegistryObject. The lid attribute MAY be specified by the submitter when creating the original version of a RegistryObject. If the submitter assigns the lid attribute when submitting the original version of a RegistryObject, she must guarantee that it is a globally unique URN. A registry MUST honor a valid submitter supplied LID. If the submitter does not specify a LID then the registry MUST assign a LID and the value of the LID attribute MUST be identical to the value of the id attribute of the first (originally created) version of the logical RegistryObject.

A. Acknowledgements

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:

Name	Affiliation
Ivan Bedini	France Telecom
Kathryn Breininger	The Boeing Company
Paul Macias	LMI
Carl Mattocks	MetLife
Monica Martin	Sun Microsystems
Farrukh Najmi	Wellfleet Software Corp
Nikola Stojanovic	GS1 US
Ted Hass	GS1 US

B. Revision History

Revision	Date	Editor	Changes Made
01	18 December 2006	Kathryn Breininger	Added figures
02	01 March 2007	Kathryn Breininger	Updated title page, notices page, and footer