English
ContactPoint draft value type
How to get in touch with a facility or an organisation, as the value of a contactPoint Property: telephone, extension, fax, e-mail, web form, other channels and the postal code. The fields follow the contact columns of the 自治体標準オープンデータセット and GIF's core data model 連絡先 (contact point); schema.org ContactPoint terms are used where the meaning matches. Every field is optional.
| Kind | value type: used inside an attribute, not as an entity of its own |
| IRI | https://datamodels.jp/ns/common/ContactPoint |
| @context | https://datamodels.jp/context/common/v1.jsonld |
| JSON Schema | /schema/common/ContactPoint/v1.json |
| Licence | CC0 1.0: the files (@context, JSON Schema, examples) can be used without conditions |
These @context and JSON Schema URLs always point to the latest compatible version.
For URLs that never change, see Versions. More in URLs and versions.
Types and relationships
used as a value typeother subjectN more links: continued on that type's page
Fields
| Field | Description | Value |
|---|---|---|
telephone | Telephone number as written by the publisher, for example 03-3264-2111. Several numbers are separated by ' / 'https://schema.org/telephone | string |
telephoneExtension | Extension of the telephone numberhttps://datamodels.jp/ns/common/telephoneExtension | string |
faxNumber | Fax numberhttps://schema.org/faxNumber | string |
email | E-mail addresshttps://schema.org/email | string |
url | Web page or web form for getting in touchhttps://schema.org/url | string |
otherChannels | Other ways to get in touch, such as social media accounts, and remarks on the contact, as free texthttps://datamodels.jp/ns/common/otherChannels | string |
postalCode | Postal code of the contact, 7 digits with or without hyphen. It can differ from the postal code of the facility's addresshttps://schema.org/postalCode | string, pattern ^\d{3}-?\d{4}$ |
Using this model
Other models use this value type as the value of an attribute. How: Rules for models.
Example
The examples are a fictional scenario (heavy rain in Chiyoda, Tokyo). Place names and codes are real; the events, people and teams are invented. See writing examples.
json
{
"telephone": "03-3264-2111",
"otherChannels": "千代田区コールセンター 03-3264-3910(年中無休、8:00〜21:00)",
"postalCode": "102-8688"
}Files: example.json
Something missing or wrong?
Open an issue, or propose new attributes or models with the proposal form. How it works: Contributing. The source files (notes, mapping tables) are on GitHub.
Referenced standards
The standards this model corresponds to, field by field. Open one to see its table.
Digital Agency GIF core data model "Contact point"
GIF's contact point has a name, a purpose, telephone numbers (several, extensions included), e-mail addresses (several), a URL, social media (several), an address and a remark. GIF's core data model 施設 (facility) holds it as contactPointInformation.
| This model | Maps to | Note |
|---|---|---|
telephone | 連絡先電話番号 (contactPointPhoneNumber) | |
telephoneExtension | 連絡先電話番号 (contactPointPhoneNumber) | GIF counts extensions as telephone numbers |
faxNumber | no counterpart | not in GIF's contact point; the datasets' FAX番号 (contactPointFaxNumber) |
email | 連絡先メールアドレス (contactPointEmailAddress) | |
url | 連絡先URL (contactPointUrl) | |
otherChannels | 連絡先SNS (contactPointSocialMedia), 連絡先備考 (contactPointRemark) | GIF keeps social media ('service: ID') and remarks apart; here they are one text |
postalCode | 連絡先住所 (contactPointAddress) | the postal code of GIF's address (see JapaneseAddress's gif-address table) |
Mapping file (YAML) for converting data from this standard: gif-contact-point.yaml (see Mapping files)
Licence of this standard: CC BY 4.0 (schema), CC0 1.0 (repository)
Municipal standard open dataset, data item definition sheet A (2026-08-01), contact columns (Digital Agency)
Of definition sheet A, datasets 01 public facilities, 05 childcare facilities, 08 AEDs, 09 care service providers and 10 medical institutions have the contact columns under these names (FAX番号 only 05, 09 and 10). Dataset 11 tourist facilities names two of them differently (連絡先電話番号, 連絡先内線番号); 13 public toilets has no contact. Columns are given as the Japanese name (English item name).
| This model | Maps to | Note |
|---|---|---|
telephone | 電話番号 (contactPointPhoneNumber) | GIF's telephone notation; several numbers separated by ' / ' |
telephoneExtension | 内線番号 (contactPointExtension) | |
faxNumber | FAX番号 (contactPointFaxNumber) | only datasets 05, 09 and 10 |
email | 連絡先メールアドレス (contactPointEmailAddress) | |
url | 連絡先FormURL (contactPointFormUrl) | |
otherChannels | 連絡先備考(その他、SNSなど) (contactPointRemarks) | |
postalCode | 郵便番号 (contactPointPostalCode) | by definition the contact's postal code. The dataset's example has no hyphen (1234567); both forms are accepted |
Mapping file (YAML) for converting data from this standard: jichitai-opendata-contact.yaml (see Mapping files)
Licence of this standard: Public Data License (Version 1.0) (PDL1.0), compatible with CC BY 4.0
Notes
- A value type, not an entity type. Use it as the value of a
contactPointProperty (IRI https://schema.org/contactPoint) and reference the schema with $ref from an entity schema. - Built on the contact columns of the Digital Agency's 自治体標準オープンデータセット, data item definition sheet A (2026-08-01, checked 2026-10-11): 電話番号, 内線番号, FAX番号, 連絡先メールアドレス, 連絡先FormURL, 連絡先備考(その他、SNSなど) and 郵便番号. Datasets 01 public facilities, 05 childcare facilities, 08 AEDs, 09 care service providers, 10 medical institutions and 11 tourist facilities have them (FAX番号 only 05, 09 and 10). Dataset 11 names two of them 連絡先電話番号 and 連絡先内線番号, and adds 連絡先名称. The correspondence is in mapping/jichitai-opendata-contact.yaml.
- It also corresponds to GIF's core data model 連絡先 (438_コアデータモデル_DMD.xlsx, checked 2026-10-11). GIF has a name, a purpose and an address for the contact, and counts fax and extension numbers as telephone numbers. The correspondence is in mapping/gif-contact-point.yaml.
- Upstream considered (2026-10-11): schema.org ContactPoint terms are reused where the meaning matches (telephone, faxNumber, email, url, postalCode). The type itself is minted as a catalog value type, like JapaneseAddress, because a catalog value type needs its own schema and page; Smart Data Models PointOfInterest's contactPoint has the same schema.org shape. schema.org has no term for an extension or for other channels such as social media, so these are minted in the common namespace (telephoneExtension, otherChannels).
- Left out: the name of the contact (連絡先名称 in dataset 11 and in GIF), and GIF's purpose and address of the contact. The datasets of the first models (AEDLocation, PublicToilet, MedicalInstitution) do not have them; they can be added when needed.