- From: Dan Brickley <danbri@w3.org>
- Date: Fri, 3 Sep 2004 13:35:02 -0400
- To: public-rdf-dawg-comments@w3.org
- Cc: public-swbp-wg@w3.org
(sent to DAWG feedback list, cc: Best Practices WG) Hi Apologies if this is already covered and I missed it. I'd like DAWG to consider a use case in which a client application wants all the "Dublin Core titles and descriptions" of some object, eg. Danbri's weblog(s), and doesn't care at all which concrete Dublin Core namespace is used. ie. http://purl.org/dc/elements/1.0/ http://purl.org/dc/elements/1.1/ This is a practical issue w/ DC deployment. I'm ignoring for now the additional mess around upper/lowercase. Assume that we see dc10:title and dc11:title in data, that the semantics are pretty much the same but that the schemas aren't explicitly/formally mapped using RDFS or OWL constructs. A couple of approaches leap to mind: 'or'ing, vs. query-specific assumptions, ie. allowing the query to say "Well, let's temporarily assume that dc1:title is a subproperty of dc2:title and vice-versa, ...". Both approaches have their issues (eg. 'or'ing both dc:title and dc:description in a larger query might be hairy), but my sense is that there is a real problem when similar namespaces where new URIs have been assigned despite modest differences in meaning. If DAWG ends up deciding not to create technology that soothes these issues, the Best Practices WG might consider making reference to querying issues when it discusses best practice for Vocabulary Management and versioning. cheers, Dan ps. Eric P, perhaps you could comment on how this is dealt with in Annotea's treatment of Dublin Core 1.0 vs 1.1?
Received on Friday, 3 September 2004 17:35:03 UTC