Skip to content
GitHub
Twitter

Organization DRAFT Profile

Version: 0.2-DRAFT-2019_07_19 (19 July 2019)

Bioschemas specification for describing a Organization in the life-science.


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
description Text
Schema:

A description of the item.


ONE
legalName Text
Schema:

The official name of the organization, e.g. the registered company name.


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
topic Text
URL
Bioschemas:

Scientific topics that describe the organization and its activities, ideally using an ontology term from EDAM:Topic.

MANY

EDAM:Topic

type Text
URL
Bioschemas:

The type of the organization should be selected from the Controlled Vocabulary column.

MANY

single-company corporation, multinational, not-for-profit, alliance, consortium, institute, department, working party, project.

Marginality: Recommended.
alternateName Text
Schema:

An alias for the item.


ONE
contactPoint ContactPoint
Schema:

A contact point for a person or organization. Supersedes contactPoints.


MANY
fundingModel Text
Bioschemas:

A description of how the organization is funded.

ONE
keywords Text
Schema:

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


ONE
location Place
PostalAddress
Text
Schema:

The location of for example where the event is happening, an organization is located, or where an action takes place.


ONE
logo ImageObject
URL
Schema:

An associated logo.


ONE
member Organization
Person
Schema:

A member of an Organization or a ProgramMembership. Organizations can be members of organizations; ProgramMembership is typically for individuals. Supersedes members, musicGroupMember. Inverse property: memberOf.


MANY
memberOf Organization
ProgramMembership
Schema:

An Organization (or ProgramMembership) to which this Person or Organization belongs. Inverse property: member.


MANY
membershipCategory Offer
Bioschemas:

Defines a membership category and associated fees (for projects and alliances etc.).

MANY
status Text
Bioschemas:

To record if the organization is still alive, and if it were are project or alliance, what the outcome was, or if it has closed down or merged, why and when. Note: There is a health-lifesci.status, but this is not related to the current status property

ONE

active, dormant, merged, closed

url URL
Schema:

URL of the item.


MANY
Marginality: Optional.
attachment URL
Bioschemas:

Any files or related websites which give more information about this organization, e.g., flyers, third party sites, …

MANY
budget PriceSpecification
Bioschemas:

The annual (or total - for a project) budget for the organization.

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.


Bioschemas:

The date when the organization information was last modified.

ONE
department Organization
Schema:

A relationship between an organization and a department of that organization, also described as an organization (allowing different urls, logos, opening hours). For example: a store with a pharmacy, or a bakery with a cafe.


MANY
dissolutionDate Date
Schema:

The date that this organization was dissolved.


ONE
founderMember Organization
Person
Bioschemas:

For an alliance or collaboration or project, the founding members. NOTE: schema/Organization has founder but this has a type of Person not Person and Organization

MANY
foundingDate Date
Schema:

The date that this organization was founded.


ONE
owns OwnershipInfo
Product
Schema:

Products owned by the organization or person.


MANY
parentOrganization Organization
Schema:

The larger organization that this organization is a subOrganization of, if any. Supersedes branchOf. Inverse property: subOrganization.


ONE
socialMedia URL
Bioschemas:

Link to social media websites like twitter or facebook.

MANY
subOrganization Organization
Schema:

A relationship between two organizations where the first includes the second, e.g., as a subsidiary. See also: the more specific ‘department’ property. Inverse property: parentOrganization.


MANY