Tony, Thanks. This responds to one of my key concerns with MARC as it
exists today, which is that many of the values that one can include in a
MARC record are defined in the standard itself (all of the indicators,
and most of the fixed fields). This means that if you want to add a
value to a value list, you need to make a change to the standard itself.
Moving those values outside of the standard solves that problem, but we
also need a way for library systems to be able to easily pick up updates
to these lists when they occur. So external but addressable lists, plus
a coordinated use of RSS to announce changes, and BINGO! We could gain a
great deal of flexibility. To do so, of course, we need a record
structure that can support list description.
kc
Hammond, Tony wrote:
>rdf:List - see
>
>RDF Vocabulary Description Language 1.0: RDF Schema
>W3C Recommendation 10 February 2004
>
>5.2 RDF Collections
>
>http://www.w3.org/TR/rdf-schema/#ch_collectionvocab
>
>Believe. :)
>
>(Closed collections introduced ionto the 2004 update of original 1999 RDF
>M=S spec.)
>
>Tony
>
>
>
>
>>-----Original Message-----
>>From: Metadata Object Description Schema List
>>[mailto:[log in to unmask]] On Behalf Of Karen Coyle
>>Sent: 11 July 2005 15:13
>>To: [log in to unmask]
>>Subject: Re: [MODS] library metadata and RDF
>>
>>
>>Houghton,Andrew wrote:
>>
>>
>>
>>>BTW, I should point out that had the authors of the MARC-XML
>>>specification created an element based XML grammar, rather
>>>
>>>
>>than a mixed
>>
>>
>>>element/attribute model, you could have dropped it directly into the
>>>RDF model with a simple RDFS schema
>>>
>>>
>>>
>>... snip ...
>>
>>
>>
>>>Try it at http://www.w3.org/RDF/Validator/ by copying the
>>>
>>>
>>above RDF-XML
>>
>>
>>>into the textbox and clicking the Parse RDF button.
>>>
>>>
>>>
>>>
>>Yes, this does parse. But unfortunately, both the
>>MARCXML-lite and this RDF-able version are far from full
>>schemas for MARC. A field like
>>
>>
>> <controlfield rdf:parseType="Resource">
>> <tag>008</tag>
>> <value>990101 n ancnnbabn n ana </value>
>> </controlfield>
>>
>>is actually a couple of dozen data elements, most of which
>>are controlled by an authority list. Which brings me to the
>>question: how does one indicate a finite set of values for a
>>field in RDF? Of course, it will use a URI to point to the
>>list, but what is the structure and what makes the list enforceable?
>>
>>kc
>>
>>
>>--
>>-----------------------------------
>>Karen Coyle / Digital Library Consultant
>>[log in to unmask] http://www.kcoyle.net
>>ph.: 510-540-7596
>>fx.: 510-848-3913
>>mo.: 510-435-8234
>>------------------------------------
>>
>>
>>
>
>********************************************************************************
>DISCLAIMER: This e-mail is confidential and should not be used by anyone who is
>not the original intended recipient. If you have received this e-mail in error
>please inform the sender and delete it from your mailbox or any other storage
>mechanism. Neither Macmillan Publishers Limited nor any of its agents accept
>liability for any statements made which are clearly the sender's own and not
>expressly made on behalf of Macmillan Publishers Limited or one of its agents.
>Please note that neither Macmillan Publishers Limited nor any of its agents
>accept any responsibility for viruses that may be contained in this e-mail or
>its attachments and it is your responsibility to scan the e-mail and
>attachments (if any). No contracts may be concluded on behalf of Macmillan
>Publishers Limited or its agents by means of e-mail communication. Macmillan
>Publishers Limited Registered in England and Wales with registered number 785998
>Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS
>********************************************************************************
>
>
>
>
--
-----------------------------------
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------
|