 |
 |
> From [log in to unmask] Wed Dec 11 15:36 MET 2002 > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > X-Priority: 3 (Normal) > X-MSMail-Priority: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > Importance: Normal > Date: Wed, 11 Dec 2002 14:39:24 -0000 > From: Pete Johnston <[log in to unmask]> > Subject: Clarifying dumb-down (Was RE: RDF typed literals and DC encoding > schemes) > To: [log in to unmask] > > Picking up Roland's point here.... > > > Without a given literal to value map the datatype encoding > > style produces a serious problem to dc-dumbdown. > > > > A dc:subject content 061(40) in my view is not to be > > recommended as a dumbdown from dc:subject scheme="UDC" > > content="061(40)". > > > > This is NOT a syntax issue, as you seem to imply. > > > > The xml guideline suffers from the same problem. > > I think I understand the point Roland is making here (which I agree is > syntax independent): in > > > dc:subject content 061(40) > > the literal string "061(40)" is the value of the attribute. > > In > > > dc:subject scheme="UDC" content="061(40)" > > the value of the attribute is the result of a transformation process > performed on the literal "061(40)", where the transformation is defined > by the scheme/datatype. > > This became particularly apparent in the (syntax-specific) discussion of > the xs:anyURI datatype and escaped characters and so on > > http://www.jiscmail.ac.uk/cgi-bin/wa.exe?A2=ind0210&L=dc-architecture&T= > 0&F=&S=&P=7120 > > and follow-ups (when I undertook to explore some examples which I fear I > still haven't had time to do). > > But I suspect that many implementations of dumb-down in DC metadata have > not taken this "datatype-aware" approach, and _have_ simply discarded > the "scheme" information. This certainly seems to be the behavior > suggested by > > http://dublincore.org/documents/usageguide/#dumbdown > > Are we saying this blunter, less sophisticated approach to dumb-down is > incorrect? I'm more and more getting to that the "easy" approach to dumbdown may result in a de-valuation of dc-simple. It makes for a lot of really unqualified records - even, when they are syntactically "simple". Many applications use schemes - in particular for subject (as is recommended already with elements/1.1/ ) Exporting such records by discarding the scheme information makes the information useless, to say the least. IMO "easy dumb" should only be considered as an escape in case a "simple dumb" is not possible. "Ignoring" should not be the same as "Discarding the de-coding information". rs > > Pete > >