call number

[connie]

Hi Fred and Bruce --
Congrats on the release! Making my way through it....

On that note: I didn't notice a type for call number.... Are we meant
to use bibo:locator?
Thanks!

[Frederick Giasson]

Hi Connie,

> On that note: I didn't notice a type for call number.... Are we meant
> to use bibo:locator

I don't think so.

Could foaf:phone fill the gap?

Bruce, any ideas?

Take care,

Fred

[Bruce D'Arcus]

On Mon, Jun 9, 2008 at 8:12 AM, Frederick Giasson <fr...@fgiasson.com> wrote:
>
> Hi Connie,
>
>> On that note: I didn't notice a type for call number.... Are we meant
>> to use bibo:locator
>
> I don't think so.
>
> Could foaf:phone fill the gap?

No, a call number is the library location identifier. See here for an example:

<http://www.worldcat.org/wcpa/oclc/60500684?page=frame&url=http%3A%2F%2Flibrary.ohio-state.edu%2Fsearch%2Fi041594872X&title=Ohio+State+University&linktype=opac&detail=OSU%3AOhio+State+University%3AAcademic>

I'm not exactly sure how call numbers work; whether they might be a
subproperty of bibo:locator or not. It might be more a frbr:item level
id.

Bruce

[Mark Diggory]

bibo:oclcnum a owl:DatatypeProperty ;
vs:term_status "stable" ;
rdfs:label "oclcnum"@en ;
rdfs:comment "OCLC Identifier"@en ;
rdfs:isDefinedBy <http://purl.org/ontology/bibo/> ;
rdfs:subPropertyOf bibo:identifier ;
rdfs:domain [ a owl:Class; owl:unionOf (bibo:Document
bibo:Collection) ] ;
rdfs:range rdfs:Literal .

[connie]

Based on the oclcnum example, can we expect a bibo:callnum?

[Bruce D'Arcus]

On Mon, Jun 9, 2008 at 10:49 AM, connie <cms...@gmail.com> wrote:
>
> Based on the oclcnum example, can we expect a bibo:callnum?

As my comments suggested, we need to first figure out exactly what a
call number is. For example if there are two hard-cover copies of the
same book, do they have the same number? Are the numbers the same in
different libraries?

If yes, then I see no problem adding bibo:callnum.

Bruce

[Mark Diggory]

I think the group needs to be very specific and careful how this
aligns with existing schemes.

There are a number of types of "call numbers" at OCLC:

http://www.oclc.org/bibformats/en/0xx/050-099.shtm

Dublin core Identifier has usage examples:

http://dublincore.org/documents/usageguide/elements.shtml

> 4.14. Identifier
>
> Label: Resource Identifier
>
> Element Description: An unambiguous reference to the resource
> within a given context. Recommended best practice is to identify
> the resource by means of a string or number conforming to a formal
> identification system. Examples of formal identification systems
> include the Uniform Resource Identifier (URI) (including the
> Uniform Resource Locator (URL), the Digital Object Identifier (DOI)
> and the International Standard Book Number (ISBN).
>
> Guidelines for content creation:
>
> This element can also be used for local identifiers (e.g. ID
> numbers or call numbers) assigned by the Creator of the resource to
> apply to a particular item. It should not be used for
> identification of the metadata record itself.
>
> Examples:
>
> Identifier="http://purl.oclc.org/metadata/dublin_core/& quot;
> Identifier="ISBN:0385424728"
> Identifier="H-A-X 5690B" [publisher number]

http://dublincore.org/documents/dc-citation-guidelines/

> 5.2 Identifiers
>
> Recommendation 7. Global identifiers should be encoded as URIs.
>
> There are various global identifiers relevant to bibliographic
> resources, for example ISSN for serials, ISBN for books, SICI
> (Serial Item and Contribution Identifier), Digital Object
> Identifier (DOI). They should be encoded in values of Dublin Core
> properties as value URIs. Table 1 lists some of these identifiers.
> Some of these identifiers use the new 'info' URI scheme [12]. Until
> the introduction of this scheme there was no global URI namespace
> for these identifiers in common use for bibliographic resources.
>
> Table 1. Identifiers for Bibliographic Resources.
> Identifier URI namespace Example
> ISSN urn:ISSN: urn:ISSN:0302-9743
> ISBN urn:ISBN: urn:ISBN:8884530431
> NBN (National Bibliographic Number) urn:NBN: urn:NBN:fi-fe19981001
> Digital Object Identifier info:doi/ info:doi/10.1045/july99-caplan
> SICI info:sici/ info:sici/07408188(200010)22:3%3C311:SEUB%
> 3E2.0.CO;2-X
> PubMed info:pmid/ info:pmid/9036860
> Open Archives Initiative info:oai/ info:oai/arXiv.org:hep-th/9901001

And DC has Encoding Schemes specific to some of these types.

http://dublincore.org/documents/dcmi-terms/#H4

-Mark