We are interested in the 'schema' for the data type descriptions being proposed for the prototype DT registry (I recall it is JSON). We would like to get some experience using it for data types that we use, and evaluate whether it provides enough scope for our needs. This should provide some validation of the design.
We are also interested in variant serializations, including RDF. This is not hard to derive from JSON of course.
I've fossicked around on the DTR area on the RDA website and found this table in Giridhar's ppt from September. Is this it? I was looking for something more formal but have not been able to find it.
Cardinality (min, max)
A unique, persistent identifier. Assigned by a type registry
Description in English mandatory. Descriptions in other languages as needed
Who created it, when, etc.
Properties that describe data. Aka predicates. For example, a weather dataset contains time, location, and temperature properties
File-formats (mime-types), etc.
OWL, KIF, etc.
WSDL, WADL, APIs, etc.
I also recall seeing some worked examples presented, but can't locate those. Could these be made available.
Simon J D Cox
Land and Water
E ***@***.*** T +61 3 9252 6342 M +61 403 302 672
37 Graham Road, Highett, Vic
PO Box 56, Highett, Vic 3190
www.csiro.au | www.csiro.au/Simon.Cox
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
Please consider the environment before printing this email.
Data type description formalization
You are here