Skip to content

JSON-LD PropertyValue should represent ROR value as a string not a URL #6520

@rdmpage

Description

@rdmpage

Following on from #6519 @dshorthouse gave the example of @TomDemeranville ORCID record. The values for ROR are given as URLs (e.g., https://ror.org/04fa4r544) whereas surely they would be better as strings without the URL (i.e. 04fa4r544)? This would make them consistent with the RINGGOLD identifier below, and also how ORCID handles DOIs.

AFAIK the whole point of using PropertyValue for an identifier is that we can present just the identifier part (the "slug", which tends to be persistent) and ignore the resolution component (which tends to be changeable).

        {
            "@type": "Organization",
            "name": "ORCID",
            "alternateName": "Product",
            "identifier": {
                "@type": "PropertyValue",
                "propertyID": "ROR",
                "value": "https://ror.org/04fa4r544"
            }
        },
        {
            "@type": "Organization",
            "name": "ORCID",
            "alternateName": "Technology",
            "identifier": {
                "@type": "PropertyValue",
                "propertyID": "ROR",
                "value": "https://ror.org/04fa4r544"
            }
        },
        {
            "@type": "Organization",
            "name": "Eduserv Athens",
            "alternateName": "Athens",
            "identifier": {
                "@type": "PropertyValue",
                "propertyID": "RINGGOLD",
                "value": "226102"
            }
        },

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions