> From [log in to unmask] Mon Dec 3 19:13 MET 2001
> X-Accept-Language: en
> MIME-Version: 1.0
> Date: Mon, 3 Dec 2001 12:53:03 -0500
> From: Geoff Mottram <[log in to unmask]>
> Subject: Dublin Core and XML
> To: [log in to unmask]
> Content-Transfer-Encoding: 8bit
> X-MIME-Autoconverted: from quoted-printable to 8bit by scarlett.mathematik.Uni-Osnabrueck.DE id TAA03616
>
> I read with interest the draft proposals "Expressing Simple Dublin Core
> in RDF/XML" and "Expressing Qualified Dublin Core in RDF/XML." I have
> the following comments:
>
> 1) Although these drafts are both excellent,
Thank's...
> I don't agree that RDF must
> be a requirement for XML documents containing Dublin Core data elements.
The intention is: If you want to use RDF then do ...
[...]
> Either way, I would like to see a separate
> recommendation or standard for how to construct plain Dublin Core XML
> documents.
...is under preparation.
>
> 2) The Dublin Core documentation seems to lack a description for how to
> create consistent, unique and legal XML element and attribute names from
> the Dublin Core element sets, qualifiers and application profiles. The
> recent Dublin Core Namespaces recommendation provides the following
> references to RDF documents:
>
> http://purl.org/dc/elements/1.1/
> http://purl.org/dc/terms/
> http://purl.org/dc/dcmitype/
>
> Human documentation would be helpful to describe the naming conventions
> being used. I gather that the core elements are now all lower case
> (title, creator, publisher, etc.) and the qualifiers can be a mixed bag
> (subject, SubjectScheme, LCSH, etc.). Are there any guidelines for how
> to capitalize Dublin Core element names
There are schema attached to both prop.recs. for clarification.
You will be able to get the answers you want from the dc-registry.
> and how to handle spaces and
> other illegal XML name characters. For example the Government
> Application profile includes element names such as "Date ¦ Acquired",
> "Date ¦ created" and "Language ¦ ISO639-2/B".
Please don't read the proposal for a Gov Profile as xml. It's
human readable documentation.
The intention there is to say for instance: Use ISO639-2/B as encoding
scheme for the language element.
Best,
rs
> If implementors devise
> their own naming conventions, Dublin Core will loose much of its
> strength as a method of exchanging metadata.
>
> Thank you.
>
> Sincerely,
>
> Geoff Mottram
> [log in to unmask]
>
|