[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: A heavier-weight proposal for character entity definition
My problem with this is that it appears to conflate the large system (the internet) requirements with the more modest requirements of the specific application language. The latter can always be built as a bound application with mush less support for character entities it doesn't need. Combining all of MathML plus the other sets seems to be contrary to modularity and layering. CALS tended to fall apart when the drive for a standard system conflicted with the local system builders. A bridge too far? len -----Original Message----- From: James Clark [mailto:jjc@j...] Suppose for example there is a standard W3C-defined builtin entity set; this would have a version number and would add new characters from time to time (but never change existing entity names). There would be a standard mapping from a version number to a URI where a XML specification of the entity set would be available. However, parsers wouldn't have to fetch and parse this, they could just recognize the version number and refer to an appropriate compiled-in table.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|