[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: various issues
Peter Murray-Rust writes: > This sounds exactly what is needed but the bad news is that I > know nothing about architectural forms. I suspect this is true for > some other readers of this list as well. I would be grateful for > any pointers (and brief explanations here if possible.) Here are > some very naive questions... For a quick introduction to Architectural Forms, see http://www.jclark.com/sp/archform.htm For other information, see http://www.sil.org/sgml/topics.html#archForms > - are AFs part of HyTime or more generally part of SGML? Architectural forms were originally specific to HyTime, but in the forthcoming Annex 1 of the standard, they have been generalised -- HyTime is one base architecture, but DSSSL is another, as is the Canadian GILS project. > - does XML support AFs without further revisison? > - if not, what has to be added? or is it possible to build this > into tools without breaking the spec? > - if tools have to be built, is the processing required at > parser level? There are different ways of dealing with AFs. James Clark's SP library can do special, smart AF processing, where it actually parses the document as if it were an instance of the base architecture rather than of the derived architecture, but that is not always necessary (or desirable). XML-based tools can simply look for the <?ArcBase ...?> processing instruction and the associated notation declaration, and then use the attribute values for processing. NXP-based apps, for example, should be able to handle this, but DTD-less parsing will not be possible unless the attribute values are included in the document instance itself (I consider this a feature rather than a bug). The one short-coming is that XML does not support data-attributes, so it will not be possible to customise the AF support -- you'll have to stick with the defaults. > - do the components belonging to different DTDs have to live in > separate files or can they be separated within a single > file (e.g. by NOTATIONs)? They should be stored in separate files (etc.), just like public entity sets. > - if someone decides they need AFs are they easy to implement? > (for my requirements it looks like an aliasing mechanism > would suffice. This _is_ an aliasing mechanism, of sorts. All the best, David -- David Megginson ak117@f... Microstar Software Ltd. dmeggins@m... University of Ottawa dmeggins@u... http://www.uottawa.ca/~dmeggins xml-dev: A list for W3C XML Developers Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To unsubscribe, send to majordomo@i... the following message; unsubscribe xml-dev List coordinator, Henry Rzepa (rzepa@i...)
|
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
|