> From [log in to unmask] Thu May 8 11:23 MET 2003
> X-RAL-MFrom: <[log in to unmask]>
> X-RAL-Connect: <pat.bath.ac.uk [138.38.32.2]>
> RDF-XML: <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:dc="http://purl.org/dc/elements/1.1/"> <rdf:Description
> about=""> <dc:publisher> UKOLN - University of Bath </dc:publisher>
> </rdf:Description> </rdf:RDF>
> DC.Publisher: UKOLN - University of Bath
>
> On Thu, 8 May 2003, Roland Schwaenzl wrote:
>
> > > >
> > > > I agree: The main point in updating the DC in HTML recommendation
> > > > is to bring it in alignment with HTML4/XHTML1 -
> > > >
> > > > The <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/">
> > > > construction seems subtle in this respect.
> >
> > "schema.dc" is a value for the "rel" attribute, which is not a built in
> > value for HTML4. So an application FIRST needs to learn the
> > meaning of rel="schema.dc" -
>
> Roland, you still haven't answered my simple question. Are you suggesting
> the use of profile instead of rel="schema.dc" or in addition to it.
The good old rfc also hints at rel="schema.something" - so i think we eventually
want both to indicate a general functionality we load on specifically structured
values of the "rel" attribute, which affect the interpretation of values of
the "name" and "scheme" attribute to "meta" and possibly also other values of "link" attributes.
> I.e.
> are you propsoing that the following example should be
>
> Option 1 (as per my current draft)
> --------
>
> <head>
> <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/" />
> <link rel="schema.dcterms" href="http://purl.org/dc/terms/" />
> <meta name="dcterms:modified"
> scheme="dcterms:W3CDTF"
> content="2003-05-05" />
> <link rel="dc:relation"
> href="http://www.ukoln.ac.uk" />
> </head>
>
> Option 2
> --------
>
> <head profile="http://purl.org/dc/">
> <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/" />
> <link rel="schema.dcterms" href="http://purl.org/dc/terms/" />
> <meta name="dcterms:modified"
> scheme="dcterms:W3CDTF"
> content="2003-05-05" />
> <link rel="dc:relation"
> href="http://www.ukoln.ac.uk" />
> </head>
>
> Option 3
> --------
>
> <head profile="http://dublincore.org/documents/dcmi-terms/">
> <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/" />
> <link rel="schema.dcterms" href="http://purl.org/dc/terms/" />
> <meta name="dcterms:modified"
> scheme="dcterms:W3CDTF"
> content="2003-05-05" />
> <link rel="dc:relation"
> href="http://www.ukoln.ac.uk" />
> </head>
>
> Option 4
> --------
>
> <head profile="http://purl.org/dc/">
> <meta name="modified"
> scheme="W3CDTF"
> content="2003-05-05" />
> <link rel="relation"
> href="http://www.ukoln.ac.uk" />
> </head>
>
> Please answer 1, 2, 3, 4 ("can I have a liitle more" - sorry, I watched
> Yellow Submarine the other day!) or provide an alternative suggestion.
I would prefer NOT to create too many values for the "rel" attribute -
as <meta name="dc:relation" content="http://foo.org/"/> appears as a synomym.
Or do you want to get other "link" attributes involved as well?
Thinking about a suitable URI a little more i would suggest to use the
DC-(X)HTML specifications URI. Probably that specification should eventually
become an informational RFC, as it will not just talk about DC but also
suggests coding for other metadata vocabularies in (X)HTML.
The RFC should have a reference to the URI used in Option 3, but the
RFC will generally explain the method of indirect vocabulary identification.+ declaration
by means of <link rel="schema.something" href="aSomethingTermDeclaration"/> and
dc.a.b handling...equivalence with dcterms.b, colon style notation....
That RFC could supersede the old one effectively (as i hope).
rs
>
> If, the answer is either 2 or 4, what should the http://purl.org/dc/ PURL
> resolve to or doesn't it matter??
>
> Sorry to be dense!
>
> Andy.
>
> > I think it would be an excellent idea to incorporate (non-normatively) a perl script with the profile, which
> > executes the directive.
>
> and produces what? RDF/XML?
> (I agree with Pete that XSLT would be better).
>
> Andy
> --
> Distributed Systems, UKOLN, University of Bath, Bath, BA2 7AY, UK
> http://www.ukoln.ac.uk/ukoln/staff/a.powell +44 1225 383933
> Resource Discovery Network http://www.rdn.ac.uk/
>
>
|