QT4 CG Dashboard

These are the open pull requests and current branches. Where possible, a summary of the changes between the pull request or branch and the latest drafts is provided with a DeltaXML pipeline.

Open PRs:
#2037
#2033
#2031
#2030
#2028
#2026
#2019
#2015
#2014
#2013
#2011
#1942
#1888
#1283
#1062

Pull requests in descending order

PR #2031: 2025 JNodes

Pull request #2031 by michaelhkay.

Fix #2025 This is a first draft for review. It includes changes to the data model, functions and operators, and XQuery/XPath. It does not yet include changes to XSLT. It's a big proposal, but I think it removes more complexity from the spec than it adds. It's basically a unification of two concepts, both of which were addressing aspects of the same problem, namely that lookup expressions lose too much information. It gets rid of the pin/label mechanism, and modifiers on lookup expressions, and introduces JNodes and JAxes in their place. (Any suggestions for improved terminology are more than welcome.) I think we get a lot more "bangs for the buck" with this solution, and it makes navigation of JSON trees work in a much closer way to familiar navigation of XML trees. It needs a lot more work on examples and explanation, of course.

Changed files
  • specifications/grammar-40/xpath-grammar.xml
  • specifications/image-sources/item-types.xml
  • specifications/xpath-datamodel-40/src/xpath-datamodel.xml
  • specifications/xpath-functions-40/src/function-catalog.xml
  • specifications/xpath-functions-40/src/xpath-functions.xml
  • specifications/xquery-40/src/expressions.xml
  • specifications/xslt-xquery-serialization-40/src/xslt-xquery-serialization.xml

PR #2030: 2029 xsd validator notes and examples

Pull request #2030 by michaelhkay.

Adds more explanation to xsd:validator Extracts material from the XQuery and XSLT specs describing the validation process, moving this to a new section in F&O, to reduce duplication. Fix #2029

Changed files
  • specifications/xpath-datamodel-40/src/xpath-datamodel.xml
  • specifications/xpath-functions-40/src/function-catalog.xml
  • specifications/xpath-functions-40/src/xpath-functions.xml
  • specifications/xquery-40/src/expressions.xml
  • specifications/xslt-40/src/xslt.xml

PR #2026: 2022 Drop module feature

Pull request #2026 by michaelhkay.

Fix #2022 The effect is that support for library modules is no longer optional. I decided not to pursue merging the "schema import" and "typed data" features into one.

Changed files
  • specifications/xquery-40/src/back-matter.xml
  • specifications/xquery-40/src/conformance.xml
  • specifications/xquery-40/src/errors.xml
  • specifications/xquery-40/src/expressions.xml

PR #2019: 1776: XSLT template rules for maps and array

Pull request #2019 by michaelhkay.

Currently work In progress, committed so that the draft can be reviewed. Changes in three main areas: - Pattern syntax: patterns such as `?item` and `?parent?item` are defined to match items in a map by their key - Built-in template rules for on-no-match="shallow-copy-all". Revisits the built in template rules for this scenario. - General revision of the processing model for xsl:apply-templates applied to a tree of maps and arrays.

Changed files
  • specifications/grammar-40/xpath-grammar.xml
  • specifications/xpath-functions-40/src/function-catalog.xml
  • specifications/xslt-40/src/xslt.xml

PR #2015: 2009 Avoid constructing document node when it makes no sense

Pull request #2015 by michaelhkay.

Fix #2009 The rules for xsl:variable are changed so there is no attempt to construct an implicit temporary tree when the sequence constructor contains an `xsl:map`. `xsl:array`, or `xsl:select` instruction (perhaps mixed with other instructions). Compatibility: note that `xsl:array` and `xsl:select` are new in 4.0, while xsl:map inside `xsl:variable` always throws an error in XSLT 3.0. Justification: - a child `xsl:select` element behaves like a `select` attribute - if the content of xsl:variable is `xsl:map` or `xsl:array` it makes no sense to require the user to add `as=map(*)` or `as=array(*)` because the type is obvious anyway.

Changed files
  • specifications/xslt-40/src/xslt.xml

PR #2011: 675(part): Add XSLT static typing rules for new kinds of XPath expression

Pull request #2011 by michaelhkay.

Updates the static typing rules in XSLT for new kinds of expression introduced in XPath 4.0. These rules are used in streamability analysis, but more work needs to be done to complete the streamability analysis. Production rules are now referenced by name, as production numbers are no longer available.

Changed files
  • specifications/xslt-40/src/xslt.xml

PR #1942: 37 Support sequence, array, and map destructuring declarations

Pull request #1942 by rhdunn.

Closes #37. This currently only supports XPath. I'm working on the wording for XQuery.

Changed files
  • specifications/grammar-40/xpath-grammar.xml
  • specifications/xquery-40/src/expressions.xml

PR #1888: 366 xsl:package-location

Pull request #1888 by Arithmeticus.

First draft, for initial feedback. Notes: - Because the CG has little energy/resources to develop the EXPath Zip module, I have situated the question of archive (compressed or not) in the URI scheme itself. There are dozens of archives, dozens of URI schemes. The only case where I have found overlap is in the `jar:` scheme/archive. Yes, I've seen `zip:` used as an alias for `jar:`, but it's not an official IANA URI scheme. This may need discussion. - I have opted to bind `@priority` to a non-zero integer. This is the first time the constraint for the union of positive and negative integers has been placed on an XSLT attribute, so I may not have correctly set up `element-catalog.xml`. - I have opted to not make attribute values `format`, `name`, and `version` as criteria for the priority package location (new term), so that developers can be warned when the package is at odds with the declaration. To make them criteria would mean that inconsistencies between the declaration and the referenced packages would remain undetected. - I adopted the terms "URL" and "entry" based upon the IANA nomenclature for the jar: scheme. - I may have overthought the distinction between archive and non-archive URIs. Feedback is appreciated. - Error code `3000` has been broken up into different possible errors. - Suggestions on the type and number of tests that need to be written for the test suite are welcome.

Changed files
  • specifications/xslt-40/src/element-catalog.xml
  • specifications/xslt-40/src/xslt.xml

PR #1283: 77b Update expressions

Pull request #1283 by michaelhkay.

This PR is the result of splitting PR #832 into two parts; this part extracts update expressions into a separate proposal, for ease of review.

Changed files
  • specifications/grammar-40/xpath-grammar.xml
  • specifications/xquery-40/src/expressions.xml

PR #1062: 150bis revised proposal for fn:ranks

Pull request #1062 by michaelhkay.

This proposal is an amended/alternative proposal for the fn:ranks function, taking into account the work done on the original issue #150 and the PR #1027 and the comments raised. Acknowledgements to the original author for the idea and for a lot of good work on examples etc. It amends the previous proposal as follows: (a) the signature and the semantics are aligned with fn:sort. This adds some functionality (multiple sort keys, ascending/descending) and also removes some complexity (two different collations for comparing input items and result items) (b) the style of exposition is changed editorially for consistency with other functions

Changed files
  • specifications/xpath-functions-40/src/function-catalog.xml
  • specifications/xpath-functions-40/src/xpath-functions.xml