W3C home > Mailing lists > Public > www-zig@w3.org > November 2001

RE: holdings-schema proposal

From: Leif Andresen <LEA@bs.dk>
Date: Thu, 29 Nov 2001 13:52:20 +0100
Message-ID: <B30E4885F1ECD2119DD40000D11B66DD82C176@bobmail.bsintern.bs.dk>
To: www-zig@w3.org
May be this can make it more clear:

The Enumaration element contains
 - enumLevel - an Integer
 - enumCaption - an InternationalString
 - specificEnumeration - an InternationalString
(ref: http://lcweb.loc.gov/z3950/agency/defns/holdings.html)

This part of Holdings Schema is based on MARC21, see:
http://www.loc.gov/marc/holdings/echdenum.html

In consequence you can't write "volume 5, issue 2" - you need two
Enumaration elements:

 - enumLevel = 1
 - enumCaption = volume
 - specificEnumeration = 5
AND
 - enumLevel = 2
 - enumCaption = issue 
 - specificEnumeration = 2

Element "childEnumChronology" is not a part of Holdings Schema.
But childEnumChronSummary is and it can be:

childEnumChronSummary-structured = same structure as above
OR
childEnumChronSummary- unstructured = just an InternationalString

But not a detailed level: childEnumChronSummary is for ESN B2. 
"volume 5, issue 2" is a more detailed level - for ESN B3.

But: we have a structure in data (e.g. "volume 5, issue 2") and in the
schema (see Enumaration above).
We non't need a flat text-string.

Hope this makes it clear.

best regards
Leif Andresen


> -----Oprindelig meddelelse-----
> Fra: Janifer Gatenby [mailto:janifer@wanadoo.fr]
> Sendt: 29. november 2001 11:04
> Til: Johan Zeeman; Ray Denenberg; www-zig@w3.org
> Cc: Janifer Gatenby
> Emne: Re: holdings-schema proposal
> 
> 
> I'm still unclear.
> 
> bibPart can contain one or more childBibParts.  childBibParts 
> have the same
> structure as bibPart.
> 
> childEnumChronSummary is an element of bibPart and is only included in
> element sets that don't iterate all the children.  I can't find
> childEnumChronology - do I have the latest version?
> 
> If all the children are iterated, then I understand that 
> there is a need for
> enumeration and chronology as an unstructured string.  Therefore the
> proposal to allow this in alternativeEnumeration
> 
> Janifer Gatenby
> Pica ITC Consultancy
> +31 71 5246  500 (tel)
> +31 71 5223 119 (fax)
> janifer.gatenby@pica.nl)
> 
> ----- Original Message -----
> From: "Johan Zeeman" <joe.zeeman@tlcdelivers.com>
> To: "Janifer Gatenby" <janifer@wanadoo.fr>; "Ray Denenberg" 
> <rden@loc.gov>;
> <www-zig@w3.org>
> Cc: "Janifer Gatenby" <janifer.gatenby@pica.nl>
> Sent: Wednesday, November 28, 2001 5:04 PM
> Subject: Re: holdings-schema proposal
> 
> 
> > It's already available in ChildEnumChronology.
> >
> > j.
> >
> > ----- Original Message -----
> > From: "Janifer Gatenby" <janifer@wanadoo.fr>
> > To: "Ray Denenberg" <rden@loc.gov>; <www-zig@w3.org>
> > Cc: "Janifer Gatenby" <janifer.gatenby@pica.nl>
> > Sent: Wednesday, November 28, 2001 9:40 AM
> > Subject: Fw: holdings-schema proposal
> >
> >
> > > Ray said:  "It is claimed that the schema cannot express
> > > "volume 5, issue 2" as a flat value. (Why it can't isn't
> > > clear to me...."
> > >
> > > It's not clear to me either.
> > >
> > > Can we allow unstructured string data in 
> "alternativeEnumeration" and
> > > "alternativeChronology" so that it can be used for simple 
> flat display?
> > >
> > >
> > > Janifer Gatenby
> > > Pica ITC Consultancy
> > > +31 71 5246  500 (tel)
> > > +31 71 5223 119 (fax)
> > > janifer.gatenby@pica.nl)> 
Received on Thursday, 29 November 2001 07:51:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 October 2009 06:12:22 GMT