Yes, I suggested
this previously [1]. Basically the arcrole becomes the NS-URI of
the format
generated by the transform.
The additional
benefit of identifying the output using the NS-URI is one can
piece together
transformation pipelines by recursively investigating the RDDL
documents at each
URI.
I don't think
Jonathan put this into the spec, but I notice that number of
the examples in
the spec (do a View Source) follow this guideline.
Cheers,
L.
I've been wondering about how one could define a
standard set of transformation rules for a XML vocabulary, and thought RDDL
might be the solution but the specification is not very informative. In terms
of an application accessing a XML file in some proprietary format, the
question is how can an application determine how we can transform this file
into a format that can be presented to the user e.g. XHTML. RDDL could allow
that information to be accessible from the namespace URI. I envisage this form
of usage:
<rddl:resource
xlink:role="http://www.w3.org/1999/XSL/Transform"
xlink:arcrole="...
namespace URI of XSLT output eg XHTML
..."
xlink:href="
... " />
This could be a standard way for authors and
applications alike to locate required XSLT resources. Comments?
Lyndon
Lyndon J B Nixon ... MAGIC Centre, FHG FOKUS ... Berlin,
Germany
"what is now proved was once only imagined" - william
blake
PhD Student, Integration of Internet with MPEG-4 &
MPEG-7
nixon@f...
members.lycos.co.uk/madeejit/phd.htm
|
Cart
