normalize how to define additionalProperty values

iodepo / odis-arch

Development of the Ocean Data and Information System (ODIS) architecture

https://book.odis.org/

27 stars 16 forks source link

normalize how to define additionalProperty values #163

Open jmckenna opened 1 year ago

jmckenna commented 1 year ago

we need to standardize how we define additionalProperty, throughout all patterns. Such as:

"additionalProperty": [
{
  "@type": "PropertyValue",
  "propertyID": "Expedition Code",
  "value": "exp_code"
},
{
  "@type": "PropertyValue",
  "propertyID": "Research Period",
  "value": "research_period"
},
{
  "@type": "PropertyValue",
  "propertyID": "Collaboration Opportunities",
  "value": "collab_opportunities"
}
]

from recent discussions through https://github.com/iodepo/odis-arch/issues/151

jmckenna commented 1 year ago

From example in https://github.com/schemaorg/schemaorg/issues/1685 :

 //additionalProperty can actually also be an array of property-value pairs

{
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "name": "myCustomProperty",
      "value": "my custom value"
    },
    {
      "@type": "PropertyValue",
      "name": "myOtherCustomProperty",
      "value": "my other custom value"
    }
  ]
}