W3C home > Mailing lists > Public > www-html@w3.org > August 2006

Re: extensibility of role/class/property/rel Re: Security Markup

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Tue, 22 Aug 2006 10:01:08 +0100
Message-ID: <640dd5060608220201u4afc9879kd4b1d6cc111b1b8b@mail.gmail.com>
To: "Karl Dubost" <karl@w3.org>
Cc: "Al Gilman" <Alfred.S.Gilman@ieee.org>, XHTML-Liste <www-html@w3.org>


> but the issue, I have raised is about the second aspects, which is
> the mechanism to prefetch values and their definitions in a user
> agents. The same way, it is possible to fetch DTD, schemas, etc and
> do something with them because the software knows the grammar for
> reading a DTD or schema

If I understand you correctly, you are saying that behaviour can be
defined using RDF, and this RDF can be retrieved at run-time based on
the use of @role. If so, I agree with you 110%. That has been my
'dream', so to speak, since even before I got involved in the HTML WG.
;) However...as Shane has pointed out, what the group has been very
careful to do, is not *mandate* this approach.

I think we've gone about as far as we can at this stage of the
language's development by adding the necessary hooks for such
functionality--@role, RDFa, and so on. The next phase is to let people
use it, and see what emerges. Taxonomies like the one Al refers to
will begin to emerge, and then we can start looking at how we define
the features of those taxonomies, how we locate them, and so on. But
it would be premature to try to define this now, since we just don't
have the experience. (And that definition need not be in XHTML 2
anyway, but should be a separate spec.)

So, the state of play is that we have a mechanism that can be used in
a many ways...we have a 'hook'. This hook could be used simply as a
container for a unique cookie that a browser or some server process
understands inately (the QName as identifier), or the hook could point
to some data to be retrieved and used by a process, such as a
server-side transformation or dynamically in the browser itself to
control behaviour (the QName as URI). But at the moment implementers
can choose how to use it.



Mark Birbeck
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
Received on Tuesday, 22 August 2006 09:01:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:14 UTC