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
Author: Giridhar Manepalli
Date: 13 Dec, 2013
(I'm not sure how this message will show up on the website. I thought I should just try and see.)
First, thanks for starting a thread on the schema topic. In order for the schema (and the model behind it) to be reasonably useful for multiple parties, I'm pretty sure we need to tweak the model that I defined in the powerpoint slide that you quoted. But we need to start somewhere. Since there is no formal JSON schema language as far as I know, one or two examples in JSON would be useful in addition to the slide. I will update that slide a bit to add more context. And also include a few JSON examples. Expect those from CNRI sometime next week. And we can take it from there. If the working group members happen to like the examples, CNRI can try and release a prototype type registry before the end of the year. After getting some feedback from the working group members, we can decide to write a formal document describing types and type registries.
You have also talked about being interested in an RDF serialization. I assume you mean RDF-XML or JSON-LD or something along those lines. A complementary and sometimes confusing aspect is that a type-record could include an OWL or an RDF schema under the "semantic information" label. So now you end up with a type-record serialized in, say, RDF-XML, which includes an RDF schema (also perhaps serialized in RDF-XML). But we can ignore that issue for now.
Finally, during the RDA meeting in September, we had a few folks who presented use cases. I assume those use cases are what you meant by "worked examples."