On 9 Nov 2005, at 10:55, Ian Davis wrote:
> On 11/9/05, Phil Shaw <[log in to unmask]> wrote:
> > I have a question for Ian. Why did you choose to reference the DC
> > properties with dc-creator instead of using the dot separator,
> > dc.creator?
>
> The embedded RDF spec supports both forms throughout. The problem with
> the dot notation in class attributes is that it confuses CSS so those
> classes can't be used for styling. It's important to be compatible
Do you propose a formal mapping from any-property to
any.property and any:property, or is it purely the responsibility of
the transformation to make sense of whatever prefix scheme is
used?
There is clearly a dependency between the source format, a
transformation service, the right to conduct the transformation and
the longevity of one's data. The widespread adoption of this format
is probably dependent on having a standard XSLT as part of the
specification in the public domain (as you have done).
This approach seems a more natural progression from XHTML than
the W3C discussions I read on this a while back. It's not literally
embedding RDF in XHTML, more like encoding RDF in XHTML.
Do you see a fit in with W3C plans, a rival or alternative?
Best regards,
Phil
--
MKSearch (beta)
http://www.mksearch.mkdoc.org/
Free, open source metadata search engine with RDF storage and query.
|