search

dcmi / usage

DCMI Usage Board - meeting record and decisions
8 stars 5 forks source link

Namespace resolving #114

Closed HughP closed 1 year ago

HughP commented 1 year ago

Greetings,

Can someone please help me better understand the implementation facts around the DCMI namespaces? I mean the following:

I work with XML/OAI-PMH protocols quite a bit and my understanding is that we set the header in documents to define the namespaces used within the document but these namespaces point out to a resolvable machine readable location for each term. For example, via an .xsd file, which can be used for validation.

My confusion comes to the point where http://purl.org/dc/terms/ points to documentation for the schema but the .xsd is not reachable at http://purl.org/dc/terms/dcterms.xsd rather the xsd is only available here: https://www.dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd

So my questions are:

  1. is why is the xsd file not hosted in the path of the namespace?
  2. should it move so that it is?

Any help to better understand the hosing situation and the application of technologies is appreciated.

niklasl commented 1 year ago

Hi @HughP,

Sorry for not responding earlier.

  1. The formal location of the XSD file is the latter one you mention. There is, as far as I can see, no formal reference to the former XSD URL you tried.
  2. I think not. The PURL namespace is dedicated to the DC terms themselves, which are defined using RDF.

Specifically, following the principles of linked data, when dereferenced, these DC term URI:s should resolve to a document in a machine-readable RDF format if you ask for such a format (i.e. using content negotiation), so a system can know what the URI means.

Example of content negotiation:

$ curl -s -L -H "Accept: text/turtle" http://purl.org/dc/terms/

(Closing as not-an-issue. Feel free to re-open if you have found a formal reference to the non-working xsd URL.)