Regrep Owl Profile v1.5 Cd01

1
ebXML Registry Profile for Web Ontology
Language (OWL)
Version 1.5
Committee Draft 01, September 25, 2006
7
8
Document identifier:
regrep-owl-profile-v1.5-cd01
Specification URIs:
13
This Version:
docs.oasis-open.org/regrep/v3.0/profiles/owl/regrep-owl-profile-v1.5-cd01.html
docs.oasis-open.org/regrep/v3.0/profiles/owl/regrep-owl-profile-v1.5-cd01.pdf
docs.oasis-open.org/regrep/v3.0/profiles/owl/regrep-owl-profile-v1.5-cd01.odt
14
Previous Version: [N/A]
15
18
Latest Version:
docs.oasis-open.org/regrep/v3.0/profiles/owl/regrep-owl-profile-v1.5.html
docs.oasis-open.org/regrep/v3.0/profiles/owl/regrep-owl-profile-v1.5.pdf
docs.oasis-open.org/regrep/v3.0/profiles/owl/regrep-owl-profile-v1.5.odt
19
Technical Committee:
20
Editors:
Name
Asuman Dogac
10
11
12
16
17
OASIS ebXML Registry Technical Committee
21
22
23
24
Abstract:
This document defines the ebXML Registry profile for publishing, management, discovery and
reuse of OWL Lite Ontologies.
Copyright OASIS Open 2005. All Rights Reserved.
September 25, 2006

Page 1 of 76
25
26
27
28
29
30
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 current location noted above for possible later
revisions of this document. This document is updated periodically on no particular schedule.
31
32
33
34
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
35
www.oasis-open.org/committees/regrep.
36
37
38
39
40
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
www.oasis-open.org/committees/regrep/ipr.php.
41
42
The non-normative errata page for this specification is located at
43
www.oasis-open.org/committees/regrep.
44
45
46
47
48
49
50
51
52
53
54
55
56
57
Notices:
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be
obtained from the OASIS Executive Director. OASIS invites any interested party to bring to its
attention any copyrights, patents or patent applications, or other proprietary rights which may
cover technology that may be required to implement this specification. Please address the
information to the OASIS Executive Director.
58
59
60
61
62
63
64
65
66
67
Copyright (c) OASIS Open 2006. All Rights Reserved.

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 paragraph are included on all such copies and derivative works.
However, this document itself may not be modified in any way, such as by removing the copyright
notice or references to OASIS, except as needed for the purpose of developing OASIS
specifications, in which case the procedures for copyrights defined in the OASIS Intellectual
Property Rights document must be followed, or as required to translate it into languages other
than English.
68
69
70
71
72
73
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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE.
74
September 25, 2006

Page 2 of 76
75
1 Table of Contents
103
1 Table of Contents...................................................................................................................................... 3
1Introduction.............................................................................................................................................. 10
1.1 Terminology..................................................................................................................................... 11
1.2 Conventions..................................................................................................................................... 11
1.3 Recommended Enhancements....................................................................................................... 11
2 OWL Overview........................................................................................................................................ 12
2.1 Semantic Web Languages upon which OWL is Layered................................................................. 12
2.2 OWL Lite Constructs....................................................................................................................... 13
2.2.1 RDF Schema Features............................................................................................................. 13
2.2.2 (In)Equality............................................................................................................................... 13
2.2.3 Property Characteristics .......................................................................................................... 13
2.2.4 Property Restrictions................................................................................................................ 13
2.2.5 Restricted Cardinality................................................................................................................ 13
2.2.6 Class Intersection..................................................................................................................... 13
2.2.7 Versioning................................................................................................................................ 14
2.2.8 Annotation Properties .............................................................................................................. 14
2.2.9 Datatypes ................................................................................................................................ 14
2.3 OWL DL Constructs......................................................................................................................... 14
2.3.1 Class Axioms............................................................................................................................ 14
2.3.2 Boolean Combinations of Class Expressions .......................................................................... 14
2.3.3 Arbitrary Cardinality ................................................................................................................. 14
2.3.4 Filler Information....................................................................................................................... 14
3 ebXML Registry Overview....................................................................................................................... 15
3.1 Overview of [ebRIM]........................................................................................................................ 15
3.1.1 RegistryObject.......................................................................................................................... 16
3.1.2 Object Identification.................................................................................................................. 16
3.1.3 Object Naming and Description................................................................................................ 17
3.1.4 Object Attributes....................................................................................................................... 17
104
3.1.4.1 Slot Attributes...................................................................................................................................... 17
105
3.1.5 Object Classification................................................................................................................. 18

3.1.6 Object Association.................................................................................................................... 18
3.1.7 Object References To Web Content......................................................................................... 19
3.1.8 Object Packaging..................................................................................................................... 19
3.1.9 ExtrinsicObject ........................................................................................................................ 20
3.1.10 Service Description................................................................................................................. 20
3.2 Overview of [ebRS].......................................................................................................................... 20
4 Representing OWL Lite Constructs in ebRIM ........................................................................................ 21
4.1 Representing RDF Schema Features in ebRIM............................................................................... 21
4.1.1 owl:Class rim:ClassificationNode......................................................................................... 21
4.1.2 rdf:Property rim:Association Type HasProperty.................................................................... 21
4.1.3 rdfs:subPropertyOf rim:Association Type SubPropertyOf.................................................... 22
4.1.4 rdfs:subClassOf rim:Association Type SubClassOf............................................................. 22
4.1.5 owl:Individual rim:ExtrinsicObject......................................................................................... 23
4.2 Representing OWL (In)Equality Constructs in ebXML RIM.............................................................. 24
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
106
107
108
109
110
111
112
113
114
115
116
117
118
119
September 25, 2006

Page 3 of 76
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
4.2.1 owl:equivalentClass, owl:equivalentPropery rim:Association Type EquivalentTo ................ 24

4.2.2 owl:sameAs rim:Association Type SameAs......................................................................... 24
4.2.3 owl:differentFrom rim:Association Type DifferentFrom........................................................ 24
4.2.4 owl:AllDifferent.......................................................................................................................... 25
4.3 Representing OWL Property Characteristics in ebRIM.................................................................... 26
4.3.1 owl:ObjectProperty rim:Association Type objectProperty..................................................... 26
4.3.2 owl:DatatypeProperty rim:Association Type DatatypeProperty............................................. 26
4.3.3 owl:TransitiveProperty rim:Association Type TransitiveProperty.......................................... 26
4.3.4 owl:inverseOf rim:Association Type InverseOf..................................................................... 27
4.3.5 owl:SymmetricProperty rim:Association Type SymmetricProperty....................................... 28
4.3.6 owl:FunctionalProperty rim:Association Type FunctionalProperty......................................... 28
4.3.7 owl:InverseFunctionalProperty rim:Association Type InverseFunctionalProperty.................. 29
4.4 OWL Property Restrictions in ebXML RIM....................................................................................... 29
4.5 Representing OWL Restricted Cardinality in ebXML RIM................................................................ 30
4.5.1 owl:minCardinality (only 0 or 1)................................................................................................. 30
4.5.2 owl:maxCardinality (only 0 or 1)................................................................................................ 31
4.5.3 owl:cardinality (only 0 or 1)....................................................................................................... 32
4.6 Representing OWL Class Intersection in ebXML RIM..................................................................... 32
4.7 Representing OWL Versioning in ebXML RIM................................................................................. 33
4.7.1 owl:versionInfo, owl:priorVersion.............................................................................................. 33
4.8 Representing OWL Annotation Properties in ebXML RIM............................................................... 34
4.8.1 rdfs:label................................................................................................................................... 34
4.8.2 rdfs:comment........................................................................................................................... 34
4.8.3 rdfs:seeAlso.............................................................................................................................. 34
4.9 OWL Datatypes in ebXML RIM........................................................................................................ 35
5 Cataloging Service Profile....................................................................................................................... 36
5.1 Invocation Control File..................................................................................................................... 36
5.2 Input Metadata................................................................................................................................. 36
5.3 Input Content................................................................................................................................... 36
5.4 Output Metadata.............................................................................................................................. 37
5.4.1 owl:Class rim:ClassificationNode......................................................................................... 37
5.4.2 rdf:Property rim:Association Type HasProperty.................................................................... 37
5.4.3 rdfs:subPropertyOf rim:Association Type SubPropertyOf.................................................... 37
5.4.4 rdfs:subClassOf rim:Association Type subClassOf.............................................................. 37
5.4.5 owl:Individual rim:ExtrinsicObject......................................................................................... 37
5.4.6 owl:equivalentClass, owl:equivalentPropery rim:Association Type EquivalentTo ................ 37
5.4.7 owl:sameAs rim:Association Type SameAs ........................................................................ 37
5.4.8 owl:differentFrom rim:Association Type DifferentFrom........................................................ 37
5.4.9 owl:AllDifferent rim:RegistryPackage................................................................................... 37
5.4.10 owl:ObjectProperty rim:Association Type ObjectProperty.................................................. 38
5.4.11 owl:DatatypeProperty rim:Association Type DatatypeProperty........................................... 38
5.4.12 owl:TransitiveProperty rim:Association Type TransitiveProperty........................................ 38
5.4.13 owl:inverseOf rim:Association Type InverseOf................................................................... 38
5.4.14 owl:SymmetricProperty rim:Association Type SymetricProperty........................................ 38
5.4.15 owl:FunctionalProperty rim:Association Type FunctionalProperty....................................... 38
5.4.16 owl:InverseFunctionalProperty rim:Association Type InverseFunctionalProperty................ 38
September 25, 2006

Page 4 of 76
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
5.4.17 owl:minCardinality (only 0 or 1)............................................................................................... 38

5.4.18 owl:maxCardinality (only 0 or 1).............................................................................................. 39
5.4.19 owl:cardinality......................................................................................................................... 39
5.4.20 owl:intersectionOf................................................................................................................... 39
5.4.21 rdfs:label................................................................................................................................. 39
5.4.22 rdfs:comment......................................................................................................................... 39
5.4.23 rdfs:seeAlso............................................................................................................................ 39
6 Discovery Profile..................................................................................................................................... 40
6.1 All SuperProperties Discovery Query............................................................................................... 40
6.1.1 Parameter $propertyName....................................................................................................... 40
6.1.2 Example of All SuperProperties Discovery Query..................................................................... 40
6.2 Immediate SuperClass Discovery Query......................................................................................... 41
6.2.1 Parameter $className............................................................................................................ 41
6.2.2 Example of Immediate SuperClass Discovery Query............................................................... 41
6.3 Immediate SubClass Discovery Query............................................................................................ 42
6.3.2 Example of Immediate SubClasss Discovery Query................................................................. 42
6.4 All SuperClasses Discovery Query.................................................................................................. 42
6.4.2 Example of All SuperClasses Discovery Query........................................................................ 43
6.5 All SubClasses Discovery Query...................................................................................................... 43
6.5.2 Example of All SubClassses Discovery Query.......................................................................... 43
6.6 EquivalentClasses Discovery Query................................................................................................ 44
6.6.2 Example of EquivalentClasses Discovery Query...................................................................... 44
6.7 EquivalentProperties Discovery Query............................................................................................. 45
6.7.1 Parameter $propertyName....................................................................................................... 45
6.7.2 Example of EquivalentProperties Discovery Query................................................................... 45
6.8 SameExtrinsicObjects Discovery Query.......................................................................................... 46
6.8.1 Parameter $extrinsicObjectName............................................................................................. 46
6.8.2 Example of SameExtrinsicObjects Discovery Query................................................................ 46
6.9 DifferentExtrinsicObjects Discovery Query...................................................................................... 46
6.9.1 Parameter $extrinsicObjectName............................................................................................. 47
6.9.2 Example of DifferentExtrinsicObjects Discovery Query............................................................ 47
6.10 AllDifferentRegistryObject Discovery Query................................................................................... 47
6.10.1 Parameter $registryObjectName............................................................................................ 47
6.10.2 Example of AllDifferentRegistryObjects Discovery Query....................................................... 47
6.11 ObjectProperties Discovery Query................................................................................................. 48
6.11.1 Parameter $className.......................................................................................................... 48
6.11.2 Example of ObjectProperties Discovery Query....................................................................... 48
6.12 ImmediateInheritedObjectProperties Discovery Query.................................................................. 49
6.12.2 Example of ImmediateInheritedObjectProperties Discovery Query........................................ 49
6.13 AllInheritedObjectProperties Discovery Query............................................................................... 50
September 25, 2006

Page 5 of 76
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
6.13.2 Example of AllInheritedObjectProperties Discovery Query..................................................... 50

6.14 DatatypeProperties Discovery Query............................................................................................. 51
6.14.2 Example of DatatypeProperties Discovery Query................................................................... 51
6.15 AllInheritedDatatypeProperties Discovery Query........................................................................... 51
6.15.2 Example of AllInheritedDatatypeProperties Discovery Query................................................. 52
6.16 TransitiveRelationships Discovery Query....................................................................................... 52
6.16.2 Parameter $propertyName..................................................................................................... 53
6.16.3 Example of TransitiveRelationships Discovery Query............................................................. 53
6.17 TargetObjects Discovery Query..................................................................................................... 53
6.17.3 Example of TargetObjects Discovery Query........................................................................... 54
6.18 TargetObjectsInverseOf Discovery Query.................................................................................... 54
6.18.3 Example of TargetObjectsInverseOf Discovery Query........................................................... 55
6.19 InverseRanges Discovery Query................................................................................................... 55
6.19.3 Example of InverseRanges Discovery Query......................................................................... 56
6.20 SymmetricProperties Discovery Query.......................................................................................... 57
6.20.2 Example of SymmetricProperties Discovery Query................................................................ 57
6.21 FunctionalProperties Discovery Query........................................................................................... 57
6.21.2 Example of FunctionalProperties Discovery Query................................................................. 58
6.22 InverseFunctionalProperties Discovery Query............................................................................... 58
6.22.2 Example of InverseFunctionalProperties Discovery Query..................................................... 58
6.23 Instances Discovery Query............................................................................................................ 59
6.23.2 Example of Instances Discovery Query.................................................................................. 59
7 Canonical Metadata Definitions............................................................................................................... 61
7.1 ObjectType Extensions.................................................................................................................... 61
7.2 AssociationType Extensions............................................................................................................ 61
7.3 Canonical Queries........................................................................................................................... 64
7.3.1 All SuperProperties Discovery Query........................................................................................ 64
7.3.2 Immediate SuperClass Discovery Query.................................................................................. 64
7.3.3 Immediate SubClass Discovery Query..................................................................................... 64
7.3.4 All SuperClasses Discovery Query........................................................................................... 65
7.3.5 All SubClasses Discovery Query.............................................................................................. 65
7.3.6 EquivalentClasses Discovery Query......................................................................................... 65
7.3.7 EquivalentProperties Discovery Query..................................................................................... 66
September 25, 2006

Page 6 of 76
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
7.3.8 SameExtrinsicObjects Discovery Query.................................................................................. 66

7.3.9 DifferentExtrinsicObjects Discovery Query............................................................................... 67
7.3.10 AllDifferentRegistryObject Discovery Query........................................................................... 67
7.3.11 ObjectProperties Discovery Query.......................................................................................... 68
7.3.12 ImmediateInheritedObjectProperties Discovery Query........................................................... 68
7.3.13 AllInheritedObjectProperties Discovery Query........................................................................ 69
7.3.14 DatatypeProperties Discovery Query...................................................................................... 69
7.3.15 AllInheritedDatatypeProperties Discovery Query.................................................................... 69
7.3.16 TransitiveRelationships Discovery Query............................................................................... 69
7.3.17 TargetObjects Discovery Query.............................................................................................. 70
7.3.18 TargetObjectsInverseOf Discovery Query.............................................................................. 70
7.3.19 InverseRanges Discovery Query............................................................................................ 71
7.3.20 SymmetricProperties Discovery Query................................................................................... 72
7.3.21 FunctionalProperties Discovery Query.................................................................................... 72
7.3.22 InverseFunctionalProperties Discovery Query........................................................................ 72
7.3.23 Instances Discovery Query Discovery Query.......................................................................... 73
8 OWL Profile References......................................................................................................................... 75
8.1 Normative References..................................................................................................................... 75
8.2 Informative References.................................................................................................................... 76
Appendix A............................................................................................................................................ 76
278
September 25, 2006

Page 7 of 76
Illustration Index
Figure 1: ebXML Registry Information Model, High Level Public View....................................................... 15
Figure 2: ebXML Registry Information Model, Inheritance View................................................................. 16
279
September 25, 2006

Page 8 of 76
Index of Tables
280
September 25, 2006

Page 9 of 76
281
1 Introduction
282
This chapter provides an introduction to the rest of this document.
283
284
285
286
287
288
289
The ebXML Registry holds the metadata for the RegistryObjects and the documents pointed at by the
RegistryObjects reside in an ebXML repository. The basic semantic mechanisms of ebXML Registry are
classification hierarchies (ClassificationScheme) consisting of ClassificationNodes and the Association
Types among RegistryObjects. Furthermore, RegistryObjects can be assigned properties through a slot
mechanism and RegistryObjects can be classified using instances of Classification, ClassificationScheme
and ClassificationNodes. Given these constructs, considerable amount of semantics can be defined in the
registry.
290
291
292
293
However, currently semantics is becoming a much broader issue than it used to be since several
application domains are making use of ontologies to add knowledge to their data and applications
[StaabStuder]. One of the driving forces for ontologies is the Semantic Web initiative [LeeHendler]. As a
part of this initiative, W3C's Web Ontology Working Group defined Web Ontology Language [OWL].
294
295
Naturally, there is lot to be gained from using a standard ontology definition language, like OWL, to
express semantics in ebXML registries.
296
297
298
299
300
301
This document normatively defines the ebXML Registry profile for Web Ontology Language (OWL) Lite.
More specifically, this document normatively specifies how OWL Lite constructs SHOULD be represented
by ebXML RIM constructs without causing any changes in the core ebXML Registry specifications
[ebRIM], [ebRS]. Furthermore, this document normatively specifies the code to process some of the
OWL semantics through parameterized stored procedures that SHOULD be made available from the
ebXML Registry.
302
303
304
305
306
307
These predefined stored queries provide the necessary means to exploit the enhanced semantics stored
in the Registry. Hence, an application program does not have to develop additional code to process this
semantics. In this way, it becomes possible to retrieve not only explicit but also the implied knowledge
through queries, the enhancements to the registry are generic and also the registry specification is kept
intact. The capabilities provided, move the semantics support beyond what is currently available in ebXML
registries and it does so by using a standard ontology language.
308
309
310
311
312
313
314
Finally it is worth noting that ontologies can play two major roles: One is to provide a source of shared and
precisely defined terms which can be used in formalizing knowledge and relationship among objects in a
domain of interest. The other is to reason about the ontologies. When an ontology language like OWL is
mapped to a class hierarchy like the one in ebXML, the first role can directly be achieved. Furthermore
some implicit information can be obtained by predefined parameterized queries. However, when we want
full reasoning power, we need reasoners. Yet, OWL reasoners can not directly run on the ebXML registry
because all the registry information is not stored in OWL syntax.
315
316
Although this Profile is reIated to ebXML Registry specifications and not to any particular implementation,
in order to be able to give concrete examples, the freebXML Registry implementation is used.
317
The document is organized as follows:
318
Chapter 1 provides an introduction to the rest of this document.
319
Chapter 2 provides an overview of the Web Ontology Language.
320
Chapter 3 provides an overview of the ebXML Registry standard.
321
322
Chapter 4 specifies the mapping between Web Ontology Language constructs and ebXML
Registry Information Model.
323
Chapter 5 describes the cataloging service for cataloging OWL content.
324
Chapter 6 provides the discovery queries for a registry implementing this profile.
325
326
Chapter 7 specifies the canonical metadata (such as object type extensions, new association
types and the stored queries) defined by this profile.
327
328
Chapter 8 provides normative and informative references that are used within or relevant to this
document.
September 25, 2006

Page 10 of 76
329
1.1 Terminology
330
331
332
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 IETF RFC
2119 [RFC211].
333
334
335
The term repository item is used to refer to content (e.g., an XML document or a DTD) that resides in a
repository for storage and safekeeping. Each repository item is described by a RegistryObject instance.
The RegistryObject catalogs the RepositoryItem with metadata.
336
1.2 Conventions
339
Throughout the document the following conventions are employed to define the data structures used. The
following text formatting conventions are used to aide readability:
UML Diagrams
340
341
UML diagrams are used as a way to concisely describe information models in a standard way. They
are not intended to convey any specific Implementation or methodology requirements.
342
343
344
345
346
347
Listings may contain values that reference ebXML Registry objects by their id attribute. These id
values uniquely identify the objects within the ebXML Registry. For convenience and better readability,
these key values are replaced by meaningful textual variables to represent such id values.
For example, the following placeholder refers to the unique id defined for the canonical
ClassificationNode that defines the Organization ObjectType defined in [ebRIM]:
337
338
Identifier Placeholders
348
349
350
<id="${CANONICAL_OBJECT_TYPE_ID _ORGANIZATION}" >
1.3 Recommended Enhancements
353
In the current ebXML Registry implementation, when a stored query is submitted to the ebXML Registry, it
is stored in the AdhocQuery relational table without validation:
AdhocQuery (id, lid, objectType, status, versionName, comment_, queryLanguage, query);
354
355
356
357
358
359
When a user tries to invoke this stored query through a AdhocQuery, ebRS parses the stored query and
converts this stored query to the syntax acceptable by the underlying database. Furthermore currently
ebRS supports the SQL 92 [SQL 92] standard which does not include the recursion mechanisms. Also,
there seems to be problems in parsing queries involving UNION. Since some of the queries involved in
this Profile requires recursion and UNION mechanisms of SQL, it may help if ebRS is extended to support
SQL 99 standard [SQL 99].
351
352
September 25, 2006

Page 11 of 76
360
361
362
363
364
365
2 OWL Overview
This chapter provides an overview of the Web Ontology Language [OWL]. Web Ontology Language
[OWL] is a semantic markup language for publishing and sharing ontologies on the World Wide Web.
OWL is derived from the DAML+OIL Web Ontology Language [DAML+OIL] and builds upon the Resource
Description Framework [RDF].
OWL provides three decreasingly expressive sublanguages [McGuinness, Harmelen]:
366
367
368
OWL Full is meant for users who want maximum expressiveness and the syntactic freedom of
RDF with no computational guarantees. It is unlikely that any reasoning software will be able to
support complete reasoning for OWL Full.
369
370
371
372
OWL DL supports those users who want the maximum expressiveness while retaining
computational completeness (all conclusions are guaranteed to be computable) and decidability
(all computations will finish in finite time). OWL DL is so named due to its correspondence with
description logics which form the formal foundation of OWL.
373
374
OWL Lite supports those users primarily needing a classification hierarchy and simple
constraints.
375
376
Within the scope of this document, only OWL Lite constructs are considered and in the rest of the
document, OWL is used to mean OWL Lite unless otherwise stated.
377
378
OWL describes the structure of a domain in terms of classes and properties.

The list of OWL language constructs is as follows [McGuinness, Harmelen]:
379
2.1 Semantic Web Languages upon which OWL is Layered
380
381
382
383
384
385
386
387
388
OWL is one of a set of languages defined for the Semantic Web. It occupies the Ontology layer of an
architecture sometimes referred to as the Semantic Web Layer Cake. This moniker alludes to the fact
that each language in the architecture sits on top of another while exposing some of the layer below is
often seen of a wedding cake. OWL is situated in this architecture directly above the RDF Vocabulary
Description Language: RDF Schema (RDFS) [RDFS]. RDFS is a language for defining vocabularies or
models with which to describe or categorize resources in the semantic web. RDFS, in turn, sits atop the
Resource Description Framework (RDF) [RDF]. RDF provides a basic data model, XML based transfer
syntax, and other basic tools. The whole Semantic Web stack itself then sits atop XML technologies
which are used for identification and syntax definition.
389
Namespace information for these languages is given in the Table 1.
390
Table 1: Semantic Web namespace table
391
392
Commonly used Prefix
Namespace URI Reference
rdf
http://www.w3.org/1999/02/22-rdfsyntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
owl
http://www.w3.org/2002/07/owl#
393
394
395
396
397
The following section discusses elements of OWL along with a few elements of RDF and RDFS which are
most important to users of OWL. In this section Terms from RDF and RDFS vocabularies are
distinguished from OWL terms by the inclusion of the appropriate prefix as given in the Table 1.
398
399
September 25, 2006

Page 12 of 76
400
2.2 OWL Lite Constructs
401
2.2.1 RDF Schema Features
402
Class (Thing, Nothing)
403
rdfs:subClassOf
404
rdf:Property
405
rdfs:subPropertyOf
406
rdfs:domain
407
rdfs:range
408
Individual
409
2.2.2 (In)Equality
410
equivalentClass
411
equivalentProperty
412
sameAs
413
differentFrom
414
AllDifferent
415
distinctMembers
416
2.2.3 Property Characteristics
417
ObjectProperty
418
DatatypeProperty
419
inverseOf
420
TransitiveProperty
421
SymmetricProperty
422
FunctionalProperty
423
InverseFunctionalProperty
424
2.2.4 Property Restrictions
425
Restriction
426
onProperty
427
allValuesFrom
428
someValuesFrom
429
2.2.5 Restricted Cardinality
430
minCardinality (only 0 or 1)
431
maxCardinality (only 0 or 1)
432
cardinality (only 0 or 1)
433
434
2.2.6 Class Intersection
intersectionOf
September 25, 2006

Page 13 of 76
435
2.2.7 Versioning
436
versionInfo
437
priorVersion
438
backwardCompatibleWith
439
incompatibleWith
440
DeprecatedClass
441
DeprecatedProperty
442
2.2.8 Annotation Properties
443
rdfs:label
444
rdfs:comment
445
rdfs:seeAlso
446
rdfs:isDefinedBy
447
AnnotationProperty
448
OntologyProperty
449
450
2.2.9 Datatypes
xsd datatypes
451
2.3 OWL DL Constructs
452
2.3.1 Class Axioms
453
oneOf, dataRange
454
disjointWith
455
equivalentClass (applied to class expressions)
456
rdfs:subClassOf (applied to class expressions)
457
2.3.2 Boolean Combinations of Class Expressions
458
unionOf
459
complementOf
460
intersectionOf
461
2.3.3 Arbitrary Cardinality
462
minCardinality
463
maxCardinality
464
cardinality
465
466
2.3.4 Filler Information
hasValue
467
September 25, 2006

Page 14 of 76
468
3 ebXML Registry Overview
469
470
This chapter provides an overview of ebXML Registry Information Model [ebRIM] and an overview of the
specific domain and/or application.
471
The [ebRIM] is the target for the mapping patterns defined by this document.
472
473
The information presented is informative and is not intended to replace the normative information defined
by ebXML Registry.
474
3.1 Overview of [ebRIM]
475
476
This section is provided in the Deployment Profile Template for ebXML V3 specs and can be removed
in a specific profile.
477
Normally only specifics topics needs to be developed here (but the profile editor can prefer to leave it)
478
479
480
This section summarizes the ebXML Registry Information Model [ebRIM]. This model is the target of the
mapping defined in this document. The reader SHOULD read [CMRR] for a more detailed overview of
ebXML Registry as a whole.
482
Figure 1: ebXML Registry Information Model, High Level Public View
483
484
485
486
487
The ebXML registry defines a Registry Information Model [ebRIM] that specifies the standard metadata
that may be submitted to the registry. Figure 1 presents the UML class diagram representing the Registry
Information Model. Figure 2, shows the inheritance relationships in among the classes of the ebXML
Registry Information Model.
488
September 25, 2006

Page 15 of 76
490
Figure 2: ebXML Registry Information Model, Inheritance View
491
The next few sections describe the main features of the information model.
492
3.1.1 RegistryObject
493
This is an abstract base class used by most classes in the model. It provides minimal
494
495
metadata for registry objects. The following sections use the Organization sub-class of RegistryObject as
an example to illustrate features of the model.
496
3.1.2 Object Identification
497
A RegistryObject has a globally unique id which is a UUID based URN:
498
499
500
501
502
<rim:Organization id="urn:uuid:dafa4da3-1d92-4757-8fd8-ff2b8ce7a1bf" >
Listing 1: Example of id attribute

The id attribute value MAY potentially be human friendly but MUST be a unique ID value within the
registry.
503
504
<rim:Organization id="uurn:oasis:Organization">
505
Listing 2: Example of human friendly id attribute
506
507
Since a RegistryObject MAY have several versions, a logical id (called lid) is also defined which is unique
for different logical objects. However the lid attribute value MUST be the same for all versions of the same
September 25, 2006

Page 16 of 76
508
509
510
511
512
logical object. The lid attribute value is a URN that, as well for id attribute, MAY potentially be human
friendly:
<rim:Organization id=${ACME_ORG_ID}
lid="urn:acme:ACMEOrganization">
Listing 3: Example of lid Attribute
513
514
515
516
517
518
519
520
521
522
523
524
525
A RegistryObject MAY also have any number of ExternalIdentifiers which may be any string value within
an identified ClassificationScheme.
<rim:ExternalIdentifier id=${EXTERNAL_IDENTIFIER_ID}
identificationScheme=${DUNS_CLASSIFICATIONSCHEME_ID}
value="ACME"/>
</rim:ExternalIdentifier>
</rim:Organization>
Listing 4: Example of ExternalIdentifier
526
527
3.1.3 Object Naming and Description
528
529
A RegistryObject MAY have a name and a description which consists of one or more strings in one or
more local languages. Name and description need not be unique across RegistryObjects.
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
<rim:Name>
<rim:LocalizedString value="ACME Inc." xml:lang="en-US"/>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="ACME is a provider of Java software."
xml:lang="en-US"/>
</rim:Description>
value="ACME"/>
</rim:Organization>
Listing 5: Example of Name and Description
547
548
549
3.1.4 Object Attributes
550
551
For each class in the model, [ebRIM] defines specific attributes. Examples of several of these attributes
such as id, lid, name and description have already been introduced.
552
3.1.4.1 Slot Attributes
553
554
555
556
In addition the model provides a way to add custom attributes to any RegistryObject instance using
instances of the Slot class. The Slot instance has a Slot name which holds the attribute name and MUST
be unique within the set of Slot names in that RegistryObject. The Slot instance also has a ValueList that
is a collection of one or more string values.
557
558
The following example shows how a custom attribute named urn:acme:slot:NASDAQSymbol and value
ACME MAY be added to a RegistryObject using a Slot instance.
559
560
561
September 25, 2006

Page 17 of 76
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
<rim:Slot name="urn:acme:slot:NASDAQSymbol">
<rim:ValueList>
<rim:Value>ACME</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Name>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="ACME makes Java. Provider of free Java
software."
xml:lang="en-US"/>
</rim:Description>
value="ACME"/>
</rim:Organization>
Listing 6: Example of a Dynamic Attribute Using Slot
583
3.1.5 Object Classification
584
585
586
587
Any RegistryObject may be classified using any number of Classification instance. A Classification
instance references an instance of a ClassificationNode as defined by [ebRIM]. The ClassificationNode
represents a value within the ClassificationScheme. The ClassificationScheme represents the
classification taxonomy.
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
<rim:Slot name="urn:acme:slot:NASDAQSymbol">
<rim:ValueList>
<rim:Value>ACME</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Name>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="ACME makes Java. Provider of free Java
software." xml:lang="en-US"/>
</rim:Description>
value="ACME"/>

<rim:Classification id=${CLASSIFICATION_ID}
classificationNode=${NAICS_SOFTWARE_PUBLISHER_NODE_ID}
classifiedObject=${ACME_ORG_ID}>
</rim:Organization>
Listing 7: Example of Object Classification
615
3.1.6 Object Association
616
617
618
Any RegistryObject MAY be associated with any other RegistryObject using an Association instance
where one object is the sourceObject and the other is the targetObject of the Association instance. An
Association instance MAY have an associationType which defines the nature of the association.
619
620
621
There are a number of predefined Association Types that a registry must support to be [ebRIM] compliant.
These canonical association types are defined as a ClassificationScheme called AssociationType. The
SubmitObjectsRequest document of the AssociationType Classification scheme is available at:
September 25, 2006

Page 18 of 76
622
623
624
http://www.oasisopen.org/committees/regrep/documents/3.0/canonical/SubmitObjectsRequest_AssociationTypeScheme.x
ml
625
[ebRIM] allows this scheme to be extensible.
626
627
628
The following example shows an Association between the ACME Organization instance and a Service
instance with the associationType of OffersService. This indicates that ACME Organization offers the
specified service (Service instance is not shown).
629
630
631
632
633
634
635
<rim:Association
id=${ASSOCIATION_ID}
associationType=${CANONICAL_ASSOCIATION_TYPE_OFFERS_SERVICE_ID}
sourceObject=${ACME_ORG_ID}
targetObject=${ACME_SERVICE1_ID}/>
Listing 8: Example of Object Association
636
3.1.7 Object References To Web Content
637
638
639
640
641
Any RegistryObject MAY reference web content that are maintained outside the registry using association
to an ExternalLink instance that contains the URL to the external web content. The following example
shows the ACME Organization with an Association to an ExternalLink instance which contains the URL to
ACMEs web site. The associationType of the Association MUST be of type ExternallyLinks as defined
by [ebRIM].
642
643
644
645
646
647
648
649
650
<rim:ExternalLink externalURI="http://www.acme.com"
id=${ACME_WEBSITE_EXTERNAL_ID}>
<rim:Association
id=${EXTERNALLYLINKS_ASSOCIATION_ID}
associationType=${CANONICAL_ASSOCIATION_TYPE_EXTERNALLY_LINKS_ID}
sourceObject=${ACME_WEBSITE_EXTERNAL_ID}
targetObject=${ACME_ORG_ID}/>
Listing 9: Example of Reference to Web Content Using ExternalLink
651
3.1.8 Object Packaging
652
653
654
655
RegistryObjects may be packaged or organized in a hierarchical structure using a familiar file and folder
metaphor. RegistryPackage instances serve as folders while RegistryObject instances serve as files in
this metaphor. A RegistryPackage instances groups logically related RegistryObject instances together as
members of that RegistryPackage.
656
657
658
The following example creates a RegistryPackage for Services offered by ACME Organization organized
in RegistryPackages according to the nature of the Service. Each Service is referenced using the
ObjectRef type defined by [ebRIM].
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
<rim:RegistryPackage
id=${ACME_SERVICES_PACKAGE_ID}>
<rim:RegistryObjectList>
<rim:ObjectRef id=${ACME_SERVICE1_ID}
id=${ACME_PURCHASING_SERVICES_PACKAGE_ID}>
<rim:ObjectRef id=${ACME_ PURCHASING_SERVICE1_ID}
<rim:ObjectRef id=${ACME_ PURCHASING_SERVICE2_ID}
</rim:RegistryPackage>
id=${ACME_HR_SERVICES_PACKAGE_ID}>
<rim:ObjectRef id=${ACME_ HR_SERVICE1_ID}
<rim:ObjectRef id=${ACME_ HR_SERVICE2_ID}
</rim:RegistryObjectList>
September 25, 2006

Page 19 of 76
676
Listing 10: Example of Object Packaging Using RegistryPackages
677
3.1.9 ExtrinsicObject
678
679
680
681
ExtrinsicObjects provide metadata that describes submitted content whose type is not intrinsically known
to the registry and therefore MUST be described by means of additional attributes (e.g., mime type).
Examples of content described by ExtrinsicObject include Collaboration Protocol Profiles, Business
Process descriptions, and schemas.
682
3.1.10 Service Description
683
684
685
Service description MAY be defined within the registry using the Service, ServiceBinding and
SpecificationLink classes defined by [ebRIM]. This MAY be used to publish service descriptions such as
WSDL and ebXML CPP/A.
686
3.2 Overview of [ebRS]
687
688
The [ebRS] specification defines the interfaces supported by an ebXML Registry and their bindings to
protocols such as SOAP and HTTP.
September 25, 2006

Page 20 of 76
689
4 Representing OWL Lite Constructs in ebRIM
690
691
692
693
694
695
It is important to note that although the mapping described in this section is complex, this complexity is
hidden from the ebXML registry user because the needed stored queries MUST already be available in
the Registry as described in Chapter 6. As this profile aims to enhance ebXML registry semantics without
causing any changes in the core ebXML Registry architecture specification [ebRIM], [ebRS], the stored
queries proposed in this specification SHOULD be submitted to the ebXML Registry by using the Stored
Query API of [ebRS].
696
697
The following ebRIM standard relational schema is used in coding the stored queries throughout this
document.
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
ClassScheme (id, home, lid, objectType, status, versionName, comment_,...);

ClassificationNode(accessControlPolicy, id, lid, home, objectType, code, parent,
path,versionName, comment_...)
Association(accessControlPolicy, id, lid, home, objectType, associationType,
sourceObject, targetObject, isConfirmedBySourceOwner,versionName, comment_
isConfirmedByTargetOwner,...)
Name_(charset, lang, value, parent,...)
Classification (id, objectType, lid, home, classificationNode, versionName,
comment_, classificationScheme, classifiedObject, nodeRepresentation,...);
ExtrinsicObject (id, lid, home, objectType,...)
714
ebXML Registry Relations
715
716
717
Detailed explanation on how to represent some of the OWL Lite constructs in ebRIM is available from
[Dogac, et. al. 2005]. Furthermore, [Dogac et. al. 2006] provides an implementation using the work
presented in this document for healthcare applications.
718
4.1 Representing RDF Schema Features in ebRIM
719
4.1.1 owl:Class rim:ClassificationNode
720
An owl:Class MUST be mapped to a rim:ClassificationNode as shown in the following examples:
721
722
723
724
725
726
727
728
729
730
731
732
733
734
<owl:Class rdf:ID="City">
</owl:Class>
Example owl:Class
<ClassificationScheme id=${GeographicalEntity}
name="GeographicalEntity/>
<rim:ClassificationNode id=${City} code='City'
parent=${GeographicalEntity}>
</rim:ClassificationNode>
Example Corresponding ebRIM construct ClassificationNode

A ClassificationScheme should be created for each ontology, and the classes belonging to this
ontology should be represented as the ClassificationNodes under this ClassificationScheme.
735
4.1.2 rdf:Property rim:Association Type HasProperty
736
737
A new ebRIM Association Type called HasProperty MUST be defined. The domain of an rdf:Property,
rdfs:domain, is the sourceObject in this Association Type and the range of an rdf:Property which is
September 25, 2006

Page 21 of 76
738
739
rdfs:range, is the targetObject of the Association Type. Consider the following example which defines an
rdf:Property instance called hasAirport" whose domain is City" and whose range is Airport" classes:
740
741
742
743
744
745
<rdf:Property rdf:ID="hasAirport">
<rdfs:domain rdf:resource="#City"/>
<rdfs:range rdf:resource="#AirPort"/>
</rdf:Property>
Example rdf:Property
746
747
748
749
750
751
752
<rim:Association id=${hasAirport}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:HasProperty'
sourceObject= ${city}
targetObject=${Airport} >
</rim:Association>
753
Example: ebRIM construct Association corresponding to rdf:Property
754
755
OWL specializes RDF Property to owl:ObjectProperty and owl:DatatypeProperty which are discussed in
the sections 4.3.1 and 4.3.2.
756
4.1.3 rdfs:subPropertyOf rim:Association Type SubPropertyOf
757
758
759
In OWL, properties can be organized into property hierarchies by declaring a property to be a

subPropertyOf another property. As shown in the following example, creditCardPayment property may
be a subPropertyOf the property paymentMethods:
760
761
762
763
<rdf:Property rdf:ID="creditCardPayment">
<rdfs:subPropertyOf rdf:Resource="#paymentMethods"/>
</rdf:Property>
764
Example rdfs:subPropertyOf
765
766
A new ebXML RIM Association Type called SubPropertyOf MUST be defined to represent
rdfs:subPropertyOf in ebRIM.
767
768
769
770
To express this semantics through ebXML RIM constructs, " creditCardPayment" Association is
associated with the "paymentMethods the newly created "SubPropertyOf" ebXML Association Type as
shown in the following:
771
772
773
774
775
776
<rim:Association id=${subPropertyOfID}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubPropertyOf'
sourceObject= ${creditCardPayment} targetObject=${paymentMethods} >
</rim:Association>
777
778
Such a semantic enhancement brings the following processing need: given a property, it should be
possible to retrieve all of its super properties as described in Section 6.1.
779
4.1.4 rdfs:subClassOf rim:Association Type SubClassOf
780
781
782
783
784
785
786
787
OWL relies on RDF Schema for building class hierarchies through the use of "rdfs:subClassOf" property
and allows multiple inheritance. In ebXML, a class hierarchy is represented by a ClassificationScheme. A
ClassificationScheme is constructed by connecting a ClassificationNode to its super class by using the
parent" attribute of the ClassificationNode. However it is not possible to associate a ClassificationNode
with more than one different super classes by using parent attribute. In other words, an ebXML Class
hierarchy has a tree structure and therefore is not readily available to express multiple inheritance. There
is a need for additional mechanisms to express multiple inheritance in ebXML RIM. Therefore, a new
Association Type called "SubClassOf" MUST be defined in the Registry.
September 25, 2006

Page 22 of 76
788
789
790
791
792
793
794
795
In the following OWL example, "AirReservationServices" service inherits both from "AirServices" service
and OWL-S ServiceProfile class.
<owl:Class rdf:ID="AirReservationServices">
<rdfs:subClassOf rdf:resource="http://www.daml.org/services/owls/1.0/Profile.owl#Profile"/>
<rdfs:subClassOf rdf:resource="#AirServices"/>
</owl:Class>
796
Example rdfs:subClassOf
797
798
799
800
To express this semantics through ebXML RIM constructs, "AirReservationServices" ClassificationNode is

associated both with the "OWL-S Profile" and "AirServices" ClassificationNodes through the "targetObject"
and "sourceObject" attributes of the two instances of the newly created "SubClassOf" ebXML Association
Type as shown in the following:
801
802
803
804
805
806
807
808
809
810
811
<rim:Association id=${subClassOf}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubClassOf'
sourceObject= ${AirReservationServices} targetObject=${OWL-S_Profile} >
</rim:Association>
<rim:Association id=${subClassOf2}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubClassOf'
sourceObject= ${AirReservationServices} targetObject=${AirServices} >
</rim:Association>
812
813
814
815
Once such a semantics is defined, there is a need to process the objects in the registry according to the
semantics implied; that is, given a class, it should be possible to retrieve all of its subclasses and/or all of
its super classes. By making the required adhoc queries available in the registry, this need can be readily
served as described in Sections 6.2, 6.3, 6.4 and 6.5.
816
4.1.5 owl:Individual rim:ExtrinsicObject
817
818
819
A class in OWL defines a group of individuals that belong together because they share some properties
[McGuinness, Harmelen]. For example, "TravelService" class may have the property "paymentMethod"
whose range may be "PossiblePaymentMethods" class as shown in the following example:
820
821
822
823
824
825
826
827
828
829
830
831
832
<owl:Class rdf:ID="TravelWebService">
</owl:Class>
<owl:ObjectProperty rdf:ID="paymentMethod">
<rdfs:domain rdf:resource="#TravelWebService"/>
<rdfs:range rdf:resource="#PossiblePaymentMethods"/>
</owl:ObjectProperty >
Example owl:Class example

In OWL, individuals are instances of classes. For example, an instance of "TravelWebService" class may
be "MyTravelWebService". Properties may be used to relate one individual to another. For example,
"MyTravelService" inherits "paymentMethod" property and this property may map to an instance of
"PossiblePaymentMethods" class, such as "Cash" as shown in the following example:
833
834
835
836
837
838
839
840
<TravelWebService rdf:ID="MyTravelWebService">
<paymentMethod> Cash </paymentMethod>
</TravelWebService>
Example owl:Individual example

In ebXML Registry the class instances can be stored in the Registry or in the Repository. This profile
recommends to store class instances in the Repository and to describe their metadata through
ExtrinsicObjects in the Registry.
September 25, 2006

Page 23 of 76
841
842
843
4.2 Representing OWL (In)Equality Constructs in ebXML RIM

4.2.1 owl:equivalentClass, owl:equivalentPropery rim:Association Type
EquivalentTo
848
849
850
In ebXML, the predefined "EquivalentTo" Association Type expresses the fact that the source
RegistryObject is equivalent to target RegistryObject. Therefore, "EquivalentTo" association MUST be
used to express "owl:equivalentClass" and "owl:equivalentProperty" properties since classes and
properties are all ebXML RegistryObjects.
The adhoc query for retrieving all the equivalent classes of a given ClassificationNode is represented in
Section 6.6. Additionally the adhoc query to retrieve all the equivalent properties (Association Type) of a
given property (Association Type) is presented in Section 6.7
851
4.2.2 owl:sameAs rim:Association Type SameAs
852
853
854
ebXML Registry contains the metadata of the objects stored in the repository. This profile recommends
that the instances to be stored in repository and to be represented through ExtrinsicObjects in the
registry.
855
856
owl:sameAs construct is used to indicate that two instances in a knowledge base are the same. This
construct may be used to create a number of different names that refer to the same individual.
844
845
846
847
857
858
859
860
<rdf:Description rdf:about="#MyAirReservationService">
<owl:sameAs rdf:resource="#THYAirReservationService"/>
</rdf:Description>
861
Example owl:sameAs
862
863
This translates into two "ExtrinsicObjects" in the ebXML registry to be the same. For this purpose a new
Association Type called "SameAs" MUST be defined in the ebXML registry.
864
865
866
867
868
869
<rim:Association id=${sameAs1} associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SameAs'

sourceObject= ${MyAirReservationService} targetObject=${THYAirReservationService}
>
</rim:Association>
Example Corresponding ebRIM construct Association
870
871
872
Furthermore, the adhoc query presented in Section 6.8 MUST be available in the registry to retrieve all
the "ExtrinsicObjects" defined to be the same with a given ExtrinsicObject.
873
4.2.3 owl:differentFrom rim:Association Type DifferentFrom
874
875
876
877
owl:differentFrom construct is used to indicate that two instances in a knowledge base are different from
one another. Explicitly stating that individuals are different can be important when using languages such
as OWL (and RDF) that do not assume that individuals have one and only one name [McGuinness,
Harmelen].
878
879
880
881
<rdf:Description rdf:about="#MyAirReservationService">
<owl:differentFrom rdf:resource="#THYAirReservationService"/>
</rdf:Description>
882
Example owl:differentFrom
883
884
885
This translates into declaring two "ExtrinsicObjects" in the ebXML registry to be different from each other.
For this purpose a new Association Type "DifferentFrom" MUST be defined in the ebXML registry to
explicitly indicate that the sourceRegistryObject is different from the targetRegistryObject.
September 25, 2006

Page 24 of 76
886
887
888
889
890
891
892
<rim:Association id=${differentFrom1}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DifferentFrom'
sourceObject= ${MyAirReservationService}
targetObject=${THYAirReservationService} >
</rim:Association>
893
The adhoc query presented in Section 6.9 can be used to process this semantics.
894
4.2.4 owl:AllDifferent
895
896
897
898
owl:AllDifferent is a special built-in OWL class, for which the property owl:distinctMembers is defined,
which links an instance of owl:AllDifferent to a list of individuals. The AllDifferent construct is particularly
useful when there are sets of distinct objects and when modelers are interested in enforcing the unique
names assumption within those sets of objects [McGuinness, Harmelen].
899
900
The following example states that the three instances of the WebService collection are all different from
one another:
901
902
903
904
905
906
907
<owl:AllDifferent>
<owl:distinctMembers rdf:parseType="Collection">
<WebService rdf:about="#MyCarService"/>
<WebService rdf:about="#MyFlightService"/>
<WebService rdf:about="#MyHotelService"/>
</owl:distinctMembers>
</owl:AllDifferent>
908
Example owl:AllDifferent
909
910
911
912
owl:AllDifferent SHOULD be represented in ebRIM as follows: the RegistryObjects under consideration

SHOULD be grouped as a RegistryPackage whose id is ${Collection}. Then the RegistryObjects in the
collection MUST be associated with this RegistryPackage with HasMember Association Type. One slot
of the registry package MUST be used to indicate that all members are different.
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
<rim:RegistryPackage id = ${Collection} >

<rim:Slot name=urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:packagetype>
<rim:ValueList>
<rim:Value>allDifferent</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Association id = ${HasMemberRegistryPackageAssoc1}
associationType = "urn:oasis:names:tc:ebxmlregrep:AssociationType:HasMember" sourceObject = ${Collection}
targetObject = ${MyCarService} />
associationType = "urn:oasis:names:tc:ebxml-regrep:HasMember"
sourceObject = ${Collection}
targetObject = ${MyFlightService} />
associationType = "urn:oasis:names:tc:ebxml-regrep:HasMember"
sourceObject = ${Collection}
targetObject = ${MyHotelService} />
Example Corresponding ebRIM Representation

The adhoc query presented in Section 6.10 can be used to process this semantics.
September 25, 2006

Page 25 of 76
937
4.3 Representing OWL Property Characteristics in ebRIM
938
4.3.1 owl:ObjectProperty rim:Association Type objectProperty
939
940
941
To represent OWL ObjectProperty in ebXML, a new type of Association called ObjectProperty" MUST be
defined. Consider the following example which defines an object property hasAirport" whose domain is
City" and whose range is Airport":
942
943
944
945
946
947
<owl:ObjectProperty rdf:ID="hasAirport">
<rdfs:domain rdf:resource="#City"/>
<rdfs:range rdf:resource="#AirPort"/>
</owl:ObjectProperty>
Example owl:ObjectProperty
948
949
950
951
952
953
<rim:Association id=${hasAirport} associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty'

sourceObject= ${City} targetObject=${Airport} >
</rim:Association>
954
955
956
Once such objectProperty definitions are stored in the ebXML registry, they can be retrieved through
ebXML query facilities by the user. The adhoc queries presented in Section 6.11 and 6.12 MUST be
available in the registry to facilitate this access.
957
4.3.2 owl:DatatypeProperty rim:Association Type DatatypeProperty
958
959
960
961
962
963
964
965
966
967
Similarly, to represent OWL DatatypeProperty in ebXML, a new Association Type called

DatatypeProperty" MUST be defined. Consider the following example which defines an datatype property
hasPrice" whose domain is the AirReservationServices" and whose range is XMLSchema
nonNegativeInteger". How OWL XML Schema types are handled in ebXML RIM is described in Section
4.9.
968
Example owl:DatatypeProperty
<owl:DatatypeProperty rdf:ID="hasPrice">
<rdfs:domain rdf:resource="#AirReservationServices"/>
<rdfs:range
rdf:resource="http://www.w3.org/2001/XMLSchema/nonNegativeInteger"/>
</owl:DatatypeProperty>
969
970
971
972
973
974
975
<rim:Association id=${hasPrice}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DatatypeProperty'
sourceObject= ${AirReservationServices}
targetObject=urn:www.w3.org:2001:XMLSchema:nonNegativeInteger >
</rim:Association>
976
977
978
The adhoc query presented in Section 6.14 MUST be available in the registry to facilitate the direct access
to datatype properties of a given classification node.
979
4.3.3 owl:TransitiveProperty rim:Association Type TransitiveProperty
980
981
982
In OWL, if a property, P, is specified as transitive then for any x, y, and z:P(x,y) and P(y,z) implies P(x,z)
[McGuinness, Harmelen]. Transitive property is a subproperty of ObjectProperty and MUST be defined as
a new Association Type called TransitiveProperty in ebRIM.
983
984
Consider the following example where "succeeds" is

TravelWebService" class:
defined
as
a transitive property of
985
September 25, 2006

Page 26 of 76
986
987
988
989
990
991
<owl:ObjectProperty rdf:ID="succeeds">
<rdf:type rdf:resource="&owl;TransitiveProperty" />
<rdfs:domain rdf:resource="#TravelWebService" />
<rdfs:range rdf:resource="#TravelWebService" />
Example owl:TransitiveProperty
992
993
994
995
996
997
998
999
1000
1001
1002
1003
<rim:Association id=${succeeds}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:TransitiveProperty'
sourceObject= ${TravelWebService} targetObject=${TravelWebService} >
</rim:Association>

Assume the following two definitions which declare three Web service instances from TravelWebService
class where "MyHotelAvailabilityService" service succeeds "MyAirReservationService" and
"MyInsuranceService" succeeds MyHotelAvailabilityService". Since "succeeds" is a transitive property, it
follows that "MyInsuranceService" succeeds "MyAirReservationService" although this fact is not explicitly
stated.
1004
1005
1006
1007
1008
1009
1010
1011
1012
<TravelWebService rdf:ID="MyHotelAvailabilityService">
<succeeds rdf:resource="#MyAirReservationService" />
</TravelWebService>
<TravelWebService rdf:ID="MyInsuranceService">
<succeeds rdf:resource="#MyHotelAvailabilityService" />
</TravelWebService>
Example owl:TransitiveProperty instances
1013
1014
1015
To make any use of this transitive property in ebXML registries, coding is necessary to find out the implied
information. The adhoc query presented in Section 6.16 MUST be available in the registry to handle this
semantics.
1016
4.3.4 owl:inverseOf rim:Association Type InverseOf
1017
1018
1019
In OWL, one property may be stated to be the inverse of another property. If the property P1 is stated to
be the inverse of the property P2, then if X is related to Y by the P2 property, then Y is related to X by the
P1 property [McGuinness, Harmelen].
1020
1021
1022
Consider, for example, the "succeeds" property defined in Section 4.3.3. To denote that a certain Web
service instance precedes another during execution, we may define the "precedes" property as an inverse
of the "succeeds" property as follows:
1023
1024
1025
1026
1027
<owl:ObjectProperty rdf:ID="precedes">
<owl:inverseOf rdf:resource="#succeeds" />
Example owl:inverseOf Property
1028
1029
1030
1031
1032
1033
<rim:Association id=${inverseOf1}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseOf'
sourceObject= ${precedes} targetObject=${succeeds} >
</rim:Association>
1034
1035
1036
1037
1038
Assume that we want to find all the Web services which can succeed a given Web service. In such a
case, we need not only find all the Web services which succeeds this given Web service, that is the target
objects of "succeeds" Association instance, but we also need to find all the sourceObjects of the
"precedes" Association instance since "precedes" is declared to be the "inverseOf" succeeds Association
September 25, 2006

Page 27 of 76
1039
instance. This can be achieved through the adhoc query presented in Section 6.19.
1040
1041
1042
1043
1044
Alternatively, one might use the additional semantics that this profile supports would be to cause inferred
information to be produced and stored along with new data as that new data was inserted into the reg/rep.
There is a trade off here: in this way, the extra work of inferring is only done at insertion/update time,
instead of at query time. However, an insertion or an update will require all the inferred data to be inserted
whether it will be used or not and hence will cause considerable maintenance overhead.
1045
4.3.5 owl:SymmetricProperty rim:Association Type SymmetricProperty
1046
1047
1048
1049
In OWL, if a property is symmetric, then if the pair (x,y) is an instance of the symmetric property P, then
the pair (y,x) is also an instance of P [McGuinness, Harmelen]. Symmetric property is a subproperty of
ObjectProperty in OWL. Consider the OWL class WebService and the complements symmetric
property:
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
<owl:Class rdf:ID="WebService">
<rdfs:subClassOf
rdf:resource="http://www.w3.org/2000/01/rdfschema#Resource"/>
</owl:Class>
<owl:SymmetricProperty rdf:ID="complements">
<rdfs:domain rdf:resource="#WebService"/>
<rdfs:range rdf:resource="#WebService"/>
</owl:SymmetricProperty>
Example owl:SymmetricProperty
<rim:Association id=${complements}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SymetricProperty'
sourceObject= ${WebService} targetObject=${WebService} >
</rim:Association>
1064
1065
1066
1067
1068
1069
Given that HotelReservationWebService complements AirReservationWebService, it is possible to

deduce that AirReservationWebService complements HotelReservationWebService.
owl:SymmetricProperty MUST be defined as a new type of Association in ebRIM called
SymmetricProperty. Furthermore the adhoc query presented in Section 6.20 MUST be available in the
Registry to retrieve symmetric Associations of a ClassificationNode.
1070
4.3.6 owl:FunctionalProperty rim:Association Type FunctionalProperty
1071
1072
1073
1074
In OWL, if a property is a FunctionalProperty, then it has no more than one value for each individual (it
may have no values for an individual) [McGuinness, Harmelen]. The range of a FunctionalProperty can be
either an Object or a datatype. Consider, for example, the hasPrice Functional property which has a
unique price:
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
<owl:DatatypeProperty rdf:ID="hasPrice">
<rdf:type rdf:resource="&owl;FunctionalProperty" />
<rdfs:range
rdf:resource="http://www.w3.org/2001/XMLSchema/nonNegativeInteger"/>
</owl:DatatypeProperty>
Example owl:FunctionalProperty
<rim:Association id=${hasPrice}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:FunctionalProperty'
sourceObject= ${AirReservationServices}
targetObject=${uurn:www.w3.org:2001:XMLSchema:nonNegativeInteger} >
</rim:Association>
September 25, 2006

Page 28 of 76
1089
1090
1091
ebXML RIM MUST contain a new Association Type called FunctionalProperty to express this semantics.
Furthermore the he adhoc query presented in Section 6.21 MUST be available in the Registry to retrieve
functional Associations of a ClassificationNode.
1093
4.3.7 owl:InverseFunctionalProperty rim:Association Type

1094
1095
1096
1097
1098
1099
In OWL, if a property is inverse functional then the inverse of the property is functional. Thus the inverse
of the property has at most one value for each individual [McGuinness, Harmelen]. InverseFunctional
properties (IFPs) are like keys. An individual filling the range role in an inverseFunctional property
instance identifies the individual in the domain role of that same property instance. In other words, if a
semantic web tool encounters two individuals with the same value for an inverseFunctional property, it
can be inferred that they are actually the same individual.
1100
1101
As an example, the ObjectProperty finalDestination indicates that each flight arrives to only one airport
as its final destination.
1092
1102
1103
1104
1105
1106
<owl:ObjectProperty rdf:ID="finalDestination">
<rdf:type rdf:resource="&owl;InverseFunctionalProperty" />
<rdfs:domain rdf:resource="#Airport"/>
<rdfs:range rdf:resource="#Flight"/>
1107
Example owl:InverseFunctionalProperty
1108
1109
1110
1111
1112
<rim:Association id=${finalDestination}
associationType='urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseFunctionalProperty'
sourceObject= ${Airport} targetObject=${Flight} >
</rim:Association>
1113
1114
1115
1116
ebRIM MUST contain a new Association Type called InverseFunctionalProperty to express this
semantics. Furthermore the adhoc query presented in Section 6.22 MUST be available in the Registry to
retrieve inverse functional Associations of a ClassificationNode.
1117
4.4 OWL Property Restrictions in ebXML RIM
1118
1119
1120
1121
1122
An important construct of OWL is "owl:Restriction". In RDF, a property has a global scope, that is, no
matter what class the property is applied to, the range of the property is the same. "owl:Restriction", on the
other hand, has a local scope; restriction is applied on the property within the scope of the class where it is
defined. This makes property definitions more reusable by factoring out class specific characteristics of
the property into the class description.
1123
1124
1125
1126
For example, we may define a property "paymentMethod" for travel Web services in general and we may
state that the range of this property is the class "PossiblePaymentMethods". Then, for
"AirReservationServices", we may wish to restrict "paymentMethod" property to, say, "CreditCard" class as
demonstrated in the following two examples:
1127
1128
1129
1130
1131
1132
<owl:ObjectProperty rdf:ID="paymentMethod">
<rdfs:domain rdf:resource="#TravelWebService"/>
<rdfs:range rdf:resource="#PossiblePaymentMethods"/>
Example owl:ObjectProperty paymentMethod
1133
1134
1135
1136
1137
1138
1139
1140
<rdfs:subClassOf>
<owlRestriction>
<owl:onProperty rdf:resource="#paymentMethod"/>
<owl:allValuesFrom rdf:resource= "#CreditCard"/>
</owl:Restriction>
</rdfs:subClassOf>
September 25, 2006

Page 29 of 76
1141
1142
1143
1144
1145
1146
1147
1148
1149
</owl:Class>
Example owl:Restriction on ObjectProperty paymentMethod

A new Association Type of restriction SHOULD be defined to represent OWL restriction. A slot of this
Association Type SHOULD indicate the whether the restriction is allValuesFrom or someValuesFrom.
When such restriction is submitted to the system, the registry MUST create a new Association instance,
say, paymentMethod_1 of AssociationType ObjectProperty is created whose sourceObject is
"AirReservationServices" and the targetObject is "CreditCard". paymentMethod_1 Association instance
is related with the paymentMethod Association instance by using an instance of the Association Type
Restriction as shown in the following example:
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
<rim:Association id = ${paymentMethod_1}
associationType =
"urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty"
sourceObject = ${AirReservationServices}
targetObject = ${CreditCard}>
</rim:Association>
<rim:Association id = ${paymentMethodRestriction}
associationType =
"urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:Restriction"
sourceObject = ${paymentMethod}
targetObject = ${paymentMethod_1}>
<rim:Slot name="urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:restrictionType">
<rim:ValueList>
<rim:Value>allValuesFrom</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:Association>
1172
Example Handling owl:Restriction in ebXML Registry
1173
1174
1175
Obviously, this serves the purpose of reusing the "paymentMethod" property. Otherwise, a new property
"paymentMethodCC" can be defined between "AirReservationServices" and the "CreditCard" classes as
shown in the following:
1176
1177
1178
1179
1180
1181
<owl:ObjectProperty rdf:ID="paymentMethodCC">
<rdfs:range rdf:resource="#CreditCard"/>
Example owl:ObjectProperty paymentMethodCC
1182
4.5 Representing OWL Restricted Cardinality in ebXML RIM
1183
4.5.1 owl:minCardinality (only 0 or 1)
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
In OWL, cardinality is stated on a property with respect to a particular class. If a minCardinality of 1 is

stated on a property with respect to a class, then any instance of the class will have at least one value for
the restricted property. This restriction is another way of saying that the property is required to have a
value for all instances of the class. In OWL Lite, the only minimum cardinalities allowed are 0 or 1. A
minimum cardinality of zero on a property just states (in the absence of any more specific information)
that the property is optional with respect to a class [McGuinness, Harmelen].
Consider for example the following OWL code which states that each instance of a WebService class
must have at least one price:
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#hasPrice"/>
September 25, 2006

Page 30 of 76
1196
1197
1198
1199
1200
<owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">
1 </owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
1201
Example owl:minCardinality
1202
1203
In ebXML RIM, cardinalities of Association Types MUST be defined by associating a minCardinality slot
with the Association Types as shown in the following example:
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
<rim:Association id = ${hasPriceMinCardinalityRestriction}
associationType = "urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty"
sourceObject = ${WebService}
targetObject = ${Price}>
<rim:Name>
<rim:LocalizedString value = 'hasPrice' />
</rim:Name>
<rim:Slot name="urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:minCardinality">
<rim:ValueList>
<rim:Value>1</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:Association>
1220
Example Representing owl:minCardinality in ebRIM
1221
4.5.2 owl:maxCardinality (only 0 or 1)
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
In OWL, cardinality is stated on a property with respect to a particular class. If a maxCardinality of 1 is

stated on a property with respect to a class, then any instance of that class will be related to at most one
individual by that property. A maxCardinality 1 restriction is sometimes called a functional or unique
property. It may be useful to state that certain classes have no values for a particular property. This
situation is represented by a maximum cardinality of zero on the property [McGuinness, Harmelen].
can have at most one price:
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="&xsd;nonNegativeInteger">
1 </owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
1238
Example owl:maxCardinality
1239
1240
In ebXML RIM, cardinalities of Association Types MUST be defined by associating a maxCardinality slot
with the Association Types as shown in the following example:
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
<rim:Association id = ${hasPriceMaxCardinalityRestriction}
sourceObject = ${WebService}"
<rim:Name>
</rim:Name>
<rim:Slot name="urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:maxCardinality">
<rim:ValueList>
September 25, 2006

Page 31 of 76
1253
1254
1255
1256
</rim:ValueList>
</rim:Slot>
</rim:Association>
1257
Example Representing owl:maxCardinality in ebRIM
1258
4.5.3 owl:cardinality (only 0 or 1)
1259
1260
1261
In OWL Lite, cardinality is provided as a convenience when it is useful to state that a property on a class
has both minCardinality 0 and maxCardinality 0 or both minCardinality 1 and maxCardinality 1
[McGuinness, Harmelen].
1262
1263
must have exactly one price:
1264
1265
1266
1267
1268
1269
1270
1271
1272
<rdfs:subClassOf>
<owl:Restriction>
<owl:Cardinality rdf:datatype="&xsd;nonNegativeInteger"> 1
</owl:Cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
1273
Example owl:Cardinality
1274
1275
In ebXML RIM, cardinalities of Association Types MUST be defined by associating a Cardinality slot with
the Association Types as shown in the following example:
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
<rim:Association id = ${hasPriceCardinalityRestriction}
sourceObject = ${WebService}
<rim:Name>
</rim:Name>
<rim:Slot name="urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:cardinality">
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:Association>
1292
Example Representing owl:Cardinality in ebRIM
1293
4.6 Representing OWL Class Intersection in ebXML RIM
1294
1295
1296
1297
OWL provides the means to manipulate class extensions using basic set operators. In OWL lite, only
owl:intersectionOf is available which defines a class that consists of exactly all objects that belong to all
the classes specified in the intersection definition. In the following example, "AirReservationServices" is
defined as the intersection of "AirServices" and "ReservationServices":
1298
1299
1300
1301
1302
1303
1304
1305
1306
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class rdf:about="#AirServices" />
<owl:Class rdf:about="#ReservationServices" />
</owl:intersectionOf>
</owl:Class>
Example owl:intersectionOf
In ebXML RIM "owl:intersectionOf" set operator MUST be represented as follows:
September 25, 2006

Page 32 of 76
1307
A new ClassificationNode is created for representing the complex class.
1308
1309
1310
The id's of the classes that are involved in the intersection definition are put as the values of the
multi-valued slot named as: urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:intersectionOf.
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
<rim:ClassificationNode id = ${AirReservationServices} code =

"AirReservationServices>
<rim:Slot name=urn:oasis:names:tc:ebxmlregrep:profile:webontology:slot:intersectionOf>
<rim:ValueList>
<rim:Value>${AirServices}</rim:Value>
<rim:Value>${ReservationServices}</rim:Value>
</rim:ValueList>
</rim:Slot>
1323
Example Defining Intersection of ClassificationNodes in ebRIM
1324
1325
1326
1327
1328
When such a representation is used to create a complex class (a new ClassificationNode) in RIM, it
becomes possible to infer that the objects (instances) classified by all
of the classes
(ClassificationNodes) specified in the Intersection definition, are also classified by this complex class. The
adhoc query presented in Section 6.23 MUST be available in the ebXML Registry to retrieve the direct
instances of the complex class and also the instances of the intersection of the classes.
1329
1330
4.7 Representing OWL Versioning in ebXML RIM
1331
4.7.1 owl:versionInfo, owl:priorVersion
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
An owl:versionInfo statement generally has as its object a string giving information about this version, for
example RCS/CVS keywords. This statement does not contribute to the logical meaning of the ontology
other than that given by the RDF(S) model theory [McGuinness, Harmelen].
An owl:priorVersion statement contains a reference to another ontology. This identifies the specified
ontology as a prior version of the containing ontology [McGuinness, Harmelen].
In ebXML, since a RegistryObject MAY have several versions, a logical id (called lid) is also defined which
is unique for different logical objects. However the lid attribute value MUST be the same for all versions of
the same logical object. Therefore, almost for all the RegistryObjects the version information is kept
through versionName and comment attributes of the VersionInfo ebRIM Class.
owl:version information MUST be stored in the versionName and comment attributes of the
VersionInfo ebRIM class.
It should be noted that in freebXML implementation the versionInfo is flattened and the versionName
and comment_ are provided as direct attributes of database tables.
<owl:Ontology rdf:about="">
<owl:versionInfo>v 1.17 2003/02/26 12:56:51 </owl:versionInfo>
</owl:Ontology>
Example owl:versionInfo
<rim:ClassificationScheme
lid= ${exampleOntology}
id=${exampleOntology} isInternal="true"
nodeType="urn:oasis:names:tc:ebxml-regrep:NodeType:UniqueCode">
<rim:versionInfo>
<rim:versionName>
<rim:LocalizedString charset="UTF-8" value="v 1.17 2003/02/26
12:56:51"/>
</rim:versionName>
</rim:versionInfo>
</rim:ClassificationScheme>
September 25, 2006

Page 33 of 76
1360
Example rim:versionName
1361
4.8 Representing OWL Annotation Properties in ebXML RIM
1362
4.8.1 rdfs:label
1363
1364
1365
1366
rdfs:label is an instance of rdf:Property that may be used to provide a human-readable version of a

resource's name [Brickley, Guha].
In ebXML RIM, human readable names of resources are provided through rim:Name. rdfs:label MUST be
expressed through rim:Name.
1367
1368
1369
1370
1371
<rdfs:label>Air Reservation Services</rdfs:label>
</owl:Class>
Example rdfs:label
1372
1373
1374
1375
1376
1377
1378

'AirReservationServices'>
<rim:Name>
<rim:LocalizedString value = 'Air Reservation Services' />
</rim:Name>
1379
Example rim:Name
1380
4.8.2 rdfs:comment
1381
1382
1383
rdfs:comment is an instance of rdf:Property that may be used to provide a human-readable description of

a resource [Brickley, Guha].
In ebXML RIM, this construct MUST be expressed through rim:Description.
1384
1385
1386
1387
1388
1389
<rdfs:comment>Open Travel Alliance Air Reservation Services
</rdfs:comment>
</owl:Class>
Example rdfs:comment
1390
1391
1392
1393
1394
1395
1396
1397

<rim:Description>
<rim:LocalizedString value = 'Open Travel Alliance Air
Reservation Services'/>
</rim:Description>
1398
Example: rim:Description
1399
4.8.3 rdfs:seeAlso
1400
1401
rdfs:seeAlso is an instance of rdf:Property that is used to indicate a resource that might provide additional
information about the subject resource [Brickley, Guha].
1402
1403
This construct MUST be expressed in ebXML RIM by defining a new Association Type called SeeAlso to
express this semantics.
1404
1405
1406
<rdfs:seeAlso rdf:resource="http://www.opentravel.org" />
September 25, 2006

Page 34 of 76
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
</owl:Class>
Example rdfs:seeAlso
<rim:ExternalLink id = ${exampleExternalLink}
externalURI= "http://www.opentravel.org" >
</rim:ExternalLink>
<rim:Association id = ${seeAlsoID}
associationType = 'urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SeeAlso'
targetObject = ${exampleExternalLink} />
1422
Example rim:seeAlsoExternalLink
1423
4.9 OWL Datatypes in ebXML RIM
1424
1425
1426
OWL allows the use of XML Schema datatypes to describe part of the datatype domain by simply
including their URIs within an OWL ontology [McGuinness, Harmelen]. In ebXML, XML Schema datatypes
MAY be used by providing an external link from the registry.
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
The following example demonstrates how XML Schema datatype integer can be referenced through an
ExternalLink whose id is
'urn:www.w3.org:2001:XMLSchema:integer' and how to define a
DatatypeProperty, namely, hasPrice, whose target object is the defined to be ExternalLink 'integer':
1443
<rim:ExternalLink id = urn:www.w3.org:2001:XMLSchema:integer
externalURI="http://www.w3.org/2001/XMLSchema#integer" >
<rim:Name> <rim:LocalizedString value = "XML Schema integer"/>
</rim:Name>
</rim:ExternalLink>
<rim:Association id = ${hasPrice} associationType =
'urn:oasis:names:tc:ebxmlregrep:AssociationType:DatatypeProperty'
targetObject = urn:www.w3.org:2001:XMLSchema:integer >
<rim:Name> <rim:LocalizedString value ="hasPrice"/></rim:Name>
</rim:Association>
September 25, 2006

Page 35 of 76
1444
5 Cataloging Service Profile
1445
1446
The ebXML Regitsry provides the ability for a content cataloging service to be configured for any type of
content. The cataloging service serves the following purposes:
1447
1448
1449
Automates the mapping from the source information model (in this case OWL) to ebRIM. This
hides the complexity of the mapping from the OWL publisher and eliminates the need for any
special UI tools to be provided by the registry implementor for publishing OWL documents.
1450
1451
1452
Selectively converts content into ebRIM compatible metadata when the content is cataloged after
being published. The generated metadata enables the selected content to be used as
parameter(s) in content specific parameterized queries.
1453
This section describes the cataloging service for cataloging OWL content.
1454
1455
An OWL document, when published to an ebXML Registry implementing the OWL Profile, MUST be
cataloged as specified in this section using a OWL Content Cataloging Service as defined by [ebRS].
1456
5.1 Invocation Control File
1457
1458
The OWL cataloging service MAY optionally support an invocation control file that declaratively specifies
the transforms necessary to catalog published OWL documents.
1459
5.2 Input Metadata
1460
1461
The OWL cataloging service MUST be pre-configured to be automatically invoked when the following
types of metadata are published, as defined by the [ebRS] specifications.
1462
These are the only types of metadata that MAY describe a OWL document being published:
An ExtrinsicObject whose ObjectType references the canonical OWL ClassificationNode

specified in Section 7. The ExtrinsicObject MUST have an OWL document as its RepositoryItem.
An ExternalLink whose ObjectType references the canonical OWL ClassificationNode specified in

Section 7. In case of ExternalLink the OWL document MUST be resolvable via a URL described
by the value of the externalURI attribute of the ExternalLink. Recall that, in the ExternalLink case
the OWL document is not stored in the repository.
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
<rim:ExtrinsicObject id=urn:acmeinc:ebxml:registry:3.0:owl>
...
<rim:ExtrinsicObject>
Example of ExtrinsicObject Input Metadata
1473
1474
1475
1476
1477
1478
1479
1480
<rim:ExternalLink
id=urn:acmeinc:ebxml:registry:3.0:owl
externalURI=http://www.acme.com/owl/ebXMLRegistryService.owl
>
...
<rim:ExternalLink>
Example of ExternalLink Input Metadata
1481
1482
5.3 Input Content
1483
1484
1485
The OWL cataloging service expects an OWL document as its input content. The input content MUST be
processed by the OWL cataloging service regardless of whether it is a RepositoryItem for an
ExtrinsicObject or whether it is content external to repository that is referenced by an ExternalLink.
1486
September 25, 2006

Page 36 of 76
1487
5.4 Output Metadata
1488
This section describes the metadata produced by the OWL cataloging service produces as output.
1489
5.4.1 owl:Class rim:ClassificationNode
1490
1491
1492
The OWL Cataloging service MUST automatically produce a rim:ClassificationNode instance for each
owl:class element within the input OWL or its imports, as specified in the owl:Class
rim:ClassificationNode mapping earlier in this document.
1493
5.4.2 rdf:Property rim:Association Type HasProperty
1494
1495
1496
The OWL Cataloging service MUST automatically produce an rim:Association instance with
associationType HasProperty for each rdf:Property element within the input OWL or its imports, as
specified in the rdf:Property rim:Association Type HasProperty mapping earlier in this document.
1497
5.4.3 rdfs:subPropertyOf rim:Association Type SubPropertyOf
1498
1499
1500
1501
associationType SubPropertyOf for each rdfs:subPropertyOf element within the input OWL or its imports,
as specified in the rdfs:subPropertyOf rim:Association Type SubPropertyOf mapping earlier in this
document.
1502
5.4.4 rdfs:subClassOf rim:Association Type subClassOf
1503
1504
1505
associationType subClassOf for each rdfs:subClassOf element within the input OWL or its imports, as
specified in the rdfs:subClassOf rim:Association Type subClassOf mapping earlier in this document.
1506
5.4.5 owl:Individual rim:ExtrinsicObject
1507
1508
1509
The OWL Cataloging service MUST automatically produce rim:ExtrinsicObject instances for each
owl:Individual element within the input OWL or its imports, as specified in the owl:Individual
rim:ExtrinsicObject mapping earlier in this document.
1511
5.4.6 owl:equivalentClass, owl:equivalentPropery rim:Association Type

EquivalentTo
1512
1513
1514
1515
The OWL Cataloging service MUST automatically produce rim:Association instances with
associationType EquivalentTo for each owl:equivalentClass or owl:equivalentProperty element within the
input OWL or its imports, as specified in the owl:equivalentClass, owl:equivalantProperty
rim:Association Type EquivalantTo mapping earlier in this document.
1516
5.4.7 owl:sameAs rim:Association Type SameAs
1517
1518
1519
associationType SameAs for each owl:sameAs element within the input OWL or its imports, as specified
in the owl:sameAs rim:Association Type SameAs mapping earlier in this document.
1520
5.4.8 owl:differentFrom rim:Association Type DifferentFrom
1521
1522
1523
1524
associationType DifferentFrom for each owl:differentFrom element within the input OWL or its imports, as
specified in the owl:differentFrom rim:Association Type DifferentFrom mapping earlier in this
document.
1525
5.4.9 owl:AllDifferent rim:RegistryPackage
1526
The OWL Cataloging service MUST automatically produce rim:RegistryPackage instances for each
1510
September 25, 2006

Page 37 of 76
1527
1528
owl:AllDifferent element within the input OWL or its imports, as specified in the owl:AllDifferent
rim:RegistryPackage mapping earlier in this document.
1529
5.4.10 owl:ObjectProperty rim:Association Type ObjectProperty
1530
1531
1532
1533
associationType ObjectProperty for each owl:ObjectProperty element within the input OWL or its imports,
as specified in the owl:ObjectProperty rim:Association Type ObjectProperty mapping earlier in this
document.
1534
5.4.11 owl:DatatypeProperty rim:Association Type DatatypeProperty
1535
1536
1537
1538
associationType datatypeProperty for each owl:DatatypeProperty element within the input OWL or its
imports, as specified in the owl:DatatypeProperty rim:Association Type datatypeProperty mapping
earlier in this document.
1539
5.4.12 owl:TransitiveProperty rim:Association Type TransitiveProperty
1540
1541
1542
1543
associationType TransitiveProperty for each owl:TransitiveProperty element within the input OWL or its
imports, as specified in the owl:TransitiveProperty rim:Association Type TransitiveProperty mapping
1544
5.4.13 owl:inverseOf rim:Association Type InverseOf
1545
1546
1547
associationType InverseOf for each owl:inverseOf element within the input OWL or its imports, as
specified in the owl:inverseOf rim:Association Type InverseOf mapping earlier in this document.
1548
5.4.14 owl:SymmetricProperty rim:Association Type SymetricProperty
1549
1550
1551
1552
associationType SymetricProperty for each owl:SymetricProperty element within the input OWL or its
imports, as specified in the owl:SymetricProperty rim:Association Type SymetricProperty mapping
1553
5.4.15 owl:FunctionalProperty rim:Association Type FunctionalProperty
1554
1555
1556
1557
associationType FunctionalProperty for each owl:FunctionalProperty element within the input OWL or its
imports, as specified in the owl:FunctionalProperty rim:Association Type FunctionalProperty mapping
1559
5.4.16 owl:InverseFunctionalProperty rim:Association Type

1560
1561
1562
1563
associationType InverseFunctionalProperty for each owl:InverseFunctionalProperty element within the
input OWL or its imports, as specified in the owl:InverseFunctionalProperty rim:Association Type
InverseFunctionalProperty mapping earlier in this document.
1564
5.4.17 owl:minCardinality (only 0 or 1)
1565
1566
1567
The OWL Cataloging service MUST automatically add a slot with name minCardinality to the relevant
rim:Association instances for each owl:minCardinality element within the input OWL or its imports, as
specified in section 4.5.1 where how to represent owl:minCardinality is described.
1558
September 25, 2006

Page 38 of 76
1568
5.4.18 owl:maxCardinality (only 0 or 1)
1569
1570
1571
The OWL Cataloging service MUST automatically add a slot with name maxCardinality to the relevant
rim:Association instances for each owl:maxCardinality element within the input OWL or its imports, as
specified in section 4.5.2 where how to represent owl:maxCardinality is described.
1572
5.4.19 owl:cardinality
1573
1574
1575
The OWL Cataloging service MUST automatically add a slot with name cardinality to the relevant
rim:Association instances for each owl:cardinality element within the input OWL or its imports, as
specified in section 4.5.3 where how to represent owl:cardinality is described.
1576
5.4.20 owl:intersectionOf
1577
1578
1579
The OWL Cataloging service MUST automatically produce a rim:RegistryPackage and a rim:Association
instances with type IntersectionOf for each owl:intersectionOf element within the input OWL or its imports,
as specified in section 4.6 where how to represent owl:intersectionOf is described.
1580
5.4.21 rdfs:label
1581
1582
1583
The OWL Cataloging service MUST automatically produce a rim:Name instance for each rdfs:label
element within the input OWL or its imports, as specified in section 4.8.1 where how to represent
rdfs:label is described.
1584
5.4.22 rdfs:comment
1585
1586
1587
The OWL Cataloging service MUST automatically produce a rim:Description instance for each
rdfs:comment element within the input OWL or its imports, as specified in section 4.8.2 where how to
represent rdfs:comment is described.
1588
5.4.23 rdfs:seeAlso
1589
1590
1591
The OWL Cataloging service MUST automatically produce a rim:ExternalLink and a rim:Association with
type SeeAlso instances for each rdfs:seeAlso element within the input OWL or its imports, as specified in
section 4.8.3 where how to represent rdfs:seeAlso is described.
September 25, 2006

Page 39 of 76
1592
6 Discovery Profile
1593
1594
1595
1596
1597
1598
The ebXML Registry provides the ability for a user defined parameterized queries to be configured for
each type of content. The queries may be as complex or simple as the discovery use case requires. The
complexity of the parameterized queries may hidden from the registry client by storing them within the
ebXML Registry as instances of the AdhocQuery class, and being invoked by simply providing their
parameters. Query parameters are often pattern strings that may contain wildcard characters '%'
(matches any number of characters) and '_' (matches exactly one character) as described by [ebRS].
1599
1600
An ebXML Registry SHOULD provide a graphical user interface that displays any configured
parameterized query as a form which contains an appropriate field for entering each query parameter.
1601
1602
1603
This chapter defines the queries that MUST be supported by an ebXML Registry implementing the OWL
Profile for processing the semantics provided in the OWL content. An implementation MAY also support
additional discovery queries for OWL content, some of which have already identified in this section.
1604
1605
The queries defined in this chapter are parameterized queries stored in the Registry as instances of the
AdhocQuery type, in the same manner as any other RegistryObject.
1606
1607
1608
1609
In the subsequent section each query is described simply in terms of its supported parameters that serve
as its search criteria. The actual AdhocQuery instances are much more complex in comparison but they
are not exposed to the client making the query. Details on these queries are specified canonically in
section 7.3 .
1610
1611
1612
1613
1614
Some of the queries that are necessary to process the semantics involved in OWL documents requires
SQL recursion mechanism which is available through SQL 99 Standard. Since SQL 92, does not support
recursion mechanism, those queries are stated to be implemented optionally. Additionally for these types
of discovery queries, references to the stored procedures are presented in Section 7.3 for the interested
users.
1615
6.1 All SuperProperties Discovery Query
1620
1621
1622
1623
1624
As presented in Section 4.1.3, a new ebXML RIM Association Type called SubPropertyOf MUST be
defined to represent rdfs:subPropertyOf in ebRIM. Such a semantic enhancement brings the following
processing need: given a property, it should be possible to retrieve all of its super properties. This requires
a recursion mechanism in SQL queries.
The AllSuperProperties discovery query MAY be implemented by an ebXML Registry implementing this
profile. It allows the discovery of all super properties of a given property instance (Association instance in
ebXML terminology) recursively in a property hierarchy (hierarchy of Association Types) in an ebXML
Registry implementation supporting recursion. The canonical query corresponding to this discovery query
is presented in Section 7.3.1.
1625
6.1.1 Parameter $propertyName
1626
1627
This parameter's value SHALL specify a string containing a pattern to match against the name attribute
value of Associations that have associationType of Property.
1628
6.1.2 Example of All SuperProperties Discovery Query
1629
1630
The following example illustrates how to find all the super properties of a given property having a name
containing creditCardPayment if the query is implemented as an AdHoc Query.
1616
1617
1618
1619
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
<rs:RequestSlotList>
<rim:Slot
name="urn:oasis:names:tc:ebxmlregrep:3.0:rs:AdhocQueryRequest:queryId">
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllSuperProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
September 25, 2006

Page 40 of 76
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
<rim:Slot name="urn:oasis:names:tc:ebxmlregrep:rs:AdhocQueryRequest:queryId">
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllSuperProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="$propertyName">
<rim:ValueList>
<rim:Value>%creditCardPayment%</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">
</rim:QueryExpression>
</rim:AdhocQuery>
Example of All SuperProperties Discovery Query
1664
6.2 Immediate SuperClass Discovery Query
1665
1666
1667
The Immediate SuperClass discovery query MUST be implemented by an ebXML Registry implementing
this profile. It allows the discovery of all of the immediate super classes of a given class. The canonical
query corresponding to this discovery query is presented in Section7.3.2.
1668
6.2.1 Parameter $className
1669
1670
value of ClassificationNodes.
1671
6.2.2 Example of Immediate SuperClass Discovery Query
1672
1673
The following example illustrates how to find all the immediate super classes of a given class that have a
name containing the string AirReservationServices .
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSuperClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSuperClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="$className">
<rim:ValueList>
<rim:Value>%AirReservationServices%</rim:Value>
</rim:ValueList>
</rim:Slot>
September 25, 2006

Page 41 of 76
1699
1700
1701
1702
1703
1704
1705
</rim:AdhocQuery>
Example of Immediate SuperClass Discovery Query
1706
6.3 Immediate SubClass Discovery Query
1707
1708
1709
The Immediate SubClass discovery query MUST be implemented by an ebXML Registry implementing
this profile. It allows the discovery of all of the immediate subclasses of a given class. The canonical
query corresponding to this discovery query is presented in Section 7.3.3.
1710
1711
1712
value of ClassificationNode.
1713
6.3.2 Example of Immediate SubClasss Discovery Query
1714
1715
The following example illustrates how to find all the immediate subclasses of a given class that have a
name containing the string AirServices .
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSubClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSubClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>%AirServices%</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of Immediate SubClass Discovery Query
1748
6.4 All SuperClasses Discovery Query
1749
1750
1751
It should be noted that, given a class, finding its immediate subclasses, super classes is necessary but
not sufficient. Given a class, it should be possible to retrieve all of its subclasses, and all of its super
classes. This requires a recursion mechanism in SQL queries.
September 25, 2006

Page 42 of 76
1752
1753
1754
1755
The All SuperClasses discovery query MAY be implemented by an ebXML Registry implementing this
profile. It allows the discovery of all super classes of a given ClassificationNode recursively in an ebXML
1756
1757
1758
1759
6.4.2 Example of All SuperClasses Discovery Query
1760
1761
The following example illustrates how to find all the super classes of a given class recursively that have a
name containing the string AirReservationServices if the query is implemented as an Adhoc Query .
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllSuperClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllSuperClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of All SuperClasses Discovery Query
1794
6.5 All SubClasses Discovery Query
1795
1796
1797
1798
The All SubClasses discovery query MAY be implemented by an ebXML Registry implementing this
profile. It allows the discovery of all subclasses of a given ClassificationNode recursively in an ebXML
1799
1800
1801
1802
6.5.2 Example of All SubClassses Discovery Query
1803
The following example illustrates how to find all the subclasses of a given class recursively that have a
September 25, 2006

Page 43 of 76
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
name containing the string AirServices , if the query is implemented as an Adhoc Query.
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllSubClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllSubClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of All SubClasses Discovery Query
1837
6.6 EquivalentClasses Discovery Query
1838
1839
The EquivalentClasses discovery query MUST be implemented by an ebXML Registry implementing this
profile. It allows the discovery of all the equivalent classes of a given ClassificatioNode.
1840
1841
1842
1843
6.6.2 Example of EquivalentClasses Discovery Query
1844
1845
The following example illustrates how to find all the equivalent classes of a given class that have a name
containing the string AirServices .
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentClasses</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentClasses</rim:Value>
</rim:ValueList>
September 25, 2006

Page 44 of 76
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of Equivalent Classes Discovery Query
1878
6.7 EquivalentProperties Discovery Query
1879
1880
1881
1882
The EquivalentProperties discovery query MUST be implemented by an ebXML Registry implementing

this profile. It allows the discovery of all the equivalent properties of a given Association that have
associationType of Property. The canonical query corresponding to this discovery query is presented in
Section 7.3.7.
1883
1884
1885
value of Associations that have associationType of Property
1886
6.7.2 Example of EquivalentProperties Discovery Query
1887
1888
The following example illustrates how to find all the equivalent properties(Association Type) of a given
property (Association Type) that have a name containing the string paymentMethods .
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>%paymentMethods%</rim:Value>
</rim:ValueList>
</rim:Slot>
September 25, 2006

Page 45 of 76
1918
1919
1920
</rim:AdhocQuery>
Example of Equivalent Properties Discovery Query
1921
6.8 SameExtrinsicObjects Discovery Query
1922
1923
1924
The SameExtrinsicObjects discovery query MUST be implemented by an ebXML Registry implementing

this profile. It allows the discovery of all the "ExtrinsicObjects" defined to be the same with a given
ExtrinsicObject. The canonical query corresponding to this discovery query is presented in Section 7.3.8.
1925
6.8.1 Parameter $extrinsicObjectName
1926
1927
value of ExtrinsicObjects.
1928
6.8.2 Example of SameExtrinsicObjects Discovery Query
1929
1930
The following example illustrates how to find all the ExtrinsicObjects that are defined to be the same as
the ExtrinsicObject that have a name containing the string MyDocument .
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTheSameExtrinsicObjects</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTheSameExtrinsicObjects</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="$extrinsicObjectName">
<rim:ValueList>
<rim:Value>%MyDocument%</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of SameExtrinsicObjects Discovery Query
1964
6.9 DifferentExtrinsicObjects Discovery Query
1965
1966
1967
1968
The DifferentExtrinsicObjects discovery query MUST be implemented by an ebXML Registry

implementing this profile. It allows the discovery of all the "ExtrinsicObjects" defined to be the different
from a given ExtrinsicObject. The canonical query corresponding to this discovery query is presented in
Section 7.3.9.
September 25, 2006

Page 46 of 76
1969
6.9.1 Parameter $extrinsicObjectName
1970
1971
value of ExtrinsicObjects.
1972
6.9.2 Example of DifferentExtrinsicObjects Discovery Query
1973
1974
The following example illustrates how to find all the ExtrinsicObjects that are defined to be different from
the ExtrinsicObject that have a name containing the string MyDocument .
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDifferentExtrinsicObjects</rim:Value
>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDifferentExtrinsicObjects</rim:Value
>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="$extrinsicObjectName">
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
2009
</rim:AdhocQuery>
Example of DifferentExtrinsicObjects Discovery Query
2010
6.10 AllDifferentRegistryObject Discovery Query
2011
2012
2013
2014
2015
The AllDifferentRegistryObjects discovery query MUST be implemented by an ebXML Registry

implementing this profile. Given a RegistryObject, it allows the discovery of all the other member
"RegistryObjects" of a Registry package that are defined to be the different from each other through a
allDifferent slot. The canonical query corresponding to this discovery query is presented in Section
7.3.10.
2016
6.10.1 Parameter $registryObjectName
2017
2018
value of RegistryObjects.
2019
6.10.2 Example of AllDifferentRegistryObjects Discovery Query
2020
2021
The following example illustrates how to find all the RegistryObjects that are defined to be different from
the RegistryObject that have a name containing the string MyDocument .
September 25, 2006

Page 47 of 76
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllDifferent</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllDifferent</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="$registryObjectName">
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of AllDifferentRegistryObjects Discovery Query
2055
6.11 ObjectProperties Discovery Query
2056
2057
2058
The ObjectProperties discovery query MUST be implemented by an ebXML Registry implementing this
profile. It allows the discovery of all of the objectProperties of a given classification node. The canonical
query corresponding to this discovery query is presented in Section 7.3.11.
2059
2060
2061
2062
6.11.2 Example of ObjectProperties Discovery Query
2063
2064
The following example illustrates how to find all the object properties of a given classification node having
a name containing AirServices .
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindObjectProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
September 25, 2006

Page 48 of 76
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindObjectProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of ObjectProperties Discovery Query
2098
6.12 ImmediateInheritedObjectProperties Discovery Query
2099
2100
2101
2102
The ImmediateInheritedObjectProperties discovery query MUST be implemented by an ebXML Registry

implementing this profile. It allows the discovery of all of the objectProperties of a given classification node
including the ones inherited from its immediate super classes. The canonical query corresponding to this
discovery query is presented in Section 7.3.12.
2103
2104
2105
2106
6.12.2 Example of ImmediateInheritedObjectProperties Discovery Query
2107
2108
a name containing AirServices including the ones inherited from its immediate super classes.
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateInheritedObjectProperties</
rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateInheritedObjectProperties</
rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
September 25, 2006

Page 49 of 76
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
</rim:AdhocQuery>
Example of ImmediateInheritedObjectProperties Discovery Query
6.13 AllInheritedObjectProperties Discovery Query
2148
2149
2150
It should be noted that, given a class, finding the object properties inherited from immediate super classes
is necessary but not sufficient. Given a class, it should be possible to retrieve all of the object properties
inherited from its super classes. This requires a recursion mechanism in SQL queries.
The AllInheritedObjectProperties discovery query MAY be implemented by an ebXML Registry
implementing this profile. It allows the discovery of all inherited ObjectProperties recursively of a given
ClassificationNode in a ClassificationScheme in an ebXML Registry implementation supporting recursion.
2151
The canonical query corresponding to this discovery query is presented in Section 7.3.13.
2152
2153
2154
2155
6.13.2 Example of AllInheritedObjectProperties Discovery Query
2156
2157
2158
a name containing AirReservationServices including the ones inherited from all of its super classes
recursively, if the query is implemented as an Adhoc Query.
2145
2146
2147
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllInheritedObjectProperties</rim:Va
lue>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAll
InheritedObjectProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
September 25, 2006

Page 50 of 76
2191
2192
2193
</rim:AdhocQuery>
Example of AllInheritedObjectProperties Discovery Query
2194
6.14 DatatypeProperties Discovery Query
2195
2196
2197
The DatatypeProperties discovery query MUST be implemented by an ebXML Registry implementing this
profile. It allows the discovery of all of the datatypeProperties of a given classification node. The
canonical query corresponding to this discovery query is presented in Section 7.3.14.
2198
2199
2200
2201
6.14.2 Example of DatatypeProperties Discovery Query
2202
2203
The following example illustrates how to find all the datatype properties of a given classification node
having a name containing AirReservationServices .
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDatatypeProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDatatypeProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of DatatypeProperties Discovery Query
2237
6.15 AllInheritedDatatypeProperties Discovery Query
2238
2239
2240
It should be noted that, given a class, finding the datatype properties inherited from immediate super
classes is necessary but not sufficient. Given a class, it should be possible to retrieve all of the datatype
properties inherited from its super classes. This requires a recursion mechanism in SQL queries.
2241
2242
2243
The AllInheritedDatatypeProperties discovery query MAY be implemented by an ebXML Registry

implementing this profile. It allows the discovery of all inherited DatatypeProperties recursively of a given
ClassificationNode in a ClassificationScheme in an ebXML Registry implementation supporting recursion.
September 25, 2006

Page 51 of 76
2244
The canonical query corresponding to this discovery query is presented in Section 7.3.15.
2245
2246
2247
2248
6.15.2 Example of AllInheritedDatatypeProperties Discovery Query
2249
2250
2251
The following example illustrates how to find all the datatype properties of a given classification node
having a name containing AirReservationServices including the ones inherited from all of its super
classes recursively, if the query is implemented as an Adhoc Query.
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllInheritedDatatypeProperties</rim:
Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllInheritedDatatypeProperties</rim:
Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>%AirReservationServices %</rim:Value>
</rim:ValueList>
</rim:Slot>
2286
Example of AllInheritedDatatypeProperties Discovery Query
</rim:AdhocQuery>
2287
6.16 TransitiveRelationships Discovery Query
2288
2289
2290
To make any use of the transitive property in ebXML registries, coding is necessary to find out the implied
information. The TransitiveRelationships discovery query MUST be implemented by an ebXML Registry
implementing this profile to handle this semantics.
2291
2292
2293
2294
Given a class which is a source of a transitive property, this discovery query retrieves not only the target
objects of a given transitive property, but if the target objects have the same property, it retrieves their
target objects too. The canonical query corresponding to this discovery query is presented in Section
7.3.16.
September 25, 2006

Page 52 of 76
2295
2296
2297
2298
2299
2300
This parameter's value SHALL specify a string containing a pattern match against the name attribute
2301
6.16.3 Example of TransitiveRelationships Discovery Query
2302
2303
The following example illustrates how to retrieve all the target objects of the succeeds property of the
AirReservationServices including the target objects implied by a transitive property relationship.
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTransitiveRelationships</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTransitiveRelationships</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>%succeeds%</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of TransitiveRelationships Discovery Query
2342
6.17 TargetObjects Discovery Query
2343
2344
2345
2346
The TargetObjects discovery query MUST be implemented by an ebXML Registry implementing this
profile. It allows the discovery of the targetObjects from the Registry, given a Classification Node
(sourceObject) and a property name (Association Type). The canonical query corresponding to this
discovery query is presented in Section 7.3.17.
September 25, 2006

Page 53 of 76
2347
2348
2349
2350
2351
2352
2353
6.17.3 Example of TargetObjects Discovery Query
2354
2355
The following example illustrates how to retrieve all the target objects of the paymentMethod property of
the AirReservationServices.
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTargetObjects</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTargetObjects</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>%paymentMethod%</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of TargetObjects Discovery Query
2394
2395
6.18 TargetObjectsInverseOf Discovery Query
2396
2397
2398
2399
2400
The TargetObjectsInverseOf discovery query MUST be implemented by an ebXML Registry implementing

this profile. Given a Classification Node (sourceObject) and a property name (Association Type), this
query retrieves the source objects of the properties which are stated to be inverseOf the property name
given as a parameter, and considering the Classification Node name as the targetObject of these
properties. The canonical query corresponding to this discovery query is presented in Section 7.3.18.
September 25, 2006

Page 54 of 76
2401
2402
2403
2404
2405
2406
2407
6.18.3 Example of TargetObjectsInverseOf Discovery Query
2408
2409
2410
The following example illustrates how to retrieve all the source objects of the properties which are stated
to the the inverseOf the property succeeds, considering the AirReservationServices as the target object
of these properties.
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTOinverseOf</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTOinverseOf</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
2448
Example of TargetObjectsInverseOf Discovery Query
</rim:AdhocQuery>
2449
2450
6.19 InverseRanges Discovery Query
2451
2452
2453
2454
2455
The InverseRanges discovery query MUST be implemented by an ebXML Registry implementing this
profile to handle this semantics. Given a Classification Node (sourceObject) and a property name
(Association Type), this query retrieves not only the target objects of this property, but also the source
objects of the properties which are stated to be inverseOf the property name given as a parameter, and
considering the Classification Node name as the targetObject of these properties. This query can be
September 25, 2006

Page 55 of 76
2456
2457
thought as the union of the queries presented in Sections 6.17and 6.18.

corresponding to this discovery query is presented in Section 7.3.19.
The canonical query
2458
2459
2460
2461
2462
2463
2464
6.19.3 Example of InverseRanges Discovery Query
2465
2466
2467
Consider, for example, the "succeeds" property defined in Section 4.3.3. To denote that a certain Web
service instance precedes another during execution, we may define the "precedes" property as an inverse
of the "succeeds" property as follows:
2468
2469
2470
2471
2472
<owl:ObjectProperty rdf:ID="precedes">
<owl:inverseOf rdf:resource="#succeeds" />
Example owl:inverseOf Property
2473
2474
2475
2476
2477
Assume that we want to find all the Web services which can succeed a given Web service. In such a
case, we need not only find all the Web services which succeeds this given Web service, that is the target
objects of "succeeds" Association instance, but we also need to find all the sourceObjects of the
"precedes" Association instance since "precedes" is declared to be the "inverseOf" succeeds Association
instance.
2478
2479
The following example illustrates how to retrieve all the services that succeeds AirReservationServices
by also making use of its preceeds" property.
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseRanges</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseRanges</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
September 25, 2006

Page 56 of 76
2510
2511
2512
2513
2514
2515
2516
2517
</rim:AdhocQuery>
Example of InverseRanges Discovery Query
2518
6.20 SymmetricProperties Discovery Query
2519
2520
2521
The SymmetricProperties discovery query MUST be implemented by an ebXML Registry implementing

this profile. It allows the discovery of all of the Symmetric Properties of a given classification node. The
2522
2523
2524
2525
6.20.2 Example of SymmetricProperties Discovery Query
2526
2527
The following example illustrates how to find all the symmetric properties of a given classification node
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindSymmetricProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindSymmetricProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of SymmetricProperties Discovery Query
2561
6.21 FunctionalProperties Discovery Query
2562
2563
The FunctionalProperties discovery query MUST be implemented by an ebXML Registry implementing

this profile. It allows the discovery of all of the Functional Properties of a given classification node. The
September 25, 2006

Page 57 of 76
2564
2565
2566
2567
2568
6.21.2 Example of FunctionalProperties Discovery Query
2569
2570
The following example illustrates how to find all the functional properties of a given classification node
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindFunctionalProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindFunctionalProperties</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of Functional Properties Discovery Query
2604
6.22 InverseFunctionalProperties Discovery Query
2605
2606
2607
2608
The InverseFunctionalProperties discovery query MUST be implemented by an ebXML Registry

implementing this profile. It allows the discovery of all of the Inverse Functional Properties of a given
classification node. The canonical query corresponding to this discovery query is presented in Section
7.3.22.
2609
2610
2611
2612
6.22.2 Example of InverseFunctionalProperties Discovery Query
2613
2614
The following example illustrates how to find all the inverse functional properties of a given classification
node having a name containing AirReservationServices .
September 25, 2006

Page 58 of 76
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
<rim:Slot
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseFunctionalProperties</rim:Val
ue>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseFunctionalProperties</rim:Val
ue>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
2649
Example of InverseFunctional Properties Discovery Query
</rim:AdhocQuery>
2650
6.23 Instances Discovery Query
2651
2652
2653
2654
When an intersection definition is used to create a complex class (a new ClassificationNode) in RIM as
described in Section 4.6, it becomes possible to infer that the objects (instances) classified by all of the
classes (ClassificationNodes) specified in the Intersection definition, are also classified by this complex
class.
2655
2656
2657
2658
2659
The Instances discovery query MUST be implemented by an ebXML Registry implementing this profile. It
allows the discovery of all of the direct instances of a given classification node and if it is a complex class
which is an intersection two classes, it also allows to retrieve the intersection of the instances of both of
the classes involved in the intersection definition. The canonical query corresponding to this discovery
query is presented in Section 7.3.23.
2660
2661
2662
2663
6.23.2 Example of Instances Discovery Query
2664
2665
2666
Consider the AirReservationServices definition presented in Section 4.6. The following example
illustrates how to find all the direct instances of the AirReservationServices and also the instances
classified by both AirServices and also the ReservationServices.
2667
2668
2669
<rim:Slot
September 25, 2006

Page 59 of 76
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInstances</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
<rim:Value>urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInstances</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:ValueList>
</rim:ValueList>
</rim:Slot>
</rim:AdhocQuery>
Example of Instances Discovery Query
September 25, 2006

Page 60 of 76
2700
7 Canonical Metadata Definitions
2701
This chapter specifies the canonical metadata defined by this profile.
2702
7.1 ObjectType Extensions
2703
2704
The following new extensions to the canonical ObjectType ClassificationScheme are described by this
profile:
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
<rim:ClassificationNode parent="urn:oasis:names:tc:ebxmlregrep:ObjectType:RegistryObject:ExtrinsicObject"
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:ObjectType:RegistryObject:ExtrinsicObject:OWL"
code="OWL" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:ObjectType:RegistryObject:ExtrinsicObject:OWL"
>
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="OWL"/>
</rim:Name>
2717
7.2 AssociationType Extensions
2718
The following new extensions to the AssociationType ClassificationScheme are described by this profile:
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
<rim:ClassificationNode parent="urn:oasis:names:tc:ebxmlregrep:classificationScheme:AssociationType"
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL" code="OWL"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="OWL"/>
</rim:Name>
<rim:ClassificationNode parent="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL"
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty"
code="ObjectProperty" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty">
<rim:Name>
<rim:LocalizedString charset="UTF-8"
value="ObjectProperty"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:HasProperty"
code="Property" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:HasProperty">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="Property"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubPropertyOf"
code="SubPropertyOf" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubPropertyOf">
<rim:Name>
September 25, 2006

Page 61 of 76
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
<rim:LocalizedString charset="UTF-8" value="SubPropertyOf"/>

</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubClassOf"
code="SubClassOf" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubClassOf">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="SubClassOf"/>
</rim:Name>
<rim:ClassificationNode parent="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL "
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:IntersectionOf"
code="IntersectionOf" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:IntersectionOf">
<rim:Name>
value="IntersectionOf"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SameAs" code="SameAs"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SameAs">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="SameAs"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:Restriction"
code="restriction" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:Restriction">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="Restriction"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DifferentFrom"
code="DifferentFrom" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DifferentFrom">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="DifferentFrom"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DatatypeProperty"
code="DatatypeProperty" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DatatypeProperty">
<rim:Name>
September 25, 2006

Page 62 of 76
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
value="DatatypeProperty"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:TransitiveProperty"
code="TransitiveProperty" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:TransitiveProperty">
<rim:Name>
value="TransitiveProperty"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseOf"
code="InverseOf" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseOf">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="InverseOf"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SymmetricProperty"
code="SymmetricProperty" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SymmetricProperty">
<rim:Name>
value="SymmetricProperty"/>
</rim:Name>
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:FunctionalProperty"
code="FunctionalProperty" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:FunctionalProperty">
<rim:Name>
value="FunctionalProperty"/>
</rim:Name>
<rim:ClassificationNode parent=urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL "
lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseFunctionalProperty"
code="InverseFunctionalProperty" id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseFunctionalProperty"
>
<rim:Name>
value="InverseFunctionalProperty"/>
</rim:Name>
September 25, 2006

Page 63 of 76
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
<rim:ClassificationNode parent=urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL "

lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SeeAlso" code="SeeAlso"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SeeAlso">
<rim:Name>
<rim:LocalizedString charset="UTF-8" value="SeeAlso"/>
</rim:Name>
Extensions to the AssociationType ClassificationScheme
2899
7.3 Canonical Queries
2900
2901
The following new canonical queries are described by this profile. Note that while these queries are
complex, the complexity is hidden from clients by exposing only the query parameters to them.
2902
7.3.1 All SuperProperties Discovery Query
2903
2904
2905
2906
Recursion is not supported by SQL-92, for this reason the stored procedure for this query coded in SQL
99 Standard is available from:
http://www.srdc.metu.edu.tr/ebxml/ebXMLRegistryProfileForOWL/StoredProceduresSupportingebXMLRe
gsitryProfileforOWL.htm.
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
7.3.2 Immediate SuperClass Discovery Query

<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSuperClasses"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSuperClasses">
<rim:Name>
<rim:LocalizedString
value="label.FindImmediateSuperClasses"/>
</rim:Name>
<rim:Description>
value="label.FindImmediateSuperClasses.desc"/>
</rim:Description>
SELECT C2.*
FROM ClassificationNode C2, Association A, Name_ N,
ClassificationNode C1
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SubClassOf'' AND
C1.id = N.parent AND
N.value LIKE ''$className'' AND
A.sourceObject = C1.id AND
A.targetObject = C2.id
</rim:AdhocQuery>
The Adhoc Query retrieving immediate super classes of a given classification node
7.3.3 Immediate SubClass Discovery Query

<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSubClasses"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateSubClasses">
<rim:Name>
September 25, 2006

Page 64 of 76
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
<rim:LocalizedString value="label.FindImmediateSubClasses"/>
</rim:Name>
<rim:Description>
value="label.FindImmediateSubClasses.desc"/>
</rim:Description>
SELECT C2.*
ClassificationNode C1
</rim:AdhocQuery>
2961
The Adhoc Query retrieving immediate subclasses of a given classification node
2962
2963
2964
2965
2966
7.3.4 All SuperClasses Discovery Query

2967
2968
7.3.5 All SubClasses Discovery Query
2971
2972
2973
7.3.6 EquivalentClasses Discovery Query
2969
2970
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentClasses"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentClasses">
<rim:Name>
<rim:LocalizedString value="label.FindEquivalentClasses"/>
</rim:Name>
<rim:Description>
value="label.FindEquivalentClasses.desc"/>
</rim:Description>
SELECT C2.*
ClassificationNode C
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:EquivalentTo'' AND
C.id = N.parent AND
A.sourceObject = C.id AND
</rim:AdhocQuery>
September 25, 2006

Page 65 of 76
2998
2999
Adhoc Query retrieving all the equivalent classes of a given classification node
7.3.7 EquivalentProperties Discovery Query
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindEquivalentProperties">
<rim:Name>
value="label.FindEquivalentProperties"/>
</rim:Name>
<rim:Description>
value="label.FindEquivalentProperties.desc"/>
</rim:Description>
SELECT A3.*
FROM Association A3, Association A1, Name_ N, Association
A2
WHERE A1.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:EquivalentTo'' AND
A2.id = N.parent AND
N.value LIKE ''$propertyName'' AND
A1.sourceObject = A2.id AND
A1.targetObject = A3.id
</rim:AdhocQuery>
3025
Adhoc Query retrieving all the equivalent Association Type of a given Association Type
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
7.3.8 SameExtrinsicObjects Discovery Query

<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTheSameExtrinsicObjects"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTheSameExtrinsicObjects">
<rim:Name>
value="label.FindTheSameExtrinsicObjects"/>
</rim:Name>
<rim:Description>
value="label.FindTheSameExtrinsicObjects.desc"/>
</rim:Description>
SELECT E2.*
FROM ExtrinsicObject E2, Association A, Name_ N,
ExtrinsicObject E
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SameAs'' AND
E.id = N.parent AND
N.value LIKE ''$extrinsicObjectName'' AND
A.sourceObject = E.id AND
A.targetObject = E2.id
</rim:AdhocQuery>
Adhoc Query retrieving all the "ExtrinsicObjects" defined to be the same with a given
ExtrinsicObject
September 25, 2006

Page 66 of 76
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
7.3.9 DifferentExtrinsicObjects Discovery Query

<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDifferentExtrinsicObjects"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDifferentExtrinsicObjects">
<rim:Name>
value="label.FindDifferentExtrinsicObjects"/>
</rim:Name>
<rim:Description>
value="label.FindDifferentExtrinsicObjects.desc"/>
</rim:Description>
SELECT E2.*
FROM ExtrinsicObject E2, Association A, Name_ N,
ExtrinsicObject E
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DifferentFrom'' AND
E.id = N.parent AND
N.value LIKE ''$extrinsicObjectName'' AND
A.sourceObject = E.id AND
A.targetObject = E2.id
</rim:AdhocQuery>
3080
3081
Adhoc Query retrieving all the "ExtrinsicObjects" defined to be different from a given
ExtrinsicObject
3082
7.3.10 AllDifferentRegistryObject Discovery Query
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllDifferent"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindAllDifferent">
<rim:Name>
<rim:LocalizedString value="label.FindAllDifferent"/>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="label.FindAllDifferent.desc"/>
</rim:Description>
SELECT RO2.*
FROM RegistryObject RO2, Association A1, Association A2,
Name_ N, RegistryObject RO,
RegistryPackage RP
WHERE A1.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:HasMember'' AND
RO.id = N.parent AND
N.value LIKE ''$registryObjectName'' AND
A1.sourceObject = RP.id AND

A1.targetObject = RO.id AND
A2.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:HasMember'' AND
A2.sourceObject = RP.id AND
A2.targetObject != RO.id AND
A2.targetObject = RO2.id
</rim:AdhocQuery>
3115
Adhoc Query retrieving all the "RegistryObjects" defined to be different from a given
September 25, 2006

Page 67 of 76
3116
RegistryObject through a allDifferent construct
3117
7.3.11 ObjectProperties Discovery Query
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindObjectProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindObjectProperties">
<rim:Name>
<rim:LocalizedString value="label.FindObjectProperties"/>
</rim:Name>
<rim:Description>
value="label.FindObjectProperties.desc"/>
</rim:Description>
SELECT A.*
FROM Association A, Name_ N, ClassificationNode C
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty'' AND
C.id = N.parent AND
A.sourceObject = C.id
</rim:AdhocQuery>
3140
Adhoc Query retrieving all the object properties of a given classification node
3141
7.3.12 ImmediateInheritedObjectProperties Discovery Query
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateInheritedObjectProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindImmediateInheritedObjectProperties">
<rim:Name>
value="label.FindImmediateInheritedObjectProperties"/>
</rim:Name>
<rim:Description>
value="label.FindImmediateInheritedObjectProperties.desc"/>
</rim:Description>
SELECT A2.*
FROM Association A, Name_ N, ClassificationNode C1,
ClassificationNode C2, Association A2
A.targetObject = C2.id AND
A2.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:ObjectProperty'' AND
A2.sourceObject=C2.id
</rim:AdhocQuery>
3170
3171
Adhoc Query retrieving all of the properties of a given classification node including the ones
inherited from its immediate super classes
September 25, 2006

Page 68 of 76
3172
7.3.13 AllInheritedObjectProperties Discovery Query
3175
3176
3177
7.3.14 DatatypeProperties Discovery Query
3173
3174
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDatatypeProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindDatatypeProperties">
<rim:Name>
<rim:LocalizedString value="label.FindDatatypeProperties"/>
</rim:Name>
<rim:Description>
value="label.FindDatatypeProperties.desc"/>
</rim:Description>
SELECT A.*
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:DatatypeProperty'' AND
C.id = N.parent AND
</rim:AdhocQuery>
3200
Adhoc Query retrieving all the datatype properties of a given classification node
3201
7.3.15 AllInheritedDatatypeProperties Discovery Query
3204
3205
3206
7.3.16 TransitiveRelationships Discovery Query
3202
3203
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTransitiveRelationships"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTransitiveRelationships">
<rim:Name>
value="label.FindTransitiveRelationships"/>
</rim:Name>
<rim:Description>
value="label.FindTransitiveRelationships.desc"/>
</rim:Description>
SELECT C.*
FROM ClassificationNode C, Association A1, Association A2,
Name_ N1, Name_ N2, Name_ N3
WHERE A1.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:TransitiveProperty'' AND
A1.id = N1.parent AND
N1.value LIKE ''$propertyName'' AND
September 25, 2006

Page 69 of 76
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
A1.sourceObject = N3.parent AND

N3.value LIKE ''$className'' AND
A2.sourceObject = A1.targetObject AND
A2.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:TransitiveProperty'' AND
A2.targetObject = C.id

</rim:AdhocQuery>
3249
Adhoc Query retrieving the objects in transitive relationship with a given object
3250
7.3.17 TargetObjects Discovery Query
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTargetObjects"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTargetObjects">
<rim:Name>
<rim:LocalizedString value="label.FindTargetObjects"/>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="label.FindTargetObjects.desc"/>
</rim:Description>
SELECT C2.*
FROM ClassificationNode C2, Association A, Name_ N, Name_
N2, ClassificationNode C1
WHERE A.id=N2.parent AND
</rim:AdhocQuery>
3274
3275
Adhoc Query retrieving the Target Objects from the Registry, given a Source Object and an
Association
3276
7.3.18 TargetObjectsInverseOf Discovery Query
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTOinverseOf"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindTOinverseOf">
<rim:Name>
<rim:LocalizedString value="label.FindTOinverseOf"/>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="label.FindTOinverseOf.desc"/>
</rim:Description>
September 25, 2006

Page 70 of 76
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
SELECT C2.*
FROM ClassificationNode C2, Association A1, Association A2,
Association A3, Name_ N, Name_ N2, ClassificationNode C1
WHERE A2.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseOf'' AND
A2.targetObject = A3.id AND
C1.id = N2.parent AND
A3.targetObject = C1.id AND
A3.sourceObject = C2.id
</rim:AdhocQuery>
3304
3305
Adhoc query retrieving the Source Objects of an Association which is in "inverseOf"

relationship to this Association
3306
7.3.19 InverseRanges Discovery Query
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseRanges"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseRanges">
<rim:Name>
<rim:LocalizedString value="label.FindInverseRanges"/>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="label.FindInverseRanges.desc"/>
</rim:Description>

SELECT C2.*
FROM ClassificationNode C2, Association A1, Association A2,
Association A3, Name_ N, NAME_ N2, ClassificationNode C1
WHERE A2.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseOf'' AND
A2.targetObject = A3.id AND
C1.id = N2.parent AND
A1.sourceObject = C1.id AND
A3.sourceObject = C2.id
</rim:AdhocQuery>
Adhoc Query Retrieving both the Target Objects of a given Association and the Source
Objects of an Association which is in "inverseOf" relationship to this Association
September 25, 2006

Page 71 of 76
3346
7.3.20 SymmetricProperties Discovery Query
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindSymmetricProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindSymmetricProperties">
<rim:Name>
<rim:LocalizedString value="label.FindSymmetricProperties"/>
</rim:Name>
<rim:Description>
value="label.FindSymmetricProperties.desc"/>
</rim:Description>
SELECT A.*
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:SymmetricProperty'' AND
C.id = N.parent AND
</rim:AdhocQuery>
3369
Adhoc Query retrieving all the Symmetric properties of a given classification node
3370
7.3.21 FunctionalProperties Discovery Query
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindFunctionalProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindFunctionalProperties">
<rim:Name>
value="label.FindFunctionalProperties"/>
</rim:Name>
<rim:Description>
value="label.FindFunctionalProperties.desc"/>
</rim:Description>
SELECT A.*
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:FunctionalProperty'' AND
C.id = N.parent AND
</rim:AdhocQuery>
3394
Adhoc Query retrieving all the Functional properties of a given classification node
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
7.3.22 InverseFunctionalProperties Discovery Query

<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseFunctionalProperties"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInverseFunctionalProperties">
<rim:Name>
value="label.FindInverseFunctionalProperties"/>
</rim:Name>
<rim:Description>
September 25, 2006

Page 72 of 76
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
value="label.FindInverseFunctionalProperties.desc"/>
</rim:Description>
SELECT A.*
WHERE A.associationType LIKE ''urn:oasis:names:tc:ebxmlregrep:profile:webontology:AssociationType:OWL:InverseFunctionalProperty'
' AND
C.id = N.parent AND
</rim:AdhocQuery>
3420
Adhoc Query retrieving all the Inverse Functional properties of a given classification node
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
7.3.23 Instances Discovery Query Discovery Query

<rim:AdhocQuery lid="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInstances"
id="urn:oasis:names:tc:ebxmlregrep:profile:webontology:query:FindInstances">
<rim:Name>
<rim:LocalizedString value="label.FindInstances"/>
</rim:Name>
<rim:Description>
<rim:LocalizedString value="label.FindInstances.desc"/>
</rim:Description>

SELECT S.*
FROM Service S, Classification C, ClassificationNode CN,
Name_ N
WHERE S.id = C. classifiedObject AND
C.classificationNode = CN.id AND
September 25, 2006

Page 73 of 76
3469
3470
3471
3472

N.parent = CN.id
</rim:AdhocQuery>
3473
Adhoc Query Retrieving the instances of intersected classes
September 25, 2006

Page 74 of 76
3474
8 OWL Profile References
3475
8.1 Normative References
3476
[Bechhofer, Harmelen, Hendler, Horrocks, McGuinness, Patel-Schneider, Stein]
3477
3478
Bechhofer, S., Harmelen, F., Hendler, J., Horrocks, I., McGuinness, D. L., Patel-Schneider, P. F., Stein, L.
A., OWL Web Ontology Language Reference, W3C Recommendation 10 February 2004
3479
http://www.w3.org/TR/2004/REC-owl-ref-20040210/
3480
3482
[Brickley, Guha] Brickley, D., Guha, R.V., RDF Vocabulary Description Language 1.0: RDF Schema
W3C Recommendation 10 February 2004
3483
http://www.w3.org/TR/rdf-schema/
3481
3484
3485
[DAML+OIL] http://www.daml.org/
3486
[ebRIM] ebXML Registry Information Model version 3.0
3487
http://docs.oasis-open.org/regrep/regrep-rim/v3.0/regrep-rim-3.0-os.pdf
3488
3489
[ebRS] ebXML Registry Services Specification version 3.0
3490
http://docs.oasis-open.org/regrep/regrep-rs/v3.0/regrep-rs-3.0-os.pdf
3491
[ebRR-DPT] Deployment Profile Template For ebXML Registry 3.0 OASIS Specifications V_0.1.2
3492
[ebMS-DPT] Deployment Profile Template For OASIS Specification ebXML Message Service 2.0
3493
3494
[McGuinness, Harmelen] McGuinness, D. L., Harmelen, F., OWL Web Ontology Language Overview,
W3C Recommendation 10 February 2004, http://www.w3.org/TR/owl-features/
3495
[OWL] Web Ontology Language (OWL), http://www.w3.org/2004/OWL/
3496
[RDF] Resource Description Framework, http://www.w3.org/TR/rdf-concepts/
3497
[RDFS] RDF Vocabulary Description Language 1.0: RDF Schema http://www.w3.org/TR/rdf-schema/
3498
[Smith, Welty, McGuinness] Smith, M. K., Welty, C., McGuinness, D. L.,
3499
3500
OWL
Web
Ontology Language
http://www.w3.org/TR/owl-guide/
Guide,
3501
[SQL 92] SQL ISO/IEC 9075:1992 Information technology - Database languages - SQL.
3502
[SQL 99] ISO/IEC 9075:1999(E) Information technology - Database languages SQL.
3503
3504
[UML] Unified Modeling Language version 1.5

http://www.omg.org/cgi-bin/apps/doc?formal/03-03-01.pdf
3505
3506
[WSDL] WSDL Specification

http://www.w3.org/TR/wsdl
W3C
Recommendation
10
February
2004,
September 25, 2006

Page 75 of 76
3507
8.2 Informative References
3508
[Dogac, et. al. 2005] Dogac A., Kabak Y., Laleci G. C. Mattocks, F. Najmi, J. Pollock
3509
Enhancing ebXML Registries to Make them OWL Aware

Distributed and Parallel Databases Journal, Springer-Verlag, Vol. 18, No. 1, July 2005, pp. 9-36.
3510
3511
3512
3513
3514
3515
3516
[Dogac et. al. 2006] Dogac A., Laleci G., Kabak Y., Unal S., Beale T., Heard S., Elkin P., Najmi F.,
Mattocks C., Webber D., Kernberg M.
Exploiting ebXML Registry Semantic Constructs for Handling Archetype Metadata in Healthcare
Informatics
International Journal of Metadata, Semantics and Ontologies, Volume 1, No. 1, 2006.
3517
3518
3519
3520
[IMPL] ebXML Registry 3.0 Implementations

freebXML Registry: A royalty free, open source ebXML Registry Implementation
http://ebxmlrr.sourceforge.net
3521
3522
[LeeHendler]
3523
Berners-Lee, T., Hendler, J., Lassila, O., "The Semantic Web", Scientific American, May 2001.
3524
3525
[StaabStuder] Staab, S., Studer, R., Handbook on Ontologies, Springer, 2004.
3526
3527
Appendix A
3528
Contributors:
Name
Farrukh Najmi
Carl Mattocks
Jeff Pollock
Evan Wallace
Dave RR Webber
Nikola Stojanovic
Ivan Bedini
Yildiray Kabak
Gokce Banu Laleci
Affiliation
Sun Micro Systems
MetLife
Network Inference
NIST
Individual
GS1 US
France Telecom
-
3529
September 25, 2006

Page 76 of 76

Regrep Owl Profile v1.5 Cd01

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Regrep Owl Profile v1.5 Cd01

Uploaded by

Copyright:

Available Formats

1

ebXML Registry Profile for Web Ontology

Committee Draft 01, September 25, 2006

Previous Version: [N/A]

OASIS ebXML Registry Technical Committee

September 25, 2006

The non-normative errata page for this specification is located at

Copyright (c) OASIS Open 2006. All Rights Reserved.

September 25, 2006

3.1.4.1 Slot Attributes...................................................................................................................................... 17

3.1.5 Object Classification................................................................................................................. 18

September 25, 2006

4.2.1 owl:equivalentClass, owl:equivalentPropery rim:Association Type EquivalentTo ................ 24

September 25, 2006

5.4.17 owl:minCardinality (only 0 or 1)............................................................................................... 38

September 25, 2006

6.13.2 Example of AllInheritedObjectProperties Discovery Query..................................................... 50

September 25, 2006

7.3.8 SameExtrinsicObjects Discovery Query.................................................................................. 66

September 25, 2006

September 25, 2006

September 25, 2006

This chapter provides an introduction to the rest of this document.

The document is organized as follows:

Chapter 1 provides an introduction to the rest of this document.

Chapter 2 provides an overview of the Web Ontology Language.

Chapter 3 provides an overview of the ebXML Registry standard.

Chapter 5 describes the cataloging service for cataloging OWL content.

September 25, 2006

<id="${CANONICAL_OBJECT_TYPE_ID _ORGANIZATION}" >

1.3 Recommended Enhancements

September 25, 2006

OWL describes the structure of a domain in terms of classes and properties.

2.1 Semantic Web Languages upon which OWL is Layered

Namespace information for these languages is given in the Table 1.

Table 1: Semantic Web namespace table

Commonly used Prefix

Namespace URI Reference

September 25, 2006

2.2 OWL Lite Constructs

2.2.1 RDF Schema Features

Class (Thing, Nothing)

2.2.3 Property Characteristics

2.2.4 Property Restrictions

2.2.5 Restricted Cardinality

2.2.6 Class Intersection

September 25, 2006

2.2.8 Annotation Properties

2.3 OWL DL Constructs

2.3.1 Class Axioms

equivalentClass (applied to class expressions)

rdfs:subClassOf (applied to class expressions)

2.3.2 Boolean Combinations of Class Expressions

2.3.3 Arbitrary Cardinality

2.3.4 Filler Information

September 25, 2006

3 ebXML Registry Overview

3.1 Overview of [ebRIM]

Figure 1: ebXML Registry Information Model, High Level Public View

September 25, 2006

Figure 2: ebXML Registry Information Model, Inheritance View

3.1.2 Object Identification

A RegistryObject has a globally unique id which is a UUID based URN:

<rim:Organization id="urn:uuid:dafa4da3-1d92-4757-8fd8-ff2b8ce7a1bf" >