Skip to main content

Contact Point

A contact point, usually within an organization.

This is an implementation of schema.org ContactPoint. It extends schema.org ContactPoint by, adding a content property which must be an array of BlockContent, as well as the properties added by CreativeWork which it extends. ContactPoint is analogous, and structurally similar to, the JATS XML <corresp> element and the HTML5 <address> element.

Properties​

Name@idTypeDescriptionInherited from
alternateNamesschema:alternateNameArray of stringAlternate names (aliases) for the item.Thing
availableLanguagesschema:availableLanguageArray of stringLanguages (human not programming) in which it is possible to communicate with the organization/department etc.ContactPoint
descriptionschema:descriptionArray of BlockContent or Array of InlineContent or stringA description of the item. See note 1.Thing
emailsschema:emailArray of Format 'email'Email address for correspondence.ContactPoint
idschema:idstringThe identifier for this item.Entity
identifiersschema:identifierArray of (PropertyValue or string)Any kind of identifier for any kind of Thing. See note 2.Thing
imagesschema:imageArray of (ImageObject or Format 'uri')Images of the item.Thing
metastencila:metaobjectMetadata associated with this item.Entity
nameschema:namestringThe name of the item.Thing
telephoneNumbersschema:telephoneArray of stringTelephone numbers for the contact point.ContactPoint
urlschema:urlFormat 'uri'The URL of the item.Thing

Notes​

  1. description : Allows for the description to be an array of nodes (e.g. an array of inline content, or a couple of paragraphs), or a string. The minItems restriction avoids a string being coerced into an array with a single string item.
  2. identifiers : Some identifiers have specific properties e.g the issn property for the Periodical type. These should be used in preference to this property which is intended for identifiers that do not yet have a specific property. Identifiers can be represented as strings, but using a PropertyValue will usually be better because it allows for propertyID (i.e. the type of identifier).

Examples​

{
"type": "ContactPoint",
"availableLanguages": [
"English",
"Māori"
],
"emails": [
"welcome@example.org"
],
"telephone": "00641234567"
}

Available as​

Source​

This documentation was generated from ContactPoint.schema.yaml.