Andy,
See http://stage.dublincore.org/usageboard/2006/2006-02.dcsv/2006-03-04.dcmi-dcsv.shtml.
In transferring the text, I made various changes in the
following paragraphs:
<p>As of 2006, when this specification was revised, the
DCMI Usage Board encourages implementors to describe the
value resource of a property more fully, where necessary, by
making it the subject of an additional description. In terms
of the the DCMI Abstract Model, this means creating a "related
description" within the context of a "description set".</p>
<p>Using a related description in this way places all of
the information in a description set within the context of
the DCMI Abstract Model, helping to ensure that recipients
of the metadata will be able to parse and understand it.
In contrast, the use of DCSV-encoded strings for the
description of the value resource forces recipients of the
metadata to understand both the DCMI Abstract Model and the
DCSV specification described here.</p>
<p>Despite these limitations, implementers may want to use
DCSV-encoded strings in situations where the chosen encoding
syntax used by the application does not support related
descriptions (e.g., XHTML) or where there is a significant
legacy adoption of DCSV-encoded structured value strings
within a community.</p>
...
<p>Note also that as of 2006, for the reasons outlined above,
it is unlikely that the DCMI Usage Board will endorse any
new DCMI-maintained terms based on the DCSV specification.</p>
A few comments:
-- I changed "DCSV-encoded structured value strings" to
"DCSV-encoded strings". Is anything important lost in doing so?
-- Used "value resource" because the phrase "describe the value"
could be misunderstood by people who do not know the DCAM.
I also changed s/DAM/DCAM/ throughout.
Tom
On Sat, Mar 04, 2006 at 08:41:19AM -0000, Andy Powell wrote:
> To do the first, I suggest slightly revising the document structure, moving the first two paragraphs of section 2:
>
> --- cut ---
> This document describes a particular method for encoding simple structured data within a value string. In the DCMI Abstract Model [DAM], a value string is defined as "a simple string that represents the value of a property". Value strings encoded according to the method described in this document are referred to here as structured value strings.
>
> (Note that for historical reasons, the method itself is still referred to here as the DCSV Syntax, or DCSV. "DCSV" originally stood for "Dublin Core Structured Value", a legacy concept from circa 1997 which no longer has a place in today's DCMI Abstract Model [DAM].)
> --- cut ---
>
> up to form the tail end of 1. Introduction. Then add, soething along the lines of:
>
> --- cut ---
> In general, the DCMI Usage Board encourages implementors to make use of the 'related description' feature of the DCMI Abstract Model, i.e. adding an additional description to the description set, to fully describe the value of a property where necessary. This places all the information in the description set within the context of the DCMI Abstract Model, helping to ensure that recipients of the metadata will be able to parse and understand it. Making use of DCSV-encoded structured value strings forces recipients of the metadata to understand both the DCMI Abstract Model and the DCSV specification described here. However, there may be some exceptions to this guidance. For example, where the chosen encoding syntax used by the application does not support related descriptions (e.g. XHTML) or where there is a significant legacy adoption of DCSV-encoded structured value strings within a community.
> --- cut ---
>
> To do the second, I would add a new section 3.
>
> --- cut ---
> 3. DCSV syntax encoding schemes
>
> Where DCSV-encoded structured value strings are used, this should be indicated by using a syntax encoding scheme. For example, the DCMI endorsed DCMI Period encoding scheme should be used as follows in XHTML:
>
> <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
> <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
> <meta name="DC.coverage"
> scheme="DCTERMS.Period"
> content="name=The Great Depression; start=1929; end=1939;" />
>
> Note that 'DCSV' itself should not be used as a syntax encoding scheme. Implementors should use the DCSV specification to derive application-specific syntax encoding schemes where necessary.
>
> Note also that, for the reasons outlined above, it is unlikely that the DCMI Usage Board will endorse any new DCMI-maintained terms based on the DCSV specification.
> --- cut ---
--
Dr. Thomas Baker [log in to unmask]
Director, Specifications and Documentation
Dublin Core Metadata Initiative
|