Indicate which documents/elements in repository we consider to be normative. Those documents would have to go through more rigorous review (e.g. open for 30 days of public comment) before they can be changed/published as a new release. I suggest that those documents are the 4 json schemas: camtrap-dp-profile.json, deployments-table-schema.json, media-table-schema.json, observations-table-schema.json. Those 4 schemas are served as versioned files and referenced in published Camtrap DP, they could benefit from wide review.
Decide if we want to include a vocabulary of terms minted by Camtrap DP that could be useful for other standards:
Create list of potential terms: those would terms that a) we didn't borrow from other vocabularies such as Darwin Core or Audiovisual Core and b) might be useful to others. Examples are cameraDelay, cameraTilt, etc.
Decide how we want to maintain these terms: either as part of Camtrap DP (requires additional normative document, landing page, scripts to push to https://rs.tdwg.org) or trying to get them included in other standards such as Audubon Core.
Decide on the names/definitions of the terms: these should be generic enough that they can be used in other standards
Based on step 4, decide whether Camtrap DP is a technical specification or a vocabulary. The maintenance of the latter has to follow the Vocabulary Maintenance Standard and allows to establish a Maintenance Group, for technical specifications there are no documented maintenance rules.
Suggest a review manager
Upon acceptance, create a landing page for the standard at tdwg.org. Those pages have specific header information and lists the "parts of the standard", see e.g. https://www.tdwg.org/standards/abcd/
This issue is mostly based on a conversation I had with @baskaufs.
In the paper we indicate that through TDWG we can seek ratification as a standard. To do so, we need:
Establish a Task Group. My suggestion would be to do this under the Machine Observations Interest Group.
Indicate which documents/elements in repository we consider to be normative. Those documents would have to go through more rigorous review (e.g. open for 30 days of public comment) before they can be changed/published as a new release. I suggest that those documents are the 4 json schemas:
camtrap-dp-profile.json,deployments-table-schema.json,media-table-schema.json,observations-table-schema.json. Those 4 schemas are served as versioned files and referenced in published Camtrap DP, they could benefit from wide review.Decide if we want to include a vocabulary of terms minted by Camtrap DP that could be useful for other standards:
cameraDelay,cameraTilt, etc.Based on step 4, decide whether Camtrap DP is a technical specification or a vocabulary. The maintenance of the latter has to follow the Vocabulary Maintenance Standard and allows to establish a Maintenance Group, for technical specifications there are no documented maintenance rules.
Suggest a review manager
Upon acceptance, create a landing page for the standard at tdwg.org. Those pages have specific header information and lists the "parts of the standard", see e.g. https://www.tdwg.org/standards/abcd/