From cf66175ded95d20d49ee4c2b944e7c84c0c71736 Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Wed, 29 Jan 2014 14:59:59 -0500 Subject: [PATCH 1/6] clarified the accepted values for temporal --- schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema.md b/schema.md index 6377dfcd..8b047f49 100644 --- a/schema.md +++ b/schema.md @@ -336,7 +336,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) ----- | ----- **Cardinality** | (0,1) **Required** | Yes, if applicable -**Accepted Values** | See Usage Notes +**Accepted Values** | ISO 8601 Date **Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. **Example** | `{"temporal":"2000-01-15T00:45:00Z/2010-01-15T00:06:00Z"}` From 57bc2d9fd35acb30b0a09a5b4bcc387788695eeb Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Wed, 29 Jan 2014 15:01:00 -0500 Subject: [PATCH 2/6] made the iso 8601 links consistent --- schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema.md b/schema.md index 8b047f49..4b4dd153 100644 --- a/schema.md +++ b/schema.md @@ -337,7 +337,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (0,1) **Required** | Yes, if applicable **Accepted Values** | ISO 8601 Date -**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. +**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://www.w3.org/TR/NOTE-datetime) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. **Example** | `{"temporal":"2000-01-15T00:45:00Z/2010-01-15T00:06:00Z"}` {: .table .table-striped} From 9cbd3ee23a7a2f919e6a8e4592aa3feff3957725 Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Wed, 29 Jan 2014 15:04:39 -0500 Subject: [PATCH 3/6] changed the 8601 hyperlinks to the wikipedia entry It's more useful, esp. given the advice around durations and such --- schema.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/schema.md b/schema.md index 4b4dd153..1a1a9189 100644 --- a/schema.md +++ b/schema.md @@ -229,7 +229,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (0,1) **Required** | No **Accepted Values** | ISO 8601 Date -**Usage Notes** | Dates should be [ISO 8601](http://www.w3.org/TR/NOTE-datetime) of least resolution. In other words, as much of YYYY-MM-DDThh:mm:ss.sTZD as is relevant to this dataset. +**Usage Notes** | Dates should be [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) of least resolution. In other words, as much of YYYY-MM-DDThh:mm:ss.sTZD as is relevant to this dataset. **Example** | `{"issued":"2001-01-15"}` {: .table .table-striped} @@ -283,7 +283,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (1,1) **Required** | Yes, always **Accepted Values** | ISO 8601 Date -**Usage Notes** | Dates should be [ISO 8601](http://www.w3.org/TR/NOTE-datetime) of least resolution. In other words, as much of YYYY-MM-DDThh:mm:ss.sTZD as is relevant to this dataset. If this file is brand-new, enter the **issued** date here as well. +**Usage Notes** | Dates should be [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) of least resolution. In other words, as much of YYYY-MM-DDThh:mm:ss.sTZD as is relevant to this dataset. If this file is brand-new, enter the **issued** date here as well. **Example** | `{"modified":"2012-01-15"}` {: .table .table-striped} @@ -337,7 +337,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (0,1) **Required** | Yes, if applicable **Accepted Values** | ISO 8601 Date -**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://www.w3.org/TR/NOTE-datetime) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. +**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. **Example** | `{"temporal":"2000-01-15T00:45:00Z/2010-01-15T00:06:00Z"}` {: .table .table-striped} From c21e621da8fc40ab5f77b2f31c606e678084b260 Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Wed, 29 Jan 2014 15:23:31 -0500 Subject: [PATCH 4/6] added ISO 8601 clarications, corrected spelling --- schema.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/schema.md b/schema.md index 1a1a9189..099fd21c 100644 --- a/schema.md +++ b/schema.md @@ -283,8 +283,10 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (1,1) **Required** | Yes, always **Accepted Values** | ISO 8601 Date -**Usage Notes** | Dates should be [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) of least resolution. In other words, as much of YYYY-MM-DDThh:mm:ss.sTZD as is relevant to this dataset. If this file is brand-new, enter the **issued** date here as well. -**Example** | `{"modified":"2012-01-15"}` +**Usage Notes** | Dates should be [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) of least resolution. In other words, as much of YYYY-MM-DDThh:mm:ss.sTZD as is relevant to this dataset. If this file is brand-new, enter the **issued** date here as well. + +If there is a need to reflect that the dataset is continually updated, ISO 8601 formatting can account for this by [giving the duration](http://en.wikipedia.org/wiki/ISO_8601#Durations). For instance, `P1D` for daily, `P2W` for every two weeks, and `PT5M` for every five minutes. +**Example** | `{"modified":"2012-01-15"}` or `{"modified":"P1D"}` {: .table .table-striped} **Field** | **PrimaryITInvestmentUII** @@ -337,8 +339,12 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (0,1) **Required** | Yes, if applicable **Accepted Values** | ISO 8601 Date -**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. -**Example** | `{"temporal":"2000-01-15T00:45:00Z/2010-01-15T00:06:00Z"}` +**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. + +If there is a need to reflect that the dataset is continually updated, ISO 8601 formatting can account for this by [with repeating intervals](http://en.wikipedia.org/wiki/ISO_8601#Time_intervals). For instance, updated monthly starting in January 2010 and continuing through the present would be represented as: `R/2010-01/P1M`. + +Updated every 5 minutes beginning on February 15, 2010 would be represented as: `R/2010-02-15/PT5M`. +**Example** | `{"temporal":"2000-01-15T00:45:00Z/2010-01-15T00:06:00Z"}` or `{"temporal":"R/2000-01-15T00:45:00Z/P1W"}` {: .table .table-striped} **Field** | **theme** @@ -347,7 +353,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Required** | No **Accepted Values** | Array of strings **Usage Notes** | Separate multiple categories with a comma. Could include [ISO Topic Categories](http://www.isotopicmaps.org/). -**Example** | `{"theme":["vegetables"]}` or if muplitle categories, `{"theme":["vegetables","produce"]}` +**Examples** | `{"theme":["vegetables"]}` or if multiple categories, `{"theme":["vegetables","produce"]}` {: .table .table-striped} **Field** | **title** From 15162545e645e7658bbc2a96a9e8772ade893c03 Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Wed, 29 Jan 2014 15:24:49 -0500 Subject: [PATCH 5/6] removed extra word in temporal --- schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema.md b/schema.md index 099fd21c..1f9ae0b9 100644 --- a/schema.md +++ b/schema.md @@ -341,7 +341,7 @@ If there is a need to reflect that the dataset is continually updated, ISO 8601 **Accepted Values** | ISO 8601 Date **Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times. -If there is a need to reflect that the dataset is continually updated, ISO 8601 formatting can account for this by [with repeating intervals](http://en.wikipedia.org/wiki/ISO_8601#Time_intervals). For instance, updated monthly starting in January 2010 and continuing through the present would be represented as: `R/2010-01/P1M`. +If there is a need to reflect that the dataset is continually updated, ISO 8601 formatting can account for this [with repeating intervals](http://en.wikipedia.org/wiki/ISO_8601#Time_intervals). For instance, updated monthly starting in January 2010 and continuing through the present would be represented as: `R/2010-01/P1M`. Updated every 5 minutes beginning on February 15, 2010 would be represented as: `R/2010-02-15/PT5M`. **Example** | `{"temporal":"2000-01-15T00:45:00Z/2010-01-15T00:06:00Z"}` or `{"temporal":"R/2000-01-15T00:45:00Z/P1W"}` From 97ecb2f3509b0bf51e42f3fdb971945efa4b182b Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Wed, 29 Jan 2014 15:27:54 -0500 Subject: [PATCH 6/6] added link for Open XML mime types --- schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema.md b/schema.md index 1f9ae0b9..856a464f 100644 --- a/schema.md +++ b/schema.md @@ -211,7 +211,7 @@ Further Metadata Field Guidance (alphabetical by JSON field) **Cardinality** | (0,1) **Required** | Yes, if the file is available for public download. **Accepted Values** | String -**Usage Notes** | This must describe the exact files available at **accessURL** using [MIME Types](http://en.wikipedia.org/wiki/Internet_media_type). +**Usage Notes** | This must describe the exact files available at **accessURL** using [MIME Types](http://en.wikipedia.org/wiki/Internet_media_type). _[Also note [Office Open XML MIME types](http://blogs.msdn.com/b/vsofficedeveloper/archive/2008/05/08/office-2007-open-xml-mime-types.aspx)]_ **Example** | `{"format":"application/json"}` {: .table .table-striped}