- From: Laurens Holst <lholst@students.cs.uu.nl>
- Date: Thu, 26 Jan 2006 17:03:52 +0100
- To: Jim Ley <jim@jibbering.com>
- Cc: Steven Pemberton <steven.pemberton@cwi.nl>, Anne van Kesteren <annevk@opera.com>, Shane McCarron <xhtml2-issues@hades.mn.aptest.com>, www-html-editor@w3.org
Jim Ley schreef: >> It is not true that the browser has to support XML Schema in order >> for it to work. > > Browsers currently support XSLT, to use XSLT with QNames in Attribute > context the browsers either need specialist knowledge of the doctype, > or they need support for XML Schema. I don’t see how they wouldn’t need knowledge of the doctype anyway in order to sensibly process the XHTML anyway. This is the case for rel + relNS as well, XSLT can do nothing with the attribute if it doesn’t know that NS contains a namespace, etc. >> All the browser has to know, if it needs to do anything special with >> these values at all, is that the attribute is a QName. > > Please stop using QNames in attribute context, rel and relNS > attributes achieve this and meet all your above advantages. > Alternatively change XSLT to support QNames in attribute context, > XHTML is an XML language and must be compatible with XSLT, it is > currently not. XSLT 2.0 has functionality to resolve QNames, see section 11 of the current Functions and Operators specification [1]. I have used this functionality already for an odd case, and although it’s not really compact, it works just fine. With regard to rel and relNS, if you want to explicitly have to specify the entire namespace URI, instead of introducing something new wouldn’t it be better to follow RDF then, and have rel="http://example.org/namespace#something ? ~Grauw [1] http://www.w3.org/TR/xpath-functions/#QName-funcs -- Ushiko-san! Kimi wa doushite, Ushiko-san!! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Laurens Holst, student, university of Utrecht, the Netherlands. Website: www.grauw.nl. Backbase employee; www.backbase.com.
Received on Thursday, 26 January 2006 16:03:58 UTC