W3C home > Mailing lists > Public > public-xg-lld@w3.org > September 2011

Re: Library data is expressed primarily as text strings

From: ZENG, MARCIA <mzeng@kent.edu>
Date: Mon, 5 Sep 2011 11:26:46 -0400
To: Emmanuelle Bermes <manue@figoblog.org>, Antoine Isaac <aisaac@few.vu.nl>
CC: "public-xg-lld@w3.org" <public-xg-lld@w3.org>
Message-ID: <CA8A6112.EF46%mzeng@kent.edu>

>On Mon, Sep 5, 2011 at 10:00 AM, Antoine Isaac <aisaac@few.vu.nl> wrote:
>> Bouncing on that thread, I'd like to mention that the section
>> following this one, "Library controlled vocabularies are expressed as
>> strings", is slightly redundant, see:
>> I'm also not fond of the heading "Library controlled vocabularies are
>> expressed as text strings": the vocabularies as a whole are expressed as
>> structured data, even though this data relies  on strings, mostly...

I especially agree with Antoine about this heading ""Library controlled
vocabularies are
expressed as text strings". The text strings are usually used as the
values in practices. A vocabulary itself does not have to be
expressed/represented in only one way.

>> Is there any objection to my trying to merge the two in the coming
>> Antoine
>>> I found the point "Library data is expressed primarily as text
>>>strings" to
>>> be
>>> vague as written, so I have sharpened the point [1] to emphasize the
>>> difference
>>> between "unique alphanumeric strings" such as ISBNs and
>>> text"
>>> such as "words and names".  Please read the following paragraph and
>>> a
>>> flag if I have somehow "overinterpreted"...:
>>>     Most information in library data is encoded as display-oriented
>>>     strings. Some of the resource identifiers used in library data are
>>> based on
>>>     unique alphanumeric strings, such as ISBNs for books, but most
>>>     identification is done using words and names.  Some data fields in
>>> MARC
>>>     records are coded uniquely, but there is no clear incentive to
>>>     these in all records as few of them are used for library-system
>>> functions.
>>>     Some data fields, such as authority-controlled names and subjects,
>>> have
>>>     associated records in separate files, and these records have
>>> identifiers
>>>     that could be used to represent those entities in library metadata;
>>>     however, the data formats in current use do not always support
>>> inclusion of
>>>     these identifiers in records, so many of today's library systems do
>>> not
>>>     properly support their use.
>>> Note "authority-controlled" with hyphen.
>>> Tom
>>> [1]
Received on Monday, 5 September 2011 15:27:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:58 UTC