Drupal7 wrongly refers to the Dublin Core Terms namespace via 'xmlns:dc'! The correct namespace references are the ones below:

xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:<strong>dcterms</strong>="http://purl.org/dc/terms/"
xmlns:dctype="http://purl.org/dc/dcmitype/"

Or ... should I be completely on the wrong info path?

By the way, I cannot find 'xmlns:dctype' in the html header. Is this intended?

CommentFileSizeAuthor
#8 994592_rdf-namespaces__rdf.api_.php_.patch1.13 KBBlooniverse
#8 994592_rdf-namespaces__rdf.module_.patch1.48 KBBlooniverse
#8 994592_rdf-namespaces__rdf.test_.patch10.73 KBBlooniverse
#8 994592_rdf-namespaces__rdf_test.module_.patch1.54 KBBlooniverse

Comments

Blooniverse’s picture

Blooniverse commented

... wrong coding above. It should be: 

xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:dctype="http://purl.org/dc/dcmitype/"

... or: 

xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcte="http://purl.org/dc/terms/"
xmlns:dcty="http://purl.org/dc/dcmitype/"
damien tournoud’s picture

damien tournoud commented
Status: Active » Closed (works as designed)

The part after the "xmlns" (the namespace prefix) is completely arbitrary. It could be:

xmlns:letsthrowaparty="http://purl.org/dc/terms/"

It would just work the same. I don't believe there is any bug here.

Blooniverse’s picture

Blooniverse commented

Correct (arbitraryness)! Exactly this fact makes it inevitable to be clear in language AND in expression.

A house is a house, and a donkey is a donkey. I wouldn't like to ride on a house and live in a donkey, would you? ;) Linguistic stuff should NOT be arbitrary in its meaning.

Blooniverse’s picture

Blooniverse commented
Issue tags: +terms, +drupal7, +namespaces, +dublin core, +DC

... it is the semantic web, after all!!!

damien tournoud’s picture

damien tournoud commented
Status: Closed (works as designed) » Needs review
Issue tags: -terms, -drupal7, -namespaces, -dublin core, -DC

Roll a patch if you feel strongly about this :)

Blooniverse’s picture

Blooniverse commented
Issue tags: -terms, -drupal7, -namespaces, -dublin core, -DC

... I will. This is a MUST! Cannot stop the fire burning in me ;)

damien tournoud’s picture

damien tournoud commented
Status: Needs review » Needs work
Issue tags: +API change

This cannot be done without an API change (modules using that namespace will stop working).

Blooniverse’s picture

Blooniverse commented
Assigned: Unassigned » Blooniverse
Status: Needs work » Needs review
StatusFileSize
new 994592_rdf-namespaces__rdf_test.module_.patch1.54 KB
new 994592_rdf-namespaces__rdf.test_.patch10.73 KB
new 994592_rdf-namespaces__rdf.module_.patch1.48 KB
new 994592_rdf-namespaces__rdf.api_.php_.patch1.13 KB

... here the patches according to the diff guidelines of Drupal.org.

Status: Needs review » Needs work

The last submitted patch, 994592_rdf-namespaces__rdf_test.module_.patch, failed testing.

Blooniverse’s picture

Blooniverse commented

Dear system,

Since I am not the maintainer respecively developer of this module, I cannot fix these occurences. The only thing my patches should optimize are the Dublin Core namespaces.

Thank you for your attention,
Philipp Schaffner

Blooniverse’s picture

Blooniverse commented
Priority: Normal » Minor
Status: Needs work » Fixed

Probably it is better to leave things as they are (namespace prefix 'dc:' refering to http://purl.org/dc/terms/). Several reasons:

Nonetheless, I have two questions left to ask you RDF guys and girls:

  1. Why does the 'og:' namespace prefix link to http://ogp.me/ns#. This results in a 404 response in my browser. Should the URI not be http://opengraphprotocol.org/schema instead?
  2. And should the 'skos:' namespace prefix not rather link to http://www.w3.org/2009/08/skos-reference/skos.rdf instead of http://www.w3.org/2004/02/skos/core#?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

scor’s picture

scor commented

the dc prefix was purposely bound to the http://purl.org/dc/terms/ namespace, since the older http://purl.org/dc/elements/1.1/ namespace is being phased out.

hughbris’s picture

hughbris commented

Could you expand on this? (#7) I think there's a lot of confusion in this issue's thread between namespace prefixes and namespaces themselves (which are URIs). If there are modules relying on the prefix that can't accept something like say, "letsthrowaparty", as a prefix, then it seems it's the modules that have the bug, or perhaps the API they are using. I can't be sure because there isn't enough detail in your comment.

And yes, for the record, I am in favor of using conventions for namespace prefixes where they exist. It's not required but it is good practice. Drupal core should aspire to that.

(also: sorry, admittedly I've come into this from a search and have no real context)
[edited to make it clear which post I'm replying to]

scor’s picture

scor commented

@hughbris What @Damien Tournoud was referring to in #7 is that modules using the dc: prefix would then break if you changed their namespace on them.

@the_phi #11 the og namespace has been fixed to dereference. Re the SKOS namespace, http://www.w3.org/2004/02/skos/core# is the official namespace as specified in the SKOS specification. This namespace support content negotiation which will serve the appropriate format (HTML or RDF) depending on the client requesting the namespace. Nothing to fix here.

Blooniverse’s picture

Blooniverse commented

Thanks, @scor, for the explanation. I was probably a bit exited last year about the semantic web ;) Wanted to have things really precise or something like that.

David Lesieur’s picture

David Lesieur commented
Issue summary: View changes
Status: Closed (fixed) » Closed (works as designed)

"Works as designed" seems to better summarize the discussion than "Fixed" as no change was made.