researchobject / principles Goto Github PK

This issue was raised as a result of a failure of Dani's test RO, which is a static object that contains all objects related to a publication. No further evolution will take place to this object, and hence no need for RO versioning control.

The original principle 7 needs to be more precise to clarify that evolution management is required when applicable, but not universal

This is related to issue #1

This is related to principle 3. An RO and its components should be associated with a minimal set of basic metadata about them, including how they relate to each other, and provenance (i.e. where they came from, when etc), to assist attribution, versioning, citation, knowledge exchange and reproducibility, and based on the fact that Dani's RO failed to pass this principle

Originally it had "An RO and its metadata should be made both machine processable and human consumable."

Currently we have "An RO and its metadata should be made machine processable, i.e being represented in a standard format and language that can be understood by machines"