RE: Invitation to the April 28 Collaboration Expedition Workshop, no fee, please RSVP

    mixed markup documents
    http://www.w3.org/2004/03/plenary-minutes#Session4

I liked this bit.

Mark Birbeck: It's impossible for any browser vendor to keep up. There's no
point in having an ever-increasing list of mime media types, we need to go
the opposite way. Build in support on the client end for the different
namespaces, a has-feature attribute or something.

This is providing locally the older Als ingenious idea, which we had
remotely?

The issued picked up by TimBL is interesting. Does the user/his software,
have to 
differentiate between SVG in a root ns of HTML and SVG in a root ns of SMIL?
Should
an applications action on meeting ns X always be the same or can it vary
dependent on
context?

This idea of required features, is it an application that responds to a
metadata
statement that an app must have required feature A,B and C? Fallbacks?
quote. timbl in IRC: I don't think that the mixed namespace can be done in
general, but can be done within an application area. unquote.

In other words, I'm OK if I know what to expect, but don't throw me a
googly? That makes
sense.

sean in IRC: The problem as I see it is we are applying tools like schema
which work at the syntax level to semantic issues. (then later) ....But
combining unknown semantics is undefined.


Good point. Its no good an application saying 'I can hack SVG', it needs to
say I can do
this with that 'class' of SVG or subset of SVG or to say that it can digest
this semantic.
The point about soap carrying a purchase order is a good example. How might
this semantic
be captured? Our area of interest is identical. A webpage with animated SVG
is not 
dissimilar. The metadata needs to say that to grok this page, you must be
able to process
(whatever that means to you) an animated SVG image. 

How on earth do you capture that in metadata!

Good read. Thanks Al.

regards DaveP




- 
DISCLAIMER: 

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged. If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system. 

RNIB endeavours to ensure that emails and any attachments generated by 
its staff are free from viruses or other contaminants. However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments. 

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent 
those of RNIB. 

RNIB Registered Charity Number: 226227 

Website: http://www.rnib.org.uk

Received on Friday, 2 April 2004 02:17:51 UTC