|
|
Dear Tod,
Option 2 and 5 do not make sense. Option 4 is technologically odd -
Aaron suggested RDF(S) + (X)HTML + RDDL.
The semantic overlap of RDDL with DC has not been considered really.
As i said at another occasion: I'm curious about stability and consequences
of the mapping RDDL to RDF (http://www.openhealth.org/RDDL/ "7.5 RDF Schema for RDDL"
as well as http://www.w3.org/TR/xlink2rdf/ "Status")
There is more to be said about, but for now...
Maybe one should put issues RDDL poses to the work items of dc-architecture -
The dc-tools ws opted for RDF - parser understandable (i.e. W3C's RDF/XML M&S)
and human understandable (XHTML rendering).
Embedding of RDF in XHTML was considered one possible technical solution -
Harry mentioned XSLT transforms on a given XML representation of RDF -
rs
|
|
|
|