We propose that the following model that emulates the best of OSDU & ODES OSDU
?Include a reference to schema service, on implementation & guidelines on-increment a version? : Semantic versioning scheme for the schema. entityType: name of the entity, wells, logs, seismic3d etc.The latter two may have a specific meaning such that wke relates to master/curated data and ref-data refers to reference values & types such as log codes. source: source of this data, such as ihs, boem, wke, ref-data etc.namespace : the authority who published this schema and manages versions to it, eg.The pattern currently used is ., example common:boem:well:1.0.0. OpenDESĮach record in OpenDES storage has a kind property, identifying to which schema it wants to be associated with. OpenDES and OSDU have different ways to identify a schema - Kind vs ResourceType.
Master Data, Reference Data, Work Product & Work Product Components Problem Statement Use of $ref & $allOf, to reuse schema definitions.Master Data, Reference Data, Work Product & Work Product Components Handling Identifiers - updated rationale to link the parent page. Master Data, Reference Data, Work Product & Work Product Components - Added more examples, linked the page that captures the EA notes. Subsequently this page is updated to reflect those additional recommendations. The original proposals have remained more or less unchanged.
The proposals were submitted & reviewed by core members of EA subcommittee in December 2019. This page & the recommendations are collectively authored by the following members, during the three week period from.
0 kommentar(er)
