RE: Possible transformiix bug with defaulted attributes.

Forgive any misguided newbieness here but...

| -----Original Message-----
| From:	David Carlisle [SMTP:davidc@xxxxxxxxx]
| > The problem arises out of conditional match against a missing attribute
| > where the XML schema provides a default value.
| 
| there is nothing in either the XML or XSL specs that suggests that
| any XML application should default attributes from anything other than a
| DTD. 
Transformiix appears to accept the use of defauls in my schema when
validating XML, so I'm confused by the apparent distinction being drawn
between my schema and an equivalent DTD? Please clarify this for a newbie.

| And certainly you wouldn't expect anything other than MSXSL to
| understand this microsoft specific format of schema:
| 
| <Schema name="DefaultTestObject"
xmlns="urn:schemas-microsoft-com:xml-data"
Again I don't understand why this should confuse any parser. The form
appears consistent with the XML namespace specs and is irrelevant to the
processing I'm doing. I might just as well put
xmlns="http://www.agilic.com/default" or to slightly misquote Tim Bray
xmlns="AnyOldBollocks" (he was acually using for a named (html) namespace.
My understanding is that the URN is merely used to partition the name spaces
and it is identity or otherwise of these URN's that can affect processing,
not their actual form. Hence the validity of something like
"AnyOldBollocks".
| 
|                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^
| > but where the attribute is missing only MSXML v3 appears to perform
| > correctly, 
| 
| transformiix is quite correct here.
Anyone else have an opinion on this (Keith V?) or do I have to produce a
sample without the dreaded word "microsoft" in it!

tia
mark



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list