You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: v1.1/schema.md
+97-12
Original file line number
Diff line number
Diff line change
@@ -56,13 +56,16 @@ Links to downloadable examples of metadata files developed in this and other for
56
56
57
57
Catalog Fields
58
58
-------------------------------------------------
59
-
These fields describe the entire Public Data Listing catalog file. Optionally, publishers may also use the `describedBy` field to reference the default [JSON Schema](http://json-schema.org/) file used to define the schema (http://project-open-data.cio.gov/v1.1/schema/catalog.json) or they may refer to their own JSON Schema file where they have extended the schema. See the [Catalog section](#Catalog) under *Further Metadata Field Guidance* for more details.
59
+
These fields describe the entire Public Data Listing catalog file. Publishers can also use the `describedBy` field to reference the default [JSON Schema](http://json-schema.org/) file used to define the schema (*https://project-open-data.cio.gov/v1.1/schema/catalog.json*) or they may refer to their own JSON Schema file if they have extended the schema with additional schema definitions. Similarly, `@context` can be used to reference the default [JSON-LD](http://www.w3.org/TR/json-ld) Context used to define the schema (*https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld*) or publishers can refer to their own if they have extended the schema with additional linked data vocabularies. See the [Catalog section](#Catalog) under *Further Metadata Field Guidance* for more details.
[conformsTo](#conformsTo) | Schema Version | A URI that identifies the version of the Project Open Data schema being used. | Always
65
-
[describedBy](#describedBy) | Data Dictionary | URL for the [JSON Schema](http://json-schema.org/) file that defines the schema used | No
64
+
[@context](#context) | Metadata Context | URL or JSON object for the [JSON-LD Context](http://www.w3.org/TR/json-ld/#the-context) that defines the schema used | No
65
+
[@id](#id) | Metadata Catalog ID | IRI for the [JSON-LD Node Identifier](http://www.w3.org/TR/json-ld/#node-identifiers) of the Catalog. This should be the URL of the data.json file itself | No
66
+
[@type](#type) | Metadata Type | IRI for the [JSON-LD data type](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `dcat:Catalog` for the Catalog | No
67
+
[conformsTo](#conformsTo) | Schema Version | URI that identifies the version of the Project Open Data schema being used. | Always
68
+
[describedBy](#describedBy) | Data Dictionary | URL for the [JSON Schema](http://json-schema.org/) file that defines the schema used | No
66
69
[dataset](#dataset) | Dataset | A container for the array of Dataset objects. See [Dataset Fields](#Dataset) below for details. | Always
67
70
68
71
@@ -73,6 +76,7 @@ See the *[Further Metadata Field Guidance](#further-metadata-field-guidance)* se
[@type](#dataset-type) | Metadata Type | IRI for the [JSON-LD data type](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `dcat:Dataset` for each Dataset | No
76
80
[title](#title) | Title | Human-readable name of the asset. Should be in plain English and include sufficient detail to facilitate search and discovery. | Always
77
81
[description](#description) | Description | Human-readable description (e.g., an abstract) with sufficient detail to enable a user to quickly understand whether the asset is of interest. | Always
78
82
[keyword](#keyword) | Tags | Tags (or keywords) help users discover your dataset; please include terms that would be used by technical and non-technical users. | Always
@@ -110,6 +114,7 @@ Within a dataset, **distribution** is used to aggregate the metadata specific to
[@type](#distribution-type) | Metadata Type | IRI for the [JSON-LD data type](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `dcat:Distribution` for each Distribution | No
113
118
[accessURL](#distribution-accessURL) | Access URL | URL providing indirect access to a dataset, for example via API or a graphical interface | If-Applicable
114
119
[conformsTo](#distribution-conformsTo) | Data Standard | URI used to identify a standardized specification the distribution conforms to | No
115
120
[describedBy](#distribution-describedBy) | Data Dictionary | URL to the data dictionary for the distribution found at the `downloadURL`. Note that documentation other than a data dictionary can be referenced using Related Documents as shown in the expanded fields. | No
@@ -123,7 +128,7 @@ Field | Label | Defini
123
128
124
129
Extending the Schema
125
130
------------------------------------------
126
-
"Extensional" and/or domain specific metadata can easily be added using other vocabularies even if it is not a term (entity/property) that will get indexed by the major search engines - it could still be indexed by other custom search engines and by Data.gov. Agencies are encouraged to extend their metadata descriptions using elements from the "Expanded Fields" list shown below, or from any well-known vocabulary (including Dublin Core, Schema.org, FGDC, ISO 19115, and NIEM) as long as they are properly assigned.
131
+
"Extensional" and/or domain specific metadata can easily be added using other vocabularies even if it is not a term (entity/property) that will get indexed by the major search engines - it could still be indexed by other custom search engines and by Data.gov. Publishers are encouraged to extend their metadata descriptions using elements from the "Expanded Fields" list shown below, or from any well-known vocabulary (including Dublin Core, Schema.org, FGDC, ISO 19115, and NIEM) as long as they are properly assigned. It's also recommended that these extensions be defined through the `describedBy` and `@context` fields at the top of the [Catalog metadata](#catalog-fields).
127
132
128
133
129
134
Further Metadata Field Guidance
@@ -140,21 +145,27 @@ Additional details for each field are provided here broken down into sections fo
**Usage Notes** | The URL or JSON object for the [JSON-LD Context](http://www.w3.org/TR/json-ld/#the-context) that defines the schema used. The URL for version 1.1 of the schema is `https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld`
**Usage Notes** | A unique identifier for the Catalog as defined by [JSON-LD Node Identifiers](http://www.w3.org/TR/json-ld/#node-identifiers). This should be the URL of the data.json file itself
**Usage Notes** | The metadata type as defined by [JSON-LD data types](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `dcat:Catalog` for the Catalog
**Usage Notes** | The metadata type as defined by [JSON-LD data types](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `dcat:Dataset` for the Dataset
**Usage Notes** | The metadata type as defined by [JSON-LD data types](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `vcard:Contact` for contactPoint
**Usage Notes** | The metadata type as defined by [JSON-LD data types](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `dcat:Distribution` for each distribution
**Usage Notes** | The metadata type as defined by [JSON-LD data types](http://www.w3.org/TR/json-ld/#specifying-the-type). This should be `org:Organization` for each publisher
0 commit comments