Journal DRAFT Profile

Version: 0.1-DRAFT-2019_05_09 (09 May 2019)

Bioschemas profile, based on Biotea model, describing a Journal in Life Sciences. For markup purposes, we are keeping the schema:Periodical type so it will be easily recognized and parsed by search engines.

If you spot any errors or omissions with this type, please file an issue in our GitHub.

Schema.org hierarchy

This Profile fits into the schema.org hierarchy as follows:

Thing > CreativeWork > CreativeWorkSeries

Description

A Journal is a collection of publication issues, publication volumes or scholarly articles, or possibly, although no commonly, any mix from those mentioned.

Latest profiles

Latest release: none

Latest draft: 0.3-DRAFT

Previous profiles

Previous version: 0.1-DRAFT-2019_03_15

Contributors

The following people have been involved in the creation of this specification document. They are all members of the Scholarly Publications group.

Group Leader(s)

Alexander Garcia

Leyla Jael Castro

Other team members

Olga Ximena Giraldo

Dietrich Rebholz-Schuhmann

Group	Use Cases	Cross Walk	Task & Issues	Examples	Live Deploys
Scholarly Publications

You can read the release version of this specification here.

Key to specification table

Green properties/types are proposed by Bioschemas, or indicate proposed changes by Bioschemas to Schema.org
Red properties/types exist in the core of Schema.org
Blue properties/types exist in the pending area of Schema.org
Black properties/types are reused from external vocabularies/ontologies

CD = Cardinality

Property	Expected Type	Description	CD	Controlled Vocabulary	Example
Marginality: Minimum.
@context	URL	Used to provide the context (namespaces) for the JSON-LD file. Not needed in other serialisations.	ONE		Property ≪@context≫ example `{ "@context": "https://schema.org/" }`
@type	Text	Schema.org/Bioschemas class for the resource declared using JSON-LD syntax. For other serialisations please use the appropriate mechanism. While it is permissible to provide multiple types, it is preferred to use a single type.	MANY	Schema.org, Bioschemas	Property ≪@type≫ example `{ "@type": "Periodical" }`
@id	IRI	Used to distinguish the resource being described in JSON-LD. For other serialisations use the appropriate approach.	ONE		Property ≪@id≫ example `{ "@id": "http://example.com/entity/A12345" }`
dct:conformsTo	IRI	Used to state the Bioschemas profile that the markup relates to. The versioned URL of the profile must be used. Note that we use a CURIE in the table here but the full URL for Dublin Core terms must be used in the markup (http://purl.org/dc/terms/conformsTo), see example.	ONE	Bioschemas profile versioned URL	Property ≪dct:conformsTo≫ example `{ "http://purl.org/dc/terms/conformsTo": { "@id": "https://bioschemas.org/profiles/Journal/0.1-DRAFT-2019_09_05", "@type": "CreativeWork" } }`
identifier	URL	Schema: The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details. Bioschemas: We recommend to use a FAIR identifier.	ONE
issn	Text	Schema: The International Standard Serial Number (ISSN) that identifies this serial publication. You can repeat this property to identify different formats of, or the linking ISSN (ISSN-L) for, this serial publication. Bioschemas: We recommend to use here the form namespace:id. For instance, issn:2041-1480.	ONE
name	Text	Schema: The name of the item. Bioschemas: Title/name of the journal.	ONE
Marginality: Recommended.
hasPart	PublicationIssue PublicationVolume ScholarlyArticle	Schema: Indicates an item or CreativeWork that is part of this item, or CreativeWork (in some sense). Inverse property: isPartOf. Bioschemas: A Journal has part a PublicationVolume or PublicationIssue or ScholaryArticle. We recommend to at least include the highest level ‘hasPart’, e.g., PublicationVolume. It is also possible, i.e., optional, to ‘hasPart’ to link as well directly to PublicationIssue and ScholarlyArticle, making it easier to find articles in this journal.	MANY
keywords	Text	Schema: Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.	ONE
license	CreativeWork URL	Schema: A license document that applies to this content, typically indicated by URL.	ONE
publisher	Organization Person	Schema: The publisher of the creative work.	MANY
url	URL	Schema: URL of the item.	ONE
Marginality: Optional.
about	Thing	Schema: The subject matter of the content. Inverse property: subjectOf. Bioschemas: Describes what this Journal is about.	MANY
alternateName	Text	Schema: An alias for the item.	MANY
editor	Person	Schema: Specifies the Person who edited the CreativeWork.	MANY
inLanguage	Language Text	Schema: The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage. Supersedes language.	MANY
isAccessibleForFree	Boolean	Schema: A flag to signal that the item, event, or place is accessible for free. Supersedes free.	ONE
publishingPrinciples	CreativeWork URL	Schema: The publishingPrinciples property indicates (typically via URL) a document describing the editorial principles of an Organization (or individual e.g. a Person writing a blog) that relate to their activities as a publisher, e.g. ethics or diversity policies. When applied to a CreativeWork (e.g. NewsArticle) the principles are those of the party primarily responsible for the creation of the CreativeWork. While such policies are most typically expressed in natural language, sometimes related information (e.g. indicating a funder) can be expressed using schema.org terminology.	ONE
sameAs	URL	Schema: URL of a reference Web page that unambiguously indicates the item’s identity. E.g. the URL of the item’s Wikipedia page, Wikidata entry, or official website.	MANY