Open pbuttigieg opened 8 months ago
each pattern for a metadata module (e.g. Organization, Person,Project, DefinedTerm, VariableMeasured) or resource type (e.g Dataset, Map, Service, Thing, DataRepository, CreativeWork) should have a separate pull request. The proposal in #3 is that each module should have one or more validation resources (JSON schema, SHACL rules), examples, and templates. See packages at https://github.com/smrgeoinfo/cdif-core/tree/inReview/in_review. When these modules are 'adopted' they will get pulled into main. Until then, the proposed content will need to reside in some repo somewhere with a set of commits for the content that the PR will bring into cdif-core main.
Once a module is in cdif-core main, branches can be generated off main to propose updates to modules.
We'll initialise the CDIF core repository with domain-neutral content from the Ocean Data and Information System (ODIS).
We're beginning with the JSON-LD/schema.org patterns as a Source of Truth (SoT) upon which we can build first-order cross-domain exchange.