Hi Paul,
Apologies for the belated response - I've been on leave and just come
back to work....
> I'm currently looking at implementing the 2008 DC profile to
> allow GRDDL transformations.
Just so that there's no confusion, I think we're talking about the
"DC-HTML" HTML meta data profile
http://dublincore.org/documents/2008/08/04/dc-html/
> There are a couple of points
> that I'd like to try and get clarification on if I can. I'm
> deeper into DC than ever before so hopefully I haven't
> misunderstood too much!
I think you're on the right track :-)
> 1) The profile states that VES is not supported. Does this
> mean that the scheme attribute should not now be included in
> the HTML if the scheme is a VES?
That's correct. The meta element is used only to represent statements
referring to literal values, and so the scheme attribute is used to
encode the URI of a syntax encoding scheme/datatype, not the URI of a
vocabulary encoding scheme.
> I'm actually concerned about
> eGMS.IPSV, which I consider to be a VES. On a similar note
> (if this is the case) should I remove
> scheme="DCTERMS.DCMIType", as according to the DC website
> this is also a VES (http://dublincore.org/documents/dcmi-terms/#H4).
Yes. There's no way of encoding this information using the DC-HTML
profile. It's a limitation which we couldn't see a solution to, at least
sticking to using existing HTML elements/attributes.
> 2) I've been using the GRDDL transformation for the 2008
> profile. However, it is also outputting non-DC statements. Is
> this not incorrect? Should it not be limited to the
> namespaces handled within the profile?
The aim is that the profile should support property URIs (as name and
rel attribute values) and syntax encoding scheme URIs (as scheme
attribute values) from any "namespaces" (i.e. not only DCMI-owmed URIs),
by abbreviating/encoding them using the "prefixed name" convention
described in section 3.1.2 of the document.
So, using the DC-HTML profile, the value of the @name attribute in the
following example would be mapped to the property URI
http://example.org/terms/date.removed
<link rel="schema.XX" href="http://example.org/terms/" >
<meta name="XX.date.removed" content="2007-05-05" >
The mapping isn't limited to some fixed set of URIs or some fixed set of
strings used as values of the name attribute.
Pete
---
Pete Johnston
Technical Researcher, Eduserv Foundation
[log in to unmask]
+44 (0)1225 474323
http://www.eduserv.org.uk/foundation/
http://efoundations.typepad.com/efoundations/
|