Dublin Core Namespaces

I left a comment/question with the DCMI usage board today. Essentially I want to know why in the XML headers we have statements like xmlns="http://purl.org/dc/elements/1.1/ " scheamLocation="dc.xsd" but they don’t resolve. My understanding was that these were supposed to resolve to the XSD file so that they could be validated. I have found the following notes very helpful:


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.

Additionally, I noted in a different Github issue that the dcterms.xsd file was not well formed based on the current documentation.


I’m wondering if the defining XSD file for dcterms is the linked one: https://www.dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd

If it is not, is there one which is? If it is, then why aren’t the following found in it:

Hugh Paterson III
Hugh Paterson III
Collaborative Scholar

I specialize in bespoke research at the intersection of Linguistics, Law, Languages, and Technology; specifically utility and life-cycle management for information products in these spaces.