W3C home > Mailing lists > Public > public-schemaorg@w3.org > June 2020

Re: scholarlyArticle no DOI

From: Richard Wallis <richard.wallis@dataliberate.com>
Date: Thu, 11 Jun 2020 17:32:04 +0100
Message-ID: <CAD47Kz6BJgqQyrrtkv72YsJfYCN-DgoV0BwhJ+ojNHC4GrPsQw@mail.gmail.com>
To: Bill Kasdorf <kasdorf.bill@gmail.com>
Cc: Hugh Paterson III <sil.linguist@gmail.com>, public-schemaorg@w3c.org
Thanks for the clarification.

Is that differentiation just a matter of specifying who is responsible for
issuing the DOI, or is it relevant to the mechanisms needed to lookup
information?

Potentially the value provided could be the DOI's associated URI.

~Richard.

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw



On Thu, 11 Jun 2020 at 17:00, Bill Kasdorf <kasdorf.bill@gmail.com> wrote:

> Technically, they're both just DOIs, as is EIDR (for the entertainment
> industry). But I like to specify "Crossref DOI" when I'm talking about a
> DOI for an article, for example, to disambiguate. Many people in scholarly
> publishing just call them DOIs and aren't even aware that there are
> different kinds of DOIs. The identifiers themselves are virtually the same;
> it's the metadata and systems they're associated with that differ. Not sure
> if that answers your question. . . .
>
> On Thu, Jun 11, 2020 at 11:53 AM Richard Wallis <
> richard.wallis@dataliberate.com> wrote:
>
>> Are there different acronym conventions to identify the differing types
>> (that could be used for a propertyID value) or are they both 'doi' ?
>>
>> ~Richard
>>
>> Richard Wallis
>> Founder, Data Liberate
>> http://dataliberate.com
>> Linkedin: http://www.linkedin.com/in/richardwallis
>> Twitter: @rjw
>>
>>
>>
>> On Thu, 11 Jun 2020 at 16:47, Bill Kasdorf <kasdorf.bill@gmail.com>
>> wrote:
>>
>>> And just to be clear, articles are identified with a Crossref DOI and
>>> data sets are identified with a DataCite DOI. Two separate but related
>>> systems.
>>>
>>> On Thu, Jun 11, 2020 at 11:11 AM Richard Wallis <
>>> richard.wallis@dataliberate.com> wrote:
>>>
>>>> As with all Schema.org types ScholarlyArticle
>>>> <https://schema.org/ScholarlyArticle> can have an associated identifier
>>>> <https://schema.org/identifier> property defined.
>>>>
>>>> For example:
>>>>
>>>> {
>>>>    "@context": "http://schema.org",
>>>>    "@type": "Article",
>>>>    "name": "DOI Handbook",
>>>>    "identifier": {
>>>>        "@type": "PropertyValue",
>>>>        "propertyID": "doi",
>>>>        "value": "10.1000/182"
>>>>    }
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>> Richard Wallis
>>>> Founder, Data Liberate
>>>> http://dataliberate.com
>>>> Linkedin: http://www.linkedin.com/in/richardwallis
>>>> Twitter: @rjw
>>>>
>>>>
>>>>
>>>> On Thu, 11 Jun 2020 at 15:36, Hugh Paterson III <sil.linguist@gmail.com>
>>>> wrote:
>>>>
>>>>> Greetings,
>>>>>
>>>>> I'm wondering why there is no DOI "attribute" listed under
>>>>> scholarlyArticle. DOI resolvers are fairly important and mainstream, with
>>>>> the Datacite API one can generally get the publication metadata of most
>>>>> currently published articles.
>>>>>
>>>>> It seems that editEIDR  solves the same kind of identification
>>>>> function, so it seems that someone has suggested that this kind of
>>>>> functionality is useful (which I agree it is). I'm wondering if there is
>>>>> any discussion for adding DOI or abstracting to an "attribute" which would
>>>>> allow for the use of Handles, URN's ARK's, DOI's, LSIDs etc.
>>>>>
>>>>> Otherwise, how are people choosing to encode DOI's?
>>>>>
>>>>> all the best,
>>>>> - Hugh
>>>>>
>>>>>
>>>>> for specifics on terms:
>>>>> https://en.wikipedia.org/wiki/Digital_object_identifier
>>>>> https://en.wikipedia.org/wiki/Archival_Resource_Key
>>>>> https://en.wikipedia.org/wiki/LSID
>>>>>
>>>>>
>>>>>
>>>
>>> --
>>> *Bill Kasdorf*
>>> *Principal, Kasdorf & Associates, LLC*
>>> *Founding Partner, Publishing Technology Partners
>>> <https://pubtechpartners.com/>*
>>> *W3C Global Publishing Evangelist*
>>> kasdorf.bill@gmail.com
>>> +1 734-904-6252
>>>
>>> ISNI: http://isni.org/isni/0000000116490786
>>> ORCiD: https://orcid.org/0000-0001-7002-4786
>>> <https://orcid.org/0000-0001-7002-4786?lang=en>
>>>
>>>
>
> --
> *Bill Kasdorf*
> *Principal, Kasdorf & Associates, LLC*
> *Founding Partner, Publishing Technology Partners
> <https://pubtechpartners.com/>*
> *W3C Global Publishing Evangelist*
> kasdorf.bill@gmail.com
> +1 734-904-6252
>
> ISNI: http://isni.org/isni/0000000116490786
> ORCiD: https://orcid.org/0000-0001-7002-4786
> <https://orcid.org/0000-0001-7002-4786?lang=en>
>
>
Received on Thursday, 11 June 2020 16:32:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 11 June 2020 16:32:30 UTC