Closed (works as designed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
rdf.module
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
15 Dec 2010 at 14:56 UTC
Updated:
29 Jul 2014 at 19:13 UTC
Related: #994592: Namespaces: Dublin Core (DC) and Dublin Core Terms (DCT). Just ignore my patch in there!
Comments
Comment #1
Blooniverse commented... I would naturally patch this, if 'you' like.
Comment #2
Blooniverse commentedComment #3
Blooniverse commented... any news? Any ideas? Any input?
Comment #4
Blooniverse commented... still no good news?
Comment #5
catchThis isn't major, if you have a proposal for a patch, uploading the patch and setting the issue to 'needs review' may encourage more people to look at the issue.
Comment #6
scor commentedThese are the namespaces for these vocabularies as defined in their specs. I know some of them don't resolve, but that's up to the maintainers of these vocabularies to fix that, not us. I'll check with them on the status of this. Either way, the status of these urls does not matter wrt to the RDFa in Drupal pages.
Comment #7
aspilicious commentedRemoving tags (needs backport to D7 queue cleanup)
Comment #8
Blooniverse commented@scor#6:
I am not in the dev mode at the moment, but as much as I remember, real/valid URLs are needed for the AJAX proposals via drop-down later on — when filling in the RDF fields (relation to vocabulary import?). Am I remembering wrongly? I have to admit that I never had the time to check the code of any of the RDF modules, so far. This here is just 'guessing something potentially observed'.
Comment #9
scor commentedThat's contrib, core does not do any of that importing RDF schema stuff... that's done in http://drupal.org/project/rdfx
Comment #10
scor commentedhttp://ogp.me/ns# was fixed a few days ago.
http://www.w3.org/2004/02/skos/core# resolves too.
no problem here.