From 45dc06f2b5faa3333cb4f3f4372358e472dc4adf Mon Sep 17 00:00:00 2001 From: Ken Kroenlein Date: Wed, 18 Sep 2019 18:09:29 -0600 Subject: [PATCH 1/2] Added some procurement information --- docs/specification/objects.md | 27 ++++++++++++++++++++++++--- 1 file changed, 24 insertions(+), 3 deletions(-) diff --git a/docs/specification/objects.md b/docs/specification/objects.md index 3e19a4e..2861966 100644 --- a/docs/specification/objects.md +++ b/docs/specification/objects.md @@ -93,7 +93,7 @@ condition names | must be unique | among condition names "nominal" : 450, "units" : "kelvin" } - }, + }, { "type" : "parameter", "name" : "Baking Time", @@ -191,7 +191,7 @@ Same as `ProcessSpec`, but with the `template` inherited from the `spec`, i.e. ` "upper_bound" : 452.5, "units" : "kelvin" } - }, + }, { "type" : "parameter", "name" : "Baking Time", @@ -681,7 +681,9 @@ Provenance is the documented history of an Object. This includes information such as who performed a measurement, the literature source for a process specification, or the purveyor and catalog number for a purchased material. This type of information tends to have limited value for modeling and other analysis but is essential for verification and auditing. -At present the only type of source supported is who performed a task and when they did so. +At present the two types of source are supported: who performed a task and when they did so; and from where a material was procured + +### Performed Source Field name | Value type | Default | Description --------------|------------|---------|------------- @@ -700,3 +702,22 @@ Field name | Value type | Default | Description } ``` +### Procured Source + +Field name | Value type | Default | Description +-----------|------------|---------|------------- +`procured_from`| String | None | The vendor or supplier who provided the material +`procured_date`| String | None | The date the material was obtained; ISO-8601 date-formatted string (YYYY-MM-DD or YYYY-MM-DDTHH:mm:SS) +`catalog_no`| String | None | The vendor-specific identification code for the material + +##### Example + +```json +{ + "type": "procured_source", + "procured_from": "joe@abc.com", + "procured_date": "2015-03-14T15:09:27", + "catalog_no": "B0722DW2KY", + +} +``` From 4cfcba90b98b025330bcf17e6694ae91af54035d Mon Sep 17 00:00:00 2001 From: Ken Kroenlein Date: Wed, 18 Sep 2019 18:13:51 -0600 Subject: [PATCH 2/2] Corrected type oversight --- docs/specification/objects.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/specification/objects.md b/docs/specification/objects.md index 2861966..434fb4c 100644 --- a/docs/specification/objects.md +++ b/docs/specification/objects.md @@ -706,6 +706,7 @@ Field name | Value type | Default | Description Field name | Value type | Default | Description -----------|------------|---------|------------- +`type` | String | Req. | "procured_source" `procured_from`| String | None | The vendor or supplier who provided the material `procured_date`| String | None | The date the material was obtained; ISO-8601 date-formatted string (YYYY-MM-DD or YYYY-MM-DDTHH:mm:SS) `catalog_no`| String | None | The vendor-specific identification code for the material @@ -715,9 +716,8 @@ Field name | Value type | Default | Description ```json { "type": "procured_source", - "procured_from": "joe@abc.com", - "procured_date": "2015-03-14T15:09:27", + "procured_from": "amazon.com", + "procured_date": "2019-07-22T08:09:27", "catalog_no": "B0722DW2KY", - } ```