XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] XML support in browsers?

Concerning the lack of namespace axis support in firefox, there is a bug fixed : https://bugzilla.mozilla.org/show_bug.cgi?id=94270 but waiting to be loaded. The last problem is to say if the XSLT expression :

<xsl:value-of select="string(count(nsa:data/descendant-or-self::*/namespace::*))"/>

on that test :

<nsa:testsuite xmlns:nsa="http://www.mozilla.org/firefox/xslt/namespace-axis">
   ...
    <nsa:test id="20">
        <nsa:assertion expectedvalue="3" uri="http://www.w3.org/TR/xpath#namespace-nodes">The
            'nsa:data' element sub-tree has a total of 3 namespace nodes.</nsa:assertion>> <nsa:data>
            <x xmlns:edi="http://ecommerce.example.org/schema">
                <y/>
            </x>
        </nsa:data>
    </nsa:test>
</nsa:testsuite>

must return 3 nodes or 8 , but that is a minor problem I think.

There are still lots of performance issues triggering XSLT in the browser, and in firefox it freezes the whole navigation, which is difficult to accept. I think performance stays the major issue of XML against JSON, used on the client side. Maybe we could trigger XSLT with options which reduce processing time, like disabling namespaces support, or using streaming capabilities.

Nico
http://debeissat.nicolas.free.fr/xsl_tests.php

2009/6/8 COUTHURES Alain <alain.couthures@agencexml.com>
Hi Robert,

Opera not handling the document function, but really, who cares?
Opera is not handling the document() function correctly but it exists.

For XSLTForms (http://www.agencexml.com/xsltforms), my client-side XForms implementation, external schemas are parsed using the document() function. Opera succeeds in loading the external file but there is a confusion at the attribute level : when the namespace definition (let's say xmlns:xs) is written before the @targetNamespace, the @targetNamespace is unseen while xmlns:xs is presented as an attribute (when the namespace definition is moved to last position, it works...) !

Best regards,

Alain Couthures
<agenceXML>
Bordeaux, France

_______________________________________________________________________


XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS