On Wed, 8 Oct 2003, NetInsert wrote:
> speaking as a representative for the NetInsert web directory,
> http://www.netinsert.com , I would like to register the NetInsert
> taxonomy system as a subject vocabulary with the Dublin Core Meta
> Initiative.
>
> NetInsert is the world's first fully automated web directory engine. A
> web directory engine organizes the web pages in the same way as a
> traditional directory, but retrieves and updates the information for the
> pages in the same way that a search engine does.
>
> At the heart of the NetInsert web directory paradigm lies the use of
> meta data. We firmly believe in the use of meta data as a powerful
> technology for describing properties of a web page such as the subject
> and the geographical location of that subject.
>
> In order to index a web page with the NetInsert directory a meta tag
> referencing a category address in the NetInsert taxonomy must be defined
> in the page. For example, defining the following tag:
>
> <meta name="netinsert" content="0.0.1.2.2.1">
>
> will make it possible to index the page in the category Industries in World:
>
> http://www.netinsert.com/dir/0.0.1.2.2.1.html
>
> NetInsert is not a major directory today and is currently in a build up
> phase with a growing number of users every month. During this process,
> some of our users have requested that we try to standardize the use of
> the netinsert meta tag, for example as a registered classification
> scheme with the DCMI.
>
> If this is of interest to you we would like to offer our users a DCMI
> version of the subject category tag. For the above example, the tag
> could look like:
>
> <meta name="DC.Subject.Classification" scheme="netinsert.com" content="1.2.1.2.3">
>
> or alternatively:
>
> <meta name="DC.Subject.Classification" scheme="netinsert" content="1.2.1.2.3">
>
> If this acceptable to you we need to know if there are any
> specifications or documentation that we need to submit in order to have
> the netinsert taxonomy registered as vocabulary with DCMI. Meanwhile, a
> further introduction of the NetInsert directory and its taxonomy is
> given on the help pages:
>
> http://www.netinsert.com/en/index.html
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/
|