Michael Smith wrote:
To be specific, by "existing schema-assocation mechanisms", I mean:- the locating-rules mechanism supported in nXML - David Tolpin's "Regular Associations for XML" mechanism, supported in ARX - whatever else there might be that does not depend on "hard coding" schema associations in individual document instances I use both the locating-rules and ARX mechanisms, and I cannot think of a use-case I could not deal with well by adding information to a locating-rules file or ARX config file.
There is one. Suppose that you have created microformat which is a subset of XHTML and you have defined RNC schema for it. Because this new format is based on XHTML it lives in http://www.w3.org/1999/xhtml namespace. If you will try to edit this document in XML editor with default setup you will be offered by full list of XHTML elements. You need some easy way (from user perspective) to override default schema bound to this namespace and use the restricted one.
If you will store schema association sideway into a some config file, users will lost this file when interchanging document. If you will store schema associtation inside document, it will be always here and when user creates new document from template it will be here also. Using PI for this seems harmless compared to <!DOCTYPE or xsi:schemaLocation because such PI don't have side effects. Applications that take care can use PI to fetch and use custom schema for guided editing or validation. Most of applications will simply ignore this PI and will process document as general XHTML code which is a right thing here.
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz
------------------------------------------------------------------
Profesionální školení a poradenství v oblasti technologií XML.
Podívejte se na náš nově spuštěný web http://DocBook.cz
Podrobný přehled školení http://xmlguru.cz/skoleni/
------------------------------------------------------------------
smime.p7s
Description: S/MIME Cryptographic Signature
