Skip to content
GitHub

DefinedTermSet DRAFT Profile

Version: 0.1-DRAFT (22 June 2026)


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
url URL
 Schema:

URL of the item.


 ONE
Marginality: Recommended.
alternateName Text
 Schema:

An alias for the item.


 MANY
creator Organization
Person
 Schema:

The creator/author of this CreativeWork. This is the same as the Author property for CreativeWork.


 MANY
license CreativeWork
URL
 Schema:

A license document that applies to this content, typically indicated by URL.


 ONE
name Text
 Schema:

The name of the item.


 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.


 ONE
version Text
number
 Schema:

The version of the CreativeWork embodied by a specified resource.


 ONE
Marginality: Optional.
citation CreativeWork
Text
 Schema:

A citation or reference to another creative work, such as another publication, web page, scholarly article, etc.


 MANY
conditionsOfAccess Text
 Schema:

Conditions that affect the availability of, or method(s) of access to, an item. Typically used for real world items such as an [[ArchiveComponent]] held by an [[ArchiveOrganization]]. This property is not suitable for use as a general Web access control mechanism. It is expressed only in natural language.\n\nFor example “Available by appointment from the Reading Room” or “Accessible only from logged-in accounts “.


 ONE
dateCreated Date
DateTime
 Schema:

The date on which the CreativeWork was created or the item was added to a DataFeed.


 ONE
dateModified Date
DateTime
 Schema:

The date on which the CreativeWork was most recently modified or when the item’s entry was modified within a DataFeed.


 ONE
datePublished Date
DateTime
 Schema:

Date of first broadcast/publication.


 ONE
description Text
 Schema:

A description of the item.


 ONE
hasDefinedTerm DefinedTerm
 Schema:

A Defined Term contained in this term set.


 MANY
isAccessibleForFree Boolean
 Schema:

A flag to signal that the item, event, or place is accessible for free.


 ONE
keywords DefinedTerm
Text
URL
 Schema:

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


 MANY
maintainer Organization
Person
 Schema:

A maintainer of a [[Dataset]], software package ([[SoftwareApplication]]), or other [[Project]]. A maintainer is a [[Person]] or [[Organization]] that manages contributions to, and/or publication of, some (typically complex) artifact. It is common for distributions of software and data to be based on “upstream” sources. When [[maintainer]] is applied to a specific version of something e.g. a particular version or packaging of a [[Dataset]], it is always possible that the upstream source has a different maintainer. The [[isBasedOn]] property can be used to indicate such relationships between datasets to make the different maintenance roles clear. Similarly in the case of software, a package may have dedicated maintainers working on integration into software distributions such as Ubuntu, as well as upstream maintainers of the underlying work.


 MANY