DCMI coins URI for self - requests check
Thomas Baker
DCMI has coind a URI to identify itself (i.e., the organization
Dublin Core Metadata Initiative Ltd) [1]. The URIs [1,2] return
the response code 302 and redirect to [3], the contents of which
are appended below.
We would like to promote this URI with a little news item (as an
example of how to publish a URI for oneself), but before doing
so would appreciate some extra eyes on this list to take a
closer look at the details. For example, should [1] return 303?
Many thanks,
Tom
[1] http://purl.org/dc/aboutdcmi#DCMI
[2] http://purl.org/dc/aboutdcmi
[3] http://dublincore.org/DCMI.rdf
----------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:foaf="http://xmlns.com/foaf/0.1/" >
<foaf:Organization rdf:about="http://purl.org/dc/aboutdcmi#DCMI">
<foaf:name>Dublin Core Metadata Initiative</foaf:name>
<foaf:nick>DCMI</foaf:nick>
<foaf:homepage rdf:resource="http://dublincore.org/" />
<rdfs:seeAlso rdf:resource="http://purl.org/dc/aboutdcmi" />
<dct:description>The Dublin Core Metadata Initiative is an open forum engaged
in the development of interoperable online metadata standards that support a broad
range of purposes and business models. DCMI's activities include consensus-driven
working groups, global conferences and workshops, standards liaison, and educational
efforts to promote widesp read acceptance of metadata standards and practices.</dct:description>
<dct:created>1995-01-03</dct:created>
<dct:subject rdf:resource="http://id.loc.gov/authorities/sh96000740#concept"/>
<dct:subject rdf:resource="http://id.loc.gov/authorities/sh98002267#concept"/>
</foaf:Organization>
</rdf:RDF>
--
Tom Baker <tba...@tbaker.de>
Stuart A. Yeates
between DCMI (the organisation) and DC (the metadata schema). Since
confusion between these two is likely, I'd be very tempted to include
information about DCMI as publisher of DC in there, to make the
relationship explicit.
cheers
stuart
Richard Cyganiak
The documentation for foaf:nick states: “The nick property relates a
Person to a short (often abbreviated) nickname, such as those use in
IRC chat, online accounts, and computer logins.” The property's range
is undeclared in the RDFS file, so this should be considered a buglet
in FOAF. But till it's resolved, it's perhaps better to avoid the
property's use for non-foaf:Persons.
I would prefer if the dct:created literal was a typed literal with
datatype xsd:date, although a plain literal is correct as well.
An addition of foaf:logo to the description would be a nice touch.
There should be some metadata about the *file* that describes the DCMI
as well, that is, some statements about <http://dublincore.org/
DCMI.rdf>. I would recommend to state values for the properties
dct:title, dct:created, dct:modified, dct:license, dct:creator,
foaf:primaryTopic.
A human-readable variant of the RDF file, served via content
negotiation, would be quite nice. On Apache, this can be done quite
easily by enabling the multi_views module, and adding a </DCMI.html>
file. Apache turns </DCMI> into a generic content-negotiated document.
As Stuart already said, DCMI is perhaps best known for the DC Element
Set. You could state that DCMI created it, perhaps both in the
dct:description and explicitly in RDF triples. This would help pinning
down the referent of the URI.
Best,
Richard
Thomas Baker
> I think the obvious thing missing from this is a clear distinction
> between DCMI (the organisation) and DC (the metadata schema). Since
> confusion between these two is likely, I'd be very tempted to include
> information about DCMI as publisher of DC in there, to make the
> relationship explicit.
Very good point. We may need a few more URIs.
Thank you,
Tom
--
Tom Baker <tba...@tbaker.de>
Thomas Baker
> Nice work!
:-)
> The documentation for foaf:nick states: ?The nick property relates a
> Person to a short (often abbreviated) nickname, such as those use in
> IRC chat, online accounts, and computer logins.? The property's range
> is undeclared in the RDFS file, so this should be considered a buglet
> in FOAF. But till it's resolved, it's perhaps better to avoid the
> property's use for non-foaf:Persons.
Well spotted.
> I would prefer if the dct:created literal was a typed literal with
> datatype xsd:date, although a plain literal is correct as well.
Good.
> An addition of foaf:logo to the description would be a nice touch.
Ooh - nice idea.
> There should be some metadata about the *file* that describes the DCMI
> as well, that is, some statements about <http://dublincore.org/
> DCMI.rdf>. I would recommend to state values for the properties
> dct:title, dct:created, dct:modified, dct:license, dct:creator,
> foaf:primaryTopic.
Okay.
> A human-readable variant of the RDF file, served via content
> negotiation, would be quite nice. On Apache, this can be done quite
> easily by enabling the multi_views module, and adding a </DCMI.html>
> file. Apache turns </DCMI> into a generic content-negotiated document.
Good next steps.
> As Stuart already said, DCMI is perhaps best known for the DC Element
> Set. You could state that DCMI created it, perhaps both in the
> dct:description and explicitly in RDF triples. This would help pinning
> down the referent of the URI.
Got it. All very useful suggestions - thanks!