ZedAI RDFa11 adaption
From zedwiki
Contents |
Step 1
Profile provision
- A base URI for ZedAI RDFa profile documents is created at http://www.daisy.org/z3986/2011/vocab/profiles/
- An RDFa 1.1 compliant profile document is created at http://www.daisy.org/z3986/2011/vocab/profiles/default/
- This profile document reserves the following prefixes:
- "" : http://www.daisy.org/z3986/2011/vocab/structure/#
- "z3986" : http://http://www.daisy.org/z3986/2011/vocab/decl/#
- "dcterms" : http://purl.org/dc/terms/
- An RDFa 1.1 compliant profile document is created at http://www.daisy.org/z3986/2011/vocab/profiles/periodicals/
- This profile document reserves the following prefixes:
- "" : http://www.daisy.org/z3986/2011/vocab/periodicals/#
- "z3986" : http://http://www.daisy.org/z3986/2011/vocab/decl/#
- "dcterms" : http://purl.org/dc/terms/
- "struct" : http://www.daisy.org/z3986/2011/vocab/structure/#
- New htaccess files is included in the build to resolve http://www.daisy.org/z3986/2011/vocab/profile/*/ to the actual document
Schema changes
-
All ZedAI Profile RDs must declare exactly one RDFa profile URI that all instances must use: the defined URI must be provided in the root element profile attribute- added to spec prose and uri to RDs -
Define a new property in the RD vocabulary used for reserving the profile URI; update all RDs to include this information -
All zedai profile schemas get a root element attribute "profile" whose value is fixed to the profile defined by the ZedAI Profile RD: this attribute is required, and its definition provided by RDFa 1.1 Core -
All zedai profile schemas get a new root element attribute "prefix" to allow additional prefix-uri associations; this attribute is optional, and its definition provided by RDFa 1.1 Core -
The "profile" and "prefix" attributes are only allowed to occur on zedai instance document root element- are they reserved attributes? (or can they be defined for other purposes on other elements?) -
The use of xmlns to create prefix-uri associations is forbidden (schematron test for this?) -
We add spec prose that makes clear that the reserved prefixes must not be redeclared in instances (references to the reserved URIs is not allowed in the prefix attribute) -
The RDFa 1.1 "vocab" attribute is not included in the ZedAI adaption (?) -
Schematron tests are written to assure the profile's prefix reservations are followed (can test on at least: z3986 (in head meta), dcterms (in head meta)) -
Schematron tests are written to assure that any prefix beyond the reserved one is declared in @prefix root -
The existing rdfa attributes module is updated to RDFa 1.1 compliance (note: we stay with CURIEs only for values, but be silent on this topic in the spec, set this restriction in the core modules instead) -
Spec and primer and samples is updated to reflect the above
Update of Resource Directories
- All Resource Directory documents are also updated:
-
version attribute value (RDFa 1.1)- removed as per latest draft -
adding a "prefix" attribute to root that associates "rd" with "http://www.daisy.org/z3986/2011/vocab/resourcedirectory/#" -
(make sure the rd prefix is used in RD instance body)
-
- The templates provided through RDs are updated.
Update of vocabularies
- The XHTML build for all vocabs under http://www.daisy.org/z3986/2011/vocab/ is also updated to use RDFa 1.1 (version attr, prefix attr, no use of xmlns)
Step 2
Consider adapting RDFa 1.1 to be used for function set declarations in the Content Selection feature.
This could be done using only the prefix attribute (no use of a profile document). We would need CSEL RD prose that explains this adaption, especially noting that this does not mean that the test attribute must validate against the CURIEsorTERMsorURIs datatype.
