[osis-core] <subject type="LCSH">
Todd Tillinghast
osis-core@bibletechnologieswg.org
Wed, 17 Sep 2003 11:31:25 -0600
Patrick,
Can you give an example of the usage?
<subject type="LCSH">what goes here</subject>
It seems to me that these values are really things that should be PSIs,
at least we are using them in the same way we would use a PSI. The type
defines the "namespace" and the PSI value goes a PCDATA.
These names seem to come largely from the library community. If we
adopt this list of standard naming systems will it be confusing in the
future when/if we add a naming system that is not parallel to this set
of names?
Todd
> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Wednesday, September 17, 2003 6:36 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] <subject type="LCSH">
>
> Todd,
>
> So is this the proposal?
>
> Change:
>
> <xs:complexType name="subjectCT">
> <xs:simpleContent>
> <xs:extension base="xs:string">
> <xs:attributeGroup ref="globalWithType"/>
> <xs:attribute name="canonical" type="xs:boolean"
> use="optional"/>
> </xs:extension>
> </xs:simpleContent>
> </xs:complexType>
>
> To:
>
> <xs:complexType name="subjectCT">
> <xs:simpleContent>
> <xs:extension base="xs:string">
> <xs:attribute name="type" type="subjectType"
> use="optional"/>
> <xs:attributeGroup ref="globalWithoutType"/>
> <xs:attribute name="canonical" type="xs:boolean"
> use="optional"/>
> </xs:extension>
> </xs:simpleContent>
> </xs:complexType>
>
> Add:
>
> <xs:simpleType name="subjectType">
> <xs:union memberTypes="osisSubjects attributeExtension"/>
> </xs:simpleType>
>
> <xs:simpleType name="osisSubjects">
> <xs:restriction base="xs:string">
> <xs:enumeration value="ATLA"/>
> <xs:enumeration value="BILDI"/>
> <xs:enumeration value="DBC"/>
> <xs:enumeration value="DDC"/>
> <xs:enumeration value="EUT"/>
> <xs:enumeration value="FGT"/>
> <xs:enumeration value="LCSH"/>
> <xs:enumeration value="NLSH"/>
> <xs:enumeration value="RSWK"/>
> <xs:enumeration value="SEARS"/>
> <xs:enumeration value="SOG"/>
> <xs:enumeration value="SWD_RSWK"/>
> <xs:enumeration value="UDC"/>
> <xs:enumeration value="VAT"/>
> </xs:restriction>
> </xs:simpleType>
>
>
> Note that in the documentation we need to expand the values (should we
> list websites? I probably won't have time to find them all and some
are
> probably not online, like the Vatican one).
>
> ATLA: publications (subject listing not online, http://www.atla.com).
>
> BILDI: (Biblewissenschaftliche Literaturdokumentation Innsbruck,
> http://bibfutheol.uibk.ac.at/bildi).
>
> DBC: Dutch Basic Classification
>
> DDC: (Dewey Decimal System), http://www.oclc.org/dewey/.
>
> EUT: Estonian Universal Thesaurus
>
> FGT: Finnish General Thesaurus
>
> LCSH: Library of Congress site (http://www.loc.gov/).
>
> NLSH: National Library Subject Headings
> (http://mak.bn.org.pl/info/info19a.htm, Poland National Library)
>
> RSWK: Regeln für den Schlagwortkatalog
>
> SEARS: Sears List of Subject Headings
>
> SOG: Soggettario (Italian subject headings system)
>
> SWD_RSWK: Swiss National Library
>
> UDC: Universal Decimal Classification
>
> VAT: Vatican Library subject headings
>
>
> Use of this attribute means that the subject is as declared in that
> system. Informative value only.
>
> Probably should note that this is a starter set, British Library lists
> its classification system as "various." ;-)
>
> Hope everyone is having a great day!
>
> Patrick
>
>
>
>
> Todd Tillinghast wrote:
> > Agree, we don't have to have an exhaustive list inorder to address
needs
> > we know of today.
> >
> > Todd
> >
> >
> >>-----Original Message-----
> >>From: osis-core-admin@bibletechnologieswg.org
> >>[mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of
> >>Chris Little
> >>Sent: Tuesday, September 16, 2003 3:42 PM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: Re: [osis-core] <subject type="LCSH">
> >>
> >>
> >>
> >>
> >>Patrick Durusau wrote:
> >>
> >>
> >>>Chris,
> >>>
> >>>A little more explanation?
> >>>
> >>>Where would we add subjectCT and what would be its content model?
> >>>
> >>>Note that we already have a subject element in the header
> >>
> >>(from Dublin
> >>
> >>>Core). It does not have enumerated types. Are you
> >>
> >>suggesting LCSH be its
> >>
> >>>type attribute and control the content of <subject>?
> >>
> >>Addition of LCSH as a possible value for <subject>'s type
> >>attribute is
> >>exactly what I'm suggesting.
> >>
> >>
> >>>There are a number of other systems, Dewey, one by the American
> >>>Theological Libraries Association, one by the Pontifical Biblical
> >>>Institute, any number of systems in use in Europe. Don't
> >>
> >>know that we
> >>
> >>>can generate a really comprehensive list quickly.
> >>
> >>Other types like Dewey or ATLA, assuming we can find a standard
> >>name/abbreviation for them would be great too. If we can't be
> >>comprehensive, at least permitting some of the most common
> >>values would
> >>be of benefit.
> >>
> >>--Chris
> >>
> >>
> >>
> >>_______________________________________________
> >>osis-core mailing list
> >>osis-core@bibletechnologieswg.org
> >>http://www.bibletechnologieswg.org/mailman/lis> tinfo/osis-core
> >>
> >
> >
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >
>
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
>
> Topic Maps: Human, not artificial, intelligence at work!
>
>
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core