- From: Corey A Harper <corey.harper@nyu.edu>
- Date: Mon, 2 Dec 2013 11:11:07 -0500
- To: Owen Stephens <owen@ostephens.com>
- Cc: Dan Scott <denials@gmail.com>, François-Xavier Pelegrin <francois-xavier.pelegrin@issn.org>, "public-schemabibex@w3.org" <public-schemabibex@w3.org>
- Message-ID: <CAE4UJ7UpG4jT+mi0vEgJUHzn6yqgSKgH0NCL1yQuvsnx51_JHw@mail.gmail.com>
First off -- thank you to Dan & Owen for pointing me to the ISSN-L download page. I was unaware this was available, and have a need for it. The use case that I see for the ISSN-L is as data for deduplication algorithms. I find it helpful to know that I have an ISSN (or other ID) designed to link together multiple manifestations, which is the one argument I see in favor of a separate ISSN-L property. It would also work to just poll all ISSN's when trying to identify a match between two (or more) records, but I wonder if there's value in having a home for "linking" type identifiers. Another example that comes to mind is OCLCs GLIMIR ids, which seem to have something in common with ISSN-L's. -Corey On Fri, Nov 29, 2013 at 11:56 AM, Owen Stephens <owen@ostephens.com> wrote: > > On 29 Nov 2013, at 15:12, Dan Scott <denials@gmail.com> wrote: > > Thanks for your interest in this discussion! I have edited the description > of the proposed Periodical "issn" property at > http://www.w3.org/community/schemabibex/wiki/Periodical#Thing_.3E_CreativeWork_.3E_Collection_.3E_Periodicalto reflect the repeatability of the property if one wishes to reflect > different editions, with an example of format as the most likely reason for > adding multiple "issn" properties.. > > > Sounds good to me > > > If the ISSN-L is currently rarely displayed, then perhaps we should simply > be silent about it in the current Periodical proposal rather than minting a > separate "issn-l" property at this time. That said, I don't think there > would be significant harm caused if someone did end up using the "issn" > property to identify an ISSN-L, given that it would be likely to be one of > several "issn" properties in that case. > > > Not just 'likely' - but should always be one of the existing ISSN > properties. > Sounds reasonable to not worry about having a property for it at the moment > > Owen > > Owen Stephens > Owen Stephens Consulting > Web: http://www.ostephens.com > Email: owen@ostephens.com > Telephone: 0121 288 6936 > > > -- Corey A Harper Metadata Services Librarian New York University Libraries 20 Cooper Square, 3rd Floor New York, NY 10003-7112 212.998.2479 corey.harper@nyu.edu
Received on Monday, 2 December 2013 16:11:46 UTC