> From [log in to unmask] Mon May 12 15:14 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:
>
> > 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.
>
> Why? This recommendation is no more or less DC-centric than the XML
> guidelines document is it? All the other DCMI encoding documents are DCMI
> recommendations... why should the XHTML one be issued in a different way.
> Either they should all be RFCs or they should all be DCMI recommendations.
> Shouldn't they?
1. The former DC in HTML was issued as an RFC
2. rel="schema.something" is in fact a general suggestion, which allows for
mixing of arbitrary vocabularies in HTML.
Language: In the "abstract model" values of properties are required as
"literal string", but URIs in links are adressed as URIs for "another resource".
"link" Attributes: Is a dc-application assumed to ignore all other "link" tag attributes.
is "rel=copyright" the only built in "link" type, which is to be honoured by a dc-application?
rs
>
> 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/
>
>
|