OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: painting types

But it also clearly points to the true limits 
or minimalism of XML's victory.  XML depends 
at it's base on lexical unification; not 
infosets, but syntax.  So your first proposal 
to solve the type problem involves using a different 
syntax (not XML parsable, so not XML) to 
create something akin to architectural forms 
thus breaking the tie to XML by tieing it to CSS.

Who wins?  All you suggest is to move the choice 
to a different means controlled by a different 
means of choosing.  Now instead of Bray, it's Bos.
To quote Goldfarb: "They want to own the parse."

Nodes is nodes.  Properties is propeties.  MMTT.


Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com]

CSS already uses a 'painting' approach with formatting, and RDF seems 
capable of doing similar things as metadata.

I can't say that I would mind seeing something like:

invoice {type:invoice;}
invoice invoiceNum {type:integer;}
invoice date {type:date;}
invoice item {type:item;}

to use ad hoc CSS syntax as I sit here at a payphone on a 7.2bps connection.

Seems like there'd be a lot of room to run with this, and it could be 
genuinely useful in a wide variety of cases.