ebXML Registry Services and Protocols
Version 3.0 Errata
OASIS Public Review Draft 01
22 February, 2007
This Version:
http://docs.oasis-open.org/regrep/v3.0/errata/regrep-rs-3.0-errata-prd01.doc
http://docs.oasis-open.org/regrep/v3.0/errata/regrep-rs-3.0-errata-prd01.html
http://docs.oasis-open.org/regrep/v3.0/errata/regrep-rs-3.0-errata-prd01.pdf
Previous Version:
N/A
Latest Version:
http://docs.oasis-open.org/regrep/v3.0/errata/regrep-rs-3.0-errata.doc
http://docs.oasis-open.org/regrep/v3.0/errata/regrep-rs-3.0-errata.html
http://docs.oasis-open.org/regrep/v3.0/errata/regrep-rs-3.0-errata.pdf
Technical Committee:
OASIS ebXML Registry TC
Chair:
Kathryn Breininger
Editor(s):
Kathryn Breininger
Related work:
This specification errata is related to:


ebXML Registry Information Model Version 3.0
ebXML Registry Services and Protocols Version 3.0
Abstract:
This is an OASIS Committee Draft listing errata for the OASIS ebXML Registry Services and
Protocols 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.oasisopen.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
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 1 of 14
Intellectual Property Rights section of the Technical Committee web page (http://www.oasisopen.org/committees/regrep/ipr.php.
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 2 of 14
Notices
Copyright © OASIS® 1993–2007. All Rights Reserved.
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" is a trademark 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.
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 3 of 14
Table of Contents
1
Issues Addressed ................................................................................................................................. 5
1.1 Terminology ........................................................................................................................................ 5
1.2 Normative References ........................................................................................................................ 5
2
Missing Figures .................................................................................................................................... 6
2.1 Figure 15: Content Management Service: Inline Invocation Model .................................................... 6
2.2 Figure 16: Content Management Service: Decoupled Invocation Model ........................................... 7
2.3 Figure 17: Cataloging Service Configuration ...................................................................................... 8
2.4 Figure 23: Federation Metadata Example .......................................................................................... 9
3
Typographical/Editorial Errors ............................................................................................................ 10
3.1 Section 5.1.2: Unique ID Generation ................................................................................................ 10
3.2 Section 6.3.2.1: Specifying Query Invocation Parameters ............................................................... 11
3.3 ebXMLRegistryInterfaces.wsdl file ................................................................................................... 12
A. Acknowledgements ............................................................................................................................ 13
B. Revision History.................................................................................................................................. 14
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 4 of 14
1
1 Issues Addressed
2
3
The following issues related to the ebXML Registry Services and Protocols version 3.0 have been
addressed in this document:
4
Missing figures:
5
6
7
8
Figure 15: Content Management Service: Inline Invocation Model, page 78
Figure 16: Content Management Service: Decoupled Invocation Model, page 79
Figure 17: Cataloging Service Configuration, page 82
Figure 23: Federation Metadata Example, page 93
9
10
Text in 5.1.2 Unique ID Generation is inconsistent with the rim.xsd. The rim.xsd is correct and paragraph
is wrong.
11
12
13
14
15
16
The stored query given in Listing 2: “Example of Stored Query Invocation” is incorrect in Section 6.3.2.1,
Specifying Query Invocation Parameters. Text in 6.3.2.1 describing the stored query invocation example
is incorrect.
17
18
19
20
21
22
23
The ebXMLRegistryInterfaces.wsdl file has a typographical error in the output message in the operation
named “UpdateObjects”.
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.
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 5 of 14
24
25
26
2 Missing Figures
2.1 Figure 15: Content Management Service: Inline Invocation Model
Insert Figure 15 on page 78, line 2732:
1. SubmitObjectRequest
Content +
etadata
M
Service
2. SubmitObjectRequest
RegistryClient
3. Content
anagement
M
Service
Request
27
28
LRegistry
ebXM
6. RegistryResponse
Content +
etadata
M
4. Content
Invocation
Control
File
Service
5. commit
anagement
M
Response
Persistent
Store
Content
anagement
M
Service
Figure 15: Content Management Service: Inline Invocation Model
29
30
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 6 of 14
31
32
33
34
2.2 Figure 16: Content Management Service: Decoupled Invocation
Model
Insert Figure 16 on page 79, line 2763:
1. SubmitObjectRequest
Content +
M
etadata
Service
2. SubmitObjectRequest
RegistryClient
5. Content
M
anagement
Service
Request
35
36
ebXM
LRegistry
4. RegistryResponse
Content +
M
etadata
6. Content
Invocation
Control
File
Service
M
anagement
Response
3. commit
7. commit
Persistent
Store
Content
M
anagem
ent
Service
Figure 16: Content Management Service: Decoupled Invocation Model
37
38
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 7 of 14
39
40
41
42
2.3 Figure 17: Cataloging Service Configuration
Insert Figure 17 on page 82, line 2870:
Figure 17: Cataloging Service Configuration
43
44
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 8 of 14
45
46
47
48
2.4 Figure 23: Federation Metadata Example
Insert Figure 23 on page 93, line 3201:
Figure 23: Federation Metadata Example
49
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 9 of 14
50
3 Typographical/Editorial Errors
51
3.1 Section 5.1.2: Unique ID Generation
52
53
Text in 5.1.2 Unique ID Generation is inconsistent with the rim.xsd. The rim.xsd is correct and paragraph
is wrong. Text needs to be edited to be consistent with rim.xsd.
54
Line 1150 original text:
55
56
57
58
59
60
61
62
63
64
65
66
A Submitter MAY optionally supply the id attribute for submitted objects. If the Submitter supplies the id
and it is a valid URN and does not conflict with the id of an existing RegistryObject within the home
registry then the registry MUST honor the Submitter-supplied id value and use it as the value of the id
attribute of the object in the registry. If the id is not a valid URN then the registry MUST return an
InvalidRequestException. If the id conflicts with the id of an existing RegistryObject within the home
registry then the registry MUST return InvalidRequestException for an UpdateObjectsRequest and treat
it as an Update action for a SubmitObjectsRequest.
If the client does not supply an id for a submitted object then the registry MUST generate a universally
unique id. A registry generated id value MUST conform to the format of a URN that specifies a DCE 128
bit UUID as specified in [UUID]:
(e.g. urn:uuid:a2345678-1234-1234-123456789012).
67
68
Replace with new text:
69
70
A Submitter MUST supply the id attribute for submitted objects. If the id is not specified then the registry
MUST return an InvalidRequestException.
71
72
73
If the id and lid match the id and lid of an existing RegistryObject within the home registry, then the
registry MUST treat it as an Update action upon the existing RegistryObject.
74
75
76
If the id matches the id of an existing RegistryObject within the home registry but the lid does not match
that existing object's lid, then the registry MUST return an InvalidRequestException.
77
78
79
80
If the lid matches the lid of an existing RegistryObject within the home registry but the id does not match
that existing object's id, then the registry MUST create the newly submitted object as a new version of the
existing object.
81
82
83
84
85
86
87
If the Submitter supplies the id and it is a valid URN then the registry MUST honor the Submitter-supplied
id value and use it as the value of the id attribute of the object in the registry. If the id is not a valid URN
then the registry MUST treat it as a temporary id and replace it, and all references to it within the request,
with a registry generated universally unique id. A registry generated universally unique id value MUST
conform to the format of a URN that specifies a DCE 128 bit UUID as specified in [UUID]:
(e.g. urn:uuid:a2345678-1234-1234-123456789012)
88
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 10 of 14
3.2 Section 6.3.2.1: Specifying Query Invocation Parameters
89
90
Text describing the listing example, line 1866, is incorrect. Original text:
91

92
Replace with new text:
93
94

95
Listing 2 example, lines 1871-1882 incorrect. Original example:
96
97
98
99
100
101
102
103
104
105
106
107
The stored query being identified by the value of the id attribute of the <rim:AdhocQuery> element.
The stored query being identified by the value of the canonical slot with name
"urn:oasis:names:tc:ebxml-regrep:rs:AdhocQueryRequest:queryId"
<AdhocQueryRequest>
<query:ResponseOption returnComposedObjects="true"
returnType="LeafClassWithRepositoryItem"/>
<rim:AdhocQuery id="${STORED_QUERY_ID}">
<rim:Slot name="$name">
<rim:ValueList>
<rim:Value>%ebXML%</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
</AdhocQueryRequest>
108
109
Listing 2: Example of Stored Query Invocation
Replace with new example:
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
<AdhocQueryRequest xmlns="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0
http://oasis-open.org/committees/regrep/documents/3.0/schema/query.xsd">
<rs:RequestSlotList>
<rim:Slot name="urn:oasis:names:tc:ebxmlregrep:rs:AdhocQueryRequest:queryId">
<rim:ValueList>
<rim:Value>urn:freebxml:registry:query:BusinessQuery</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="$name">
<rim:ValueList>
<rim:Value>%ebXML% </rim:Value>
</rim:ValueList>
</rim:Slot>
</rs:RequestSlotList>
<query:ResponseOption returnComposedObjects="true"
returnType="LeafClassWithRepositoryItem" />
<rim:AdhocQuery id="temporaryId">
<rim:QueryExpression queryLanguage="urn:oasis:names:tc:ebxmlregrep:QueryLanguage:SQL-92">
<!-- No need for an actual query since it is fetched from registry using
the queryId -->
</rim:QueryExpression>
</rim:AdhocQuery>
</AdhocQueryRequest>
141
Listing 2: Example of Stored Query Invocation
142
143
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 11 of 14
144
145
146
3.3 ebXMLRegistryInterfaces.wsdl file
The ebXMLRegistryInterfaces.wsdl file has a typographical error in the output message in the operation
named “UpdateObjects”.
147
148
149
150
151
152
Original text:
<operation name=”updateObjects”>
<input message=”tns:msgUpdateObjectsRequest”/>
<output message=”tns:msgUpdateObjectsRequest”/>
</operation>
153
154
155
156
157
158
Replace with text:
<operation name=”updateObjects”>
<input message=”tns:msgUpdateObjectsRequest”/>
<output message=”tns:msgRegistryResponse”/>
</operation>
159
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 12 of 14
160
A. Acknowledgements
161
162
The following individuals have participated in the creation of this specification and are gratefully
acknowledged:
163
Participants:
Ivan Bedini
Name
Affiliation
France Telecom
Kathryn Breininger
The Boeing Company
Paul Macias
LMI
Carl Mattocks
MetLife
Monica Martin
Sun Microsystems
Farrukh Najmi
Wellfleet Software Corporation
Nikola Stojanovic
GS1 US
Ted Hass
GS1 US
164
165
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 13 of 14
166
B. Revision History
167
Revision
Date
Editor
Changes Made
01
18 December 2006
Kathryn Breininger
Added figures, corrected text
02
07 February 2007
Kathryn Breininger
Corrected text, added wsdl correction
03
01 March 2007
Kathryn Breininger
Updated title page, notices page, and
footer
168
169
regrep-rs-3.0-errata-prd01
Copyright © OASIS® 1993–2007. All Rights Reserved.
22 February 2007
Page 14 of 14