OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tm-pubsubj-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [tm-pubsubj-comment] OWL and Published Subjects - is coordinationrelevant?

I posted last week a call for reflection to both PubSubj an WebOnt working groups

I would like to expand a little more on why I see some liaison between OASIS PubSubj and
OWL would be relevant from both viewpoints. For example several points in the OWL
Requirements document focus on the necessity of interoperability of ontologies.

<< 3.1 Shared ontologies:
Interoperability requires agreements on the definitions of terms. Ontologies can provide
standard sets of terms and formal
descriptions of those terms. Data sources that commit to the same ontology explicitly
agree to use the same terms with the
same meanings. >>

And also

<< 3.3 Ontology interoperability
Different ontologies may model the same concepts in different ways. The language should
provide primitives for relating different
representations, thus allowing data to be converted to different ontologies and enabling a
"web of ontologies."

Although shared ontologies and ontology extension allow a certain degree of
interoperability between different organizations and
domains, there are often cases where there are multiple ways to model the same information
... >>

How can those agreements and differences be clearly expressed? Referring to a definite
term in a non-ambiguous way needs this term to be identified independently both of its
name, and of the relationships declared in any given ontology it happens to belong. PSI
are fit to provide such ways for identification, clarification and hence non-ambiguous

To refer to the example of Dolphins quoted in the Requirements doc, a PSI could be defined
e.g by http://psi.seaworld.org/animals/dolphin.html
This hypothetical PSI should provide a non ambiguous definition of what Dolphins are ...

One zoological ontology could use this PSI to identify the "Dolphins" class in the generic
class hierarchy
Animals > Mammals > Cetaceans > Dolphins

Note that the French version will use the same PSI to identify "Dauphins"
Animaux > Mammifères > Cétacés > Dauphins

Another ontology used by a French Riviera tourism website could use the same PSI to
identify the "Dauphins" class in a more local and specific hierarchy
Antibes > Attractions > Marineland > Dolphins

Referring to the same PSI for those two classes will support assertions like:

"If Flipper is an instance of Dolphins in Marineland, then he is a Mammal"
"Instances of Cetaceans can be seen in Marineland, Antibes"

But of course, I would make a mistake using the same PSI to identify my local swimming
team :))
Embrun > Sports > Natation > Clubs > Les Dauphins

BTW, it figures that URLs of Open Directory categories - a use case quoted in the
Requirements doc - are not fit to be used as conformant PSIs, since they are defined in
their very syntax by the category hierarchy, see for example the following.


Go figure if Dolphins in three sub-sub ... categories are the same guys, even if those
three categories are cross-referencing each other. Not only the URIs are stuck to a
specific hierarchy, but moreover, they are notoriously unstable (I've been there -
redefining hierarchies is a popular fun game among Open Directory editors)

To come back to our working groups, I think it would be great to explore at least two

1 - How OWL could integrate the notion of PSIs?

2 - How PubSubj Recommendations could take this very issue of ontologies interoperability
as an explicit use case?

And since our two efforts are roughly at the same stage of development (more issues than
definitive answers), maybe they could be able to achieve recommendations consistent with
each other, or at least explore together their common issues.

Thanks to consider (from both sides)


Bernard Vatant
Chair - OASIS TM PubSubj Technical Committee

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC