@qt4cg statuses
This page displays recent status updates about the QT4CG project.
The are also captured in an RSS feed.
By year: 2025, 2024, 2023, 2022, 2021, 2020
QT4 CG meeting 138 draft minutes #minutes—10-14
Draft minutes published.
Issue #2235 closed #closed-2235
XQuery declare function with unprefixed name
Issue #2236 closed #closed-2236
2235 Tweak the rules for default function namespace
Issue #2240 closed #closed-2240
2237 XSLT impact of multiple schemas
Issue #2148 closed #closed-2148
fn:base-uri: Raise errors?
Issue #1718 closed #closed-1718
Ordered Maps: positions in callback functions
Issue #2225 closed #closed-2225
1718 Ordered Maps: positions in callback functions
Issue #2186 closed #closed-2186
Adaptive serialization of JNodes
Issue #2226 closed #closed-2226
2186 Change adaptive serialization of JNodes
Issue #2079 closed #closed-2079
Extend EQName with optional prefix
Issue #2227 closed #closed-2227
2079 Allow optional prefix in EQName syntax
Issue #2012 closed #closed-2012
Add array:sort-with
Issue #2228 closed #closed-2228
2012 Define array:sort-with, revise fn:sort-with
Issue #2232 closed #closed-2232
1935 Errors from doc-available
Issue #1935 closed #closed-1935
doc-available() with invalid options
Issue #2241 closed #closed-2241
The diagram in the Data Model appendix D is missing
Issue #2239 closed #closed-2239
First cut at diagrams for JNodes (completes QT4CG-127-01)
Issue #2231 closed #closed-2231
Updated status section for all documents
Issue #1537 closed #closed-1537
XSLT: local functions within an enclosing xsl:mode
Issue #2244 closed #closed-2244
Fix bibliographic reference
Issue #2250 created #created-2250
Function to detect/infer the string encoding from a binary
A function for detecting/inferring the encoding from an octet sequence may be helpful:
- The encoding can be derived from an initial BOM.
- In addition, implementation-defined heuristics could be used, as e.g. provided by the ICU
CharsetDetector.detectAll
method.
Norm’s proposal for the function signature:
fn:inferred-encoding($data as (xs:hexBinary|xs:base64Binary),
$default-encoding as xs:string? := ()) as xs:string?
We could allow a result sequence and include confidence values in the result.
See the discussion in https://github.com/qt4cg/qtspecs/pull/2222.
Pull request #2249 created #created-2249
2221 fn:unparsed-text: Encoding, BOM handling
Closes #2221
Note that this PR is also a revision of #1950, which I felt was a bit ambiguous, and did not cover all possible cases. I believe that the proposed changes are compatible with 3.1. In particular, it states more clearly what is going to happen if both an implicit encoding is determined (for example, via a BOM), and an explicit encoding is supplied.
Pull request #2248 created #created-2248
2148b XDM Recognize that Base URI property may be invalid
This PR is intended to complement PR #2224 by recognising in the XDM specification that the base URI property of a document or element node may be either a URI, or absent, or invalid.
QT4 CG meeting 138 draft agenda #agenda-10-14
Draft agenda published.
Pull request #2247 created #created-2247
Deferred Evaluation in XPath - the f:generator record
This PR introduces the notion of deferred evaluation and presents the tool to achieve this - the built-in named record type f:generator
.
- Two major use cases are presented.
- The fields of
f:generator
are defined. - All system-provided methods of
f:generator
are defined. - Examples of using each of the methods of
f:generator
are provided. - The formal equivalents of each of the system-provided methods of
f:generator
are provided in a separate appendix.
Pull request #2246 created #created-2246
2233 Expand xsl:analyze-string; introduce fn:regex-groups()
Fix #2233
Issue #2230 closed #closed-2230
2229 Drop map:keys-where()
Issue #2245 created #created-2245
Action QT4CG-116-01: Add a specific error code for unsupported options on doc and doc-available
I’ve reviewed the unassigned action:
QT4CG-116-01: Add a specific error code for unsupported options on doc and doc-available
I believe that it was intended for MK and I don’t believe that it’s been completed.
The action appears to have been to add a specific error code for the case where options are requested on fn:doc
or fn:doc-available
that the processor cannot support. For example, if xinclude
is true()
but the processor is incapable of doing XInclude processing.
I'm creating an issue to track this because it's not entirely clear from the minutes how much consensus there was for this action.
Pull request #2244 created #created-2244
Fix bibliographic reference
I think the bibliographic reference in
<p>The following types, which were originally defined in
<bibref ref="xpath-datamodel-30"/> and were subsequently adopted by
<bibref ref="xmlschema11-2"/>:
<code>xs:anyAtomicType</code>, <code>xs:dayTimeDuration</code>,
<code>xs:yearMonthDuration</code>.
</p>
Really should be to the 3.0 specification, not the current 4.0 specification. I've fixed that, but left in the bibliographic reference to the current spec.
Issue #2243 closed #closed-2243
Build fix to make xspecref and bibliography references relative
See 4596 more statuses in yearly archives.