@qt4cg statuses

This is CG's PR #2864 with the addition of the compiled SCM file.

Closes #2863

Records have changed; they are not extensible anymore, and all fields are required. The corresponding attributes should e removed.

An example:

<fos:record-type id="uri-structure-record" extensible="false">
  <fos:summary>
    <p>This record type represents the components of a URI.</p>
  </fos:summary>
  <fos:field name="uri" type="xs:string?" required="false">

Fix #2861

I think there are a few edge cases that aren't covered by the spec, for example what heppens if a string after Unicode normalization contains the quote or separator character?

I would suggest making it simpler, in the interests of being easier to understand and easier to implement, while not affecting any practical use cases. Put each string through the following steps, in order, each applying to the output of the previous step.

1. Apply character mapping if requested.
2. Apply unicode normalization if requested.
3. Normalize line endings.
4. Apply quoting to strings that (now) contain special characters.

Note: character mapping was originally designed with the primary use case of manually generating XML markup, which is why the XML output method doesn't interfere with strings generated using character mapping. That justification doesn't apply here.

I suggest a new function in the section for "Parsing and building URI". It takes two absolute URIs, and converts one of them to a relative URI with respect to the other URI, if possible.

A usecase could be: Add a reference to an image to a document. The absolute path to the image points to a directory within my document file structure, but i prefer relative references within my document. The new function is related to fn:resolve-uri.

The function takes two URIs called u1 and u2 as input. The result shall be empty, if

• the two URIs differ in scheme and / or host, or
• any of the URIs contain a query and/or fragment part, or
• any of the URIs is not absolute, or
• there is no common prefix in both partportions

Otherwise, the result shall be a relative URI r, so that resolve-uri(r, u1) eq u2 holds.

Examples:

• relative-uri('file:/a/b/c/d','file:/a/b/c/') gives d
• relative-uri(' http://example.com/dir1/dir3/other.html', 'http://example.com/dir1/dir2/page.html') gives ../dir3/other.html
• relative-uri(' http://example.com/dir1/dir3/other.html', 'https://example.com/dir1/dir2/page.html') gives the empty sequence because of different schemes

Greetings, Frank Steimke

Fix #2843

Fix #2853

This resolves the issue as follows:

• In both XSLT and XQuery, the expression defining the default value of a function parameter (for a user-defined function) is evaluated in the same way as the initializing expression of a global variable. We don't constrain the expression, but it has no access to the static or dynamic context of the function caller, and it defines a fixed default that applies to all calls on that function.
• However, as a special case there is provision to define that the context item/value of the caller is used as the default. In XQuery this is done by defining the default using the custom syntax $node as node() := context value. In XSLT we use select="current()".