Type Pattern

Signposting the Scholarly Web

To convey the type of a scholarly object (e.g. article, dataset, software) to machines, use the type link relation type to link from the object's landing page to a URI for the object's type. A URI for an object's type conveyed on links with the type relation type should be an HTTP URI chosen from namespaces that are widely supported by the community, such as schema.org or the COAR Controlled Vocabulary for Types.

In case of a traditional landing page that describes the scholarly object, provide two type links, one to convey that a landing page is concerned (i.e. https://schema.org/AboutPage) and one to convey the actual type of the object. In case of a landing page that also is a content resource (e.g. an HTML article to which the object's persistent identifier redirects), provide one type link to convey the actual type of the object.

The below examples illustrate the use of type links in the HTTP Link header of HTML landing pages. But type links can also be provided in that page's HTML link element and/or in a Link Set that is discoverable from the landing page.

Type Scenarios

  • Landing Page ➞ Type URI

    Express the type of the scholarly object and flag the landing page as describing the scholarly object.
    Example 1 »   Example 2 »

  • Landing Page (which is also a Content Resource) ➞ Type URI

    Express the type of the scholarly object.
    Example »