OK this is getting towards FAQ territory (see fwd'd
msg on DC and OWL DL).
The DC properties can all be used either with
resources or literals, and there's 5+ years practice
of doing so.
Users who are trying to exploit DL facilities seem to
suffer pain because of this.
I wonder if SWBP has any advice (a) for them, or
(b) for the Dublin Core initiative (noting that
Tom Baker is a critical link between SWBP and DCMI).
There is a DC conference coming up in mid-Sept,
http://dc2005.uc3m.es/ and we have a SemWeb session
in the schedule that needs fleshing out, as well as
a meeting of the Dublin Core architecture WG. I'd like
to start gathering perspectives from this WG re the
costs (in terms of exploiting SW infrastructure) of DC
continuing to focus on properties that can be used in
both styles. If there is a lot that can be shown to be
gained from making DC more DL-friendly, perhaps
(Tom, any comments?) some proposals could be
sketched here (and on dc-architecture) for a way forward...?
Thanks for any thoughts,
Dan
Forwarded message 1
Hi all,
On the similar note, Protégé gives me number of errors when I try to import
the dcterms namespace (http://www.purl.org/dc/terms/). I can import the dces
(http://www.purl.org/dc/elements/1.1/) and the dcmitype
(http://www.purl.org/dc/dcmitype/) namespace without any problems. Has
anyone faced this problem before?
Thank you in advance for the help!
Gauri
-----Original Message-----
From: General DCMI discussion list [mailto:DC-GENERAL@JISCMAIL.AC.UK] On
Behalf Of Daniel Rabus
Sent: 22 June 2005 15:12
To: DC-GENERAL@JISCMAIL.AC.UK
Subject: [DC] Implementing DC in OWL DL
Hi Everyone,
are there any recommendations or guidelines how to implement the DC elements
and DC terms qualifiers in OWL DL?
As a part of my diploma thesis I'm developing a Java program (using
Jena) to manage meta data of various kinds of documents. The DC seems very
suitable to fit the requirements, however, I have to implement the used
ontology (mainly DC and FOAF) in OWL Lite/DL to be able to use extended
inference capabilities.
Especially the explicit mapping of the generic rdf:Property to either
owl:DatatypeProperty or owl:ObjectProperty and the (possibly) resulting
conflicts in the property hierarchy are problematic.
At the moment I'm using my own "OWL port" of the DC elements and terms, but
this solution is closely tied up with the ontology I've created. A more
"general" attempt would be nice.
Any help is appreciated!
Many thanks,
Daniel Rabus
Student, Department of Computer Science
GSO University of Applied Sciences, Nuremberg