Andy Powell wrote:
> I remain unconvinced that this is 'only a slight constraint' on the XML
> representation. Making RDF mandatory is at odds with keeping things
> simple.
>
> The examples in my document are not valid RDF...
>
> <?xml version="1.0"?>
>
> <metadata
> xmlns="http://myorg.org/myapp/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://myorg.org/myapp/
> http://myorg.org/myapp/schema.xsd"
> xmlns:dc="http://purl.org/dc/elements/1.1/">
> <dc:title>
> UKOLN
> </dc:title>
> <dc:subject>
> national centre, network information support, library
> community, awareness, research, information services,public
> library networking, bibliographic management, distributed
> library systems, metadata, resource discovery,
> conferences,lectures, workshops
> </dc:subject>
> <dc:description>
> UKOLN is a national focus of expertise in digital information
> management. It provides policy, research and awareness services
> to the UK library, information and cultural heritage communities.
> UKOLN is based at the University of Bath.
> </dc:description>
> <dc:publisher>
> UKOLN, University of Bath
> </dc:publisher>
> <dc:identifier>
> http://www.ukoln.ac.uk/
> </dc:identifier>
> <dc:date>
> 2001-07-18
> </dc:date>
> </metadata>
>
> It is more less the XML representation used in OAI for example. What
> needs to change to make this valid RDF?
Just replace <metadata> with <rdf:RDF><rdf:Description>:
<?xml version="1.0"?>
<rdf:RDF
xmlns="http://myorg.org/myapp/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://myorg.org/myapp/schema.xsd"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description>
<dc:title>
UKOLN
</dc:title>
<dc:subject>
national centre, network information support, library
community, awareness, research, information services,public
library networking, bibliographic management, distributed
library systems, metadata, resource discovery,
conferences,lectures, workshops
</dc:subject>
<dc:description>
UKOLN is a national focus of expertise in digital information
management. It provides policy, research and awareness services
to the UK library, information and cultural heritage communities.
UKOLN is based at the University of Bath.
</dc:description>
<dc:publisher>
UKOLN, University of Bath
</dc:publisher>
<dc:identifier>
http://www.ukoln.ac.uk/
</dc:identifier>
<dc:date>
2001-07-18
</dc:date>
</rdf:Description>
</rdf:RDF>
You can verify it with CARA
http://zoe.mathematik.Uni-Osnabrueck.DE/RDF/parser.html
This is a slightly change, isn't it? You have just to reflect the
replacement of of the XML root element <metadata> with
<rdf:RDF><rdf:Description> in your XML Schema.
>
> I would argue that these examples are very much the kind of XML people
> implementing DC in XML will come up with. How are schemes handled in HTML
> and XHTML?
Since the RDF serialization is represented in XML I don't see
the difference for RDF and XML here. This is a general problem
for XML. However, you can simply embed RDF in XHTML using the
abbreviated RDF syntax.
> As an attribute on the <meta> element. That is the intuitive
> way of expressing a scheme IMHO and very much in line with the xml:lang
> mechanism. To suggest to people that they do otherwise is to ask them to
> do non-intuitive things :-( .
Sorry, I don't understand ;-). Can you explain how you want to use
the <meta> element?
Best regards,
Stefan
|