Skip to content
GitHub
Twitter

PublicationVolume DRAFT Profile

Version: 0.1-DRAFT-2019_02_15 (08 February 2019)

Bioschemas profile, based on Biotea model, describing a PublicationVolume in Life Sciences.


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


Key to specification table

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
@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
@id IRI Used to distinguish the resource being described in JSON-LD. For other serialisations use the appropriate approach. ONE
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
volumeNumber Integer
Text
 Schema:

Identifies the volume of publication or multi-part work; for example, “iii” or “2”.


 ONE
Marginality: Recommended.
hasPart PublicationIssue
ScholarlyArticle
 Schema:

Indicates an item or CreativeWork that is part of this item, or CreativeWork (in some sense). Inverse property: isPartOf.


Bioschemas:

A PublicationVolume has part PublicationIssue (a.k.a. supplements) or ScholaryArticle. We recommend to include at least the highest ‘hasPart’ level, i.e., PublicationIssue. It is also possible to use ‘hasPart’ to link as well directly to ScholarlyArticle, making it easier to find articles in this volume.

 MANY
identifier PropertyValue
Text
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:

Volumes in a journal are commonly identified by a number thus not unique nor global. We recommend to use the URL as identifier whenever possible.

 ONE
isPartOf Journal
 Schema:

Indicates an item or CreativeWork that this item, or CreativeWork (in some sense), is part of. Inverse property: hasPart.


Bioschemas:

A PublicationVolume is part of a Journal.

 ONE
pageEnd Integer
Text
 Schema:

The page on which the work ends; for example “138” or “xvi”.


 ONE
pageStart Integer
Text
 Schema:

The page on which the work starts; for example “135” or “xiii”.


 ONE
url URL
 Schema:

URL of the item.


Bioschemas:

Oficial URL.

 ONE
Marginality: Optional.
about Thing
 Schema:

The subject matter of the content. Inverse property: subjectOf.


Bioschemas:

Describes what this volume is about.

 ONE
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
keywords Text
 Schema:

Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.


 ONE
pagination Text
 Schema:

Any description of pages that is not separated into pageStart and pageEnd; for example, “1-6, 9, 55” or “10-12, 46-49”.


 MANY
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.


Bioschemas:

Any other URL linking to this volume.

 MANY