@qt4cg statuses

This page displays recent status updates about the QT4CG project.

The are also captured in an RSS feed.

By year: 2026, 2025, 2024, 2023, 2022, 2021, 2020

QT4 CG meeting 154 draft minutes #minutes-03-03

03 Mar at 17:45:00 GMT

Draft minutes published.

Issue #1479 closed #closed-1479

03 Mar at 17:27:35 GMT

Default element namespace in XQuery: interaction of 'fixed' and '##any'

Issue #2483 closed #closed-2483

03 Mar at 17:27:34 GMT

1479 XQuery: Default Namespace Clarifications

Issue #2484 closed #closed-2484

03 Mar at 17:25:33 GMT

Subtyping: node() vs (doc() | elem() | att() | text() | comment() | pi() | ns())

Issue #2491 closed #closed-2491

03 Mar at 17:25:32 GMT

2484 Subtyping: abstract types vs choice types

Issue #2052 closed #closed-2052

03 Mar at 17:23:40 GMT

fn:collation-available: $usage

Issue #2492 closed #closed-2492

03 Mar at 17:23:39 GMT

2052 fn:collation-available: $usage

Issue #2497 created #created-2497

03 Mar at 17:22:55 GMT
JNodes diagrams: selector → jkey, content → jvalue

Two JNode diagrams need to be updated after my changes in #2490: selector must be renamed to jkey, content/position/parent to jvalue/jposition/jparent (or we skip the leading j’s).

@ndw I can update the svg and n3 manually, unless you have an automated way to do this…

Issue #272 closed #closed-272

03 Mar at 17:21:29 GMT

Setting parameter values in xsl:use-package

Issue #2474 closed #closed-2474

03 Mar at 17:21:28 GMT

272 Allow xsl:use-package to set parameters

Issue #2472 closed #closed-2472

03 Mar at 17:21:12 GMT

XSLT: "Potential visibility"

Issue #2479 closed #closed-2479

03 Mar at 17:21:11 GMT

2472 drop the term "potential visibility"

Issue #2466 closed #closed-2466

03 Mar at 17:19:30 GMT

format-number() precision

Issue #2469 closed #closed-2469

03 Mar at 17:19:29 GMT

2466 Adapt rules of format-number to new comparison rules

Issue #2465 closed #closed-2465

03 Mar at 17:17:28 GMT

Error description of FODC0006 should be more generic

Issue #2480 closed #closed-2480

03 Mar at 17:17:27 GMT

2465 Improve description of FODC0006

Issue #1702 closed #closed-1702

03 Mar at 17:16:36 GMT

Node Updates: Functions

Issue #1506 closed #closed-1506

03 Mar at 17:16:28 GMT

Type declarations: Constructor functions?

Issue #1251 closed #closed-1251

03 Mar at 17:16:22 GMT

Allow sequence constructor in extension instructions that are implemented with named templates

Issue #1225 closed #closed-1225

03 Mar at 17:16:09 GMT

Generalization of Deep Updates

Issue #2018 closed #closed-2018

03 Mar at 17:16:02 GMT

Type-checking the result of xsl:apply-templates

Issue #1045 closed #closed-1045

03 Mar at 17:15:54 GMT

Functions to manage namespace usage

Issue #641 closed #closed-641

03 Mar at 17:15:43 GMT

Serialization fallback

Issue #2388 closed #closed-2388

03 Mar at 17:15:13 GMT

Adaptive Serialization: function items

Issue #2485 closed #closed-2485

03 Mar at 17:15:12 GMT

2388 Adaptive serialization of anonymous functions

Issue #2493 closed #closed-2493

03 Mar at 17:12:54 GMT

2408 Misc editorial corrections

Issue #2496 created #created-2496

28 Feb at 08:02:34 GMT
EBV: maps, arrays, QNames

One of my favorite topics (sorry for being persistent): I would like to update EBV slightly to reflect the semantics and usage patterns of current versions of the language.

Currently, an EBV can be computed if $data is an XML or JNode, so you can do…

  • $node[.]
  • boolean($map-or-array/.)
  • if($xnode1 and $xnode2) then ...
  • if($map | $array) then ...

…but you cannot do…

  • $map-or-array[.]
  • boolean($map-or-array)
  • if($map1 and $map2) then ...

I think it would be much more intuitive to directly allow boolean($map-or-array) and to return true if the map or array exists.

Similarly, I cannot see boolean($qname) causing any trouble.

Issue #2495 closed #closed-2495

27 Feb at 09:27:07 GMT

Fix whitespace changes; (attempt to) improve long type signatures

Issue #2494 closed #closed-2494

27 Feb at 09:27:07 GMT

XQFO: Whitespace in function signatures

Pull request #2495 created #created-2495

27 Feb at 09:26:58 GMT
Fix whitespace changes; (attempt to) improve long type signatures

Fix #2494

The whitespace issue turned out to be in the CSS not related to fos.scm directly. I fixed it, but it's not clear what changed. Keep your eyes open for code elements that look like they have extra or missing whitespace!

With this PR, we get:

image

See 5126 more statuses in yearly archives.