enhancements to CTA implementation
----------------------------------

                 Key: XERCESJ-1541
                 URL: https://issues.apache.org/jira/browse/XERCESJ-1541
             Project: Xerces2-J
          Issue Type: Improvement
          Components: XML Schema 1.1 Structures
    Affects Versions: 2.11.0
            Reporter: Mukul Gandhi
            Assignee: Mukul Gandhi


I thought it's good to create this JIRA issue for tracking purposes.

Following is a summary of significant enhancements we've done to XSD 1.1 CTA 
implementation within Xerces, post 2.11.0 release. 

- added in-scope namespaces to XDM tree for type alternatives (for full XPath 
mode evaluation). this makes possible namespace aware operations on CTA XDM 
nodes (e.g fn:resolve-QName etc)
- enhanced static type checking of CTA XPath expressions. essentially to raise 
certain errors during static analysis phase for XPath expressions (after 
parsing and before evaluation), for e.g to detect of the schema type used in 
XPath expression is not present in in-scope schema types in XPath static 
context, or if the namespace prefix used in XPath expressions is declared.
- the XDM tree of CTA now carry the document URI of the parent document.
- we now set base-uri property in CTA's XPath static context.
- we now correctly set type annotations on CTA XDM nodes, namely xs:untyped on 
the root element node, and xs:untypedAtomic on it's possible attribute.

Other than these, we've made improvements to quite a few XPath 2.0 F&O 
implementations within PsychoPath XPath engine, which will benefit both CTA and 
assertions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to