Hello,
great information, this is exactly what we were looking for. We will
carefully consider your valuable suggestions for a DC Subject compatible
tag for netinsert. We hope to be able to provide our end users with such an
option in the next release.
Thanks a million. We are honored to receive expertise help from the
professional meta data community in these matters.
Best regards,
Henrik Nyberg for NetInsert
P.S. A note to the people who have requested an RDF of the NetInsert
taxonomy: we haven't forgotten about it and it is still very much in the
roadmap. At this point however, we have no estimate of a release date for
the RDF.
----- Original Message -----
From: "Andy Powell" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, February 25, 2004 10:40 AM
Subject: Re: NetInsert subject classification scheme
>
> Henrik,
> (Apologies for a very delayed response!).
> One possible approach is that you 'name' your encoding scheme using a URI
> within your own namespace, e.g.
>
> http://www.netinsert.com/Taxonomy
>
> If you do this, then your XHTML encoding would be along the lines of
>
> <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
> <link rel="schema.NetInsert" href="http://www.netinsert.com/" />
>
> <meta name="DC.subject"
> scheme="NetInsert.Taxonomy"
> content="0.0.1.2.2.1"
> />
>
> This is in line with the XHTML encoding guidelines at
>
> http://dublincore.org/documents/dcq-html/
>
> and doesn't require any registration of 'NetInsert' with DCMI.
>
> Note that there are other possibilities for choosing the URI that you use
> to name your taxonomy - for example, you could use a PURL
>
> http://purl.org/netinsert/Taxonomy
>
> in which case the 'rel="schema' line above will need to be changed. Note
> also that there are psuedo-religious issues around whether you should use
> a URIref rather than a URI to name your scheme (i.e. whether it should
> have a '#' in it or not).
>
> The above approach can also be used if you choose a future encoding
> based on XML, where the instance metadata will look something like
>
> <dc:subject xsi:type="netinsert:Taxonomy">0.0.1.2.2.1</dc:subject>
>
> given an appropriate namnespace declaration for the 'netinsert' prefix.
> It will also work in RDF/XML (though the syntax is not as shown above).
>
> You might also like to consider assigning a URI (or URIref) to each of
> the terms in your taxonomy? If so, then a possible way of doing this is
> to use the 'info' URI scheme (though note that this isn't a registered URI
> scheme yet). For details see
>
> http://www2.elsevier.co.uk/~tony/info/info.html
>
> Some examples are at
>
> http://www2.elsevier.co.uk/~tony/info/info.html#ex_ddc
>
> Hope this helps,
>
> 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/
|