[ 
https://issues.apache.org/jira/browse/DERBY-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim Haase updated DERBY-6633:
-----------------------------

    Attachment: DERBY-6633.zip
                DERBY-6633.stat
                DERBY-6633.diff

Thanks for the suggestions on what needs doing, Knut. Attaching 
DERBY-6633.diff, DERBY-6633.stat, and DERBY-6633.zip, with changes to 7 topics:

M       src/ref/rreffuncxmlparse.dita
M       src/ref/rreffuncxmlserialize.dita
M       src/ref/rreflimitsxml.dita
M       src/ref/rrefsqljtypexml.dita
M       src/ref/rreffuncxmlquery.dita
M       src/ref/rreffuncxmlexists.dita
M       src/devguide/cdevstandardsxml.dita

I removed the second table row from the "XML Limitations" topic and removed the 
usage notes from the XML operator topics, moving the reference to the Dev Guide 
topic elsewhere. I'm not at all confident of the text I substituted for the 
previous info about XPaths and parsers, so I would appreciate any edits you 
have there. For the XML data type topic, I removed the note, added some 
cross-references, and fixed some formatting and punctuation.

There was no need for changes to the "java.sql.SQLXML interface" topic.

Thanks in advance!

> Remove DOM level 3 XPath requirement from description of XML operators
> ----------------------------------------------------------------------
>
>                 Key: DERBY-6633
>                 URL: https://issues.apache.org/jira/browse/DERBY-6633
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>         Attachments: DERBY-6633.diff, DERBY-6633.stat, DERBY-6633.zip
>
>
> After DERBY-6624, it is no longer a requirement to have an implementation of 
> the DOM level 3 XPath specification in order to use the XML operators. The 
> docs should stop mentioning the requirement.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to