/ Jirka Kosek <[EMAIL PROTECTED]> was heard to say: | 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
That just means your locating rules need to be powerful enough pick
the right one. Perhaps based on a profile attribute on the HTML
document or on a successful XPath match. There's room for debate about
just how Turing complete the locating rules algorithm should be.
| 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
Yes. That's "the packaging problem", one of XML's oddly unresolved
issues.
| 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
Even if it's the wrong one :-)
| 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.
Yep. I'm not really arguing against the PI as much as lamenting the
fact that the locating rules aren't more powerful and more portable.
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | Every vice you destroy has a
http://nwalsh.com/ | corresponding virtue, which perishes
| along with it.--Anatole France
pgpVTgZC0mw70.pgp
Description: PGP signature
