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:
#2006
#2001
#1999
#1998
#1991
#1984
#1959
#1942
#1894
#1888
#1883
#1283
#1062

Pull requests in descending order

PR #2001: 1085 Revert fn:sort to the 3.1 spec; introduce fn:sort-by

Pull request #2001 by michaelhkay.

Fix #1085 The new functionality introduced into the 4.0 version of fn:sort is repackaged into a new function fn:sort-by with a much cleaner interface; the fn:sort function reverts to its 3.1 specification. If this PR attracts support then the corresponding change will be applied to the array:sort function.

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

PR #1991: 835 Add built-in named record types to static context

Pull request #1991 by michaelhkay.

This PR adds six built-in named record types to the static context of every application: Record [key-value-pair] Record [load-xquery-module-record] Record [parsed-csv-structure-record] Record [random-number-generator-record] Record [schema-type-record] Record [uri-structure-record] These are now listed in Appendix C of F&O Issue 835 requests a review of the names of these records; perhaps putting them in one place will make that review easier. Personally, I am happy with the names as currently defined.

Changed files
  • specifications/xpath-functions-40/src/xpath-functions.xml
  • specifications/xpath-functions-40/style/merge-function-specs.xsl
  • specifications/xquery-40/src/expressions.xml

PR #1984: 882 Drop fn:chain

Pull request #1984 by michaelhkay.

Fix #882 Supersedes PR #1883 There has been a great deal of discussion about the relative merits of the status-quo fn:chain function and the proposed replacement fn:compose. The CG was polled on whether it preferred to have fn:chain only, fn:compose only, or both, or neither. There was no clear consensus. The only option which no-one seemed to favour was to have fn:chain only -- which is the status quo. Since no-one is happy with the status quo I am therefore proposing that we drop this function. We can then start with a clean slate. For the record the main criticisms of the fn:chain function as currently specified were: (a) it is more useful to have a function that combines several functions into a single function, without actually applying that function to a set of supplied arguments (b) The function has special-case behaviour for arrays (if the input is not an array and the function has arity > 1 then the input sequence is converted to an array). (c) The need for the function is not clearly motivated; the examples given can all be achieved in some simpler more intuitive way.

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

PR #1959: 1953 (part) XSLT Worked example using methods to implement atomic sets

Pull request #1959 by michaelhkay.

Provides an XSLT package that uses named record types and methods to implement an atomic set data type, as an example of how abstract data types can now be implemented.

Changed files
  • specifications/xslt-40/src/element-catalog.xml
  • specifications/xslt-40/src/schema-for-xslt40.xsd
  • 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 #1883: 882 Replace fn:chain by fn:compose

Pull request #1883 by michaelhkay.

Drops the existing fn:chain function and replaces it with a new fn:compose function. This combines two separate changes: (a) whereas fn:chain applies a sequence of functions to an input, fn:compose returns a composite function that can be used repeatedly with different inputs. (b) the fn:compose function is restricted to arity-1 functions, which leads to a much simpler specification that still handles the vast majority of practical use cases. In particular, note that if the sequence of functions to be applied is statically known, then it can always be written out explicitly; the real use case for this function is when the sequence of functions is constructed dynamically. And in this situation, fn:chain in its current form can easily fail because of problems with the arity of the functions included in the chain.

Changed files
  • specifications/xpath-functions-40/src/function-catalog.xml
  • specifications/xpath-functions-40/src/xpath-functions.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