Data not compliant with designated schema can be loaded successfully
When creating a record that includes attributes that do not exist in the schema for that particular kind, I would expect the data to be rejected. However, the data is accepted and the record is created. See the example data below where an attribute called "InvalidAttr" was included:
{
"acl": {
"owners": [
"data.certification473.owners@osduvalidation.osduvalidation.com"
],
"viewers": [
"data.certification59744.viewers@osduvalidation.osduvalidation.com"
]
},
"data": {
"ResourceID": "srn:master-data/Well:999322544063999:",
"InvalidAttr": "bad_data",
"ResourceTypeID": "srn:type:master-data/Well:",
"ResourceSecurityClassification": "srn:reference-data/ResourceSecurityClassification:RESTRICTED:",
"UWI": "999322544063999"
},
"id": "osduvalidation:osdu:999322544063999",
"kind": "osduvalidation:osdu:well-master:0.2.1",
"legal": {
"legaltags": [
"osduvalidation-osdu-certification-test-tag4396232"
],
"otherRelevantDataCountries": [
"US"
],
"status": "compliant"
},
"meta": [
{}
],
"version": 0
}
For reference: https://community.opengroup.org/osdu/documentation/-/wikis/Releases/R2.0/Services/Storage/Tutorial#creating-records