Dear all,

I am including the following in the "etc" category.

I will generate a new packet tomorrow "for the record" -
this will only affect the numbering of page 131 (out of 132).

Tom


Small problem with namespace documents

-- Pete has pointed out that dcterms:publisher is used with a literal
   value in the namespace documents for http://purl.org/dc/terms/, etc
   http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0802&L=dc-usage&P=2654

   In
        http://purl.org/dc/elements/1.1/
        http://purl.org/dc/terms/
        http://purl.org/dc/dcmitype/
        http://purl.org/dc/dcam/
   we say

        Namespace-URI dcterms:publisher "The Dublin Core Metadata
        Initiative"@en-US .

   i.e. we use the new dcterms:publisher property with a literal value.

   But the definition of that new property says the range of
   dcterms:publisher is the class dcterms:Agent.

   i.e. I think we've been tripped up by our own introduction of ranges.

   I think we need to do one of the following:

   (i) revert to using the dc:publisher property, for which range is
   unspecified so a literal object is OK (even if a bit absurd in some
   ways)
   (ii) change to using a blank node as object

   Namespace-URI dcterms:publisher _:x .
   _:x rdf:value "The Dublin Core Metadata Initiative"@en-US .

   (iii) coin a URI for DCMI as Agent and use that as object (and ideally
   that URI should either be a # URI or do the 303 thing because
   DCMI-as-Agent is not an information resource). (Maybe we already have a
   PURL that serves this purpose, but I suspect we aren't very clear about
   whether many of the existing PURLs (other than the term URIs) denote
   docs or other things)

   I'm guessing this is actually generated by the scripts so may need
   someone to tweak them.


-- 
Dr. Thomas Baker <[log in to unmask]>
Director, Specifications and Documentation
Dublin Core Metadata Initiative