[Person-ontology] Ontology Requirements for Distributed Data Sharing

[Drummond Reed]

To clarify, this distribute data sharing metadata involves very specialized attributes-of-attributes normally required in directory/metadirectory or data synchronization protocols like createDate, lastUpdateDate, Source, syncConflict, access permissions, etc. This is the kind of metadata that exists at the protocol and data repository management level, before we get into any business or real-world modeling semantics.

Higgins engineers, including directory/metadirectory engineers from IBM, Novell, Oracle, and CA, have so far been the ones contributing to this relatively small vocabulary in Higgins OWL. We'd love to know if SUMO or other upper level ontologies have covered the same territory.

=Drummond

> -----Original Message-----
> From: person-ontology-bounces at idcommons.net [mailto:person-ontology-
> bounces at idcommons.net] On Behalf Of Schoening, James R Mr CIV USA AMC
> Sent: Thursday, October 18, 2007 7:07 PM
> To: person-ontology at idcommons.net
> Subject: [Person-ontology] Ontology Requirements for Distributed Data
> Sharing
>
> All,
>
>         Drummon Reed, a Higgins Project member, asked if we could
> explore this topic:
>
>         "Another topic area worth exploring is the specific ontology
> requirements for distributed data sharing. It turns out a great deal of
> the current Higgins OWL vocabulary is just for defining metadata
> required for cross-context data sharing. Call it a "domain ontology" for
> a very specialized domain. This isn't a focus of SUMO or any other KIF
> ontology as best I can tell, but it's the first focus of the Higgins
> community, one it must conquer before it can move to using other domain
> ontologies."
>
> Jim Schoening
> _______________________________________________
> Person-ontology mailing list
> Person-ontology at idcommons.net
> http://idcommons.net/cgi-bin/mailman/listinfo/person-ontology