Michael Kay
- Login: mike
- Email: mike@saxonica.com
- Registered on: 2012-02-01
- Last connection: 2025-01-25
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 28 | 2681 | 2709 |
| Reported issues | 21 | 1787 | 1808 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Saxon | Manager, Developer, Reporter | 2012-02-06 |
| Non-Conformances | Manager | 2020-02-26 |
| Saxon-CE | Manager, Developer | 2012-02-01 |
| SaxonC | Manager, Reporter | 2016-02-24 |
| SaxonJS | Manager | 2016-07-28 |
| SaxonMirrorHE | Manager, Developer | 2021-02-02 |
| W3C QT Specifications | Manager | 2019-05-16 |
Activity
2025-01-25
-
`xsl:document` was using push mode when non-validating, but I have now changed it to do so also when validating.` Bug #6669: Validated result with mixed content is indentedOn Slack I found that Saxon (EE 12.5) indents the output of the following XSLT 3 using schema-aware processing:
```xslt
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"
xmlns:xsd="http://www.w3.org/20... -
Created xslt40 test case output-0729 (though this isn't specific to XSLT 4).· Commented on issue
Test passes with this change.
But I still want to explore: why is the xsl:document instruction evaluated in pull mode, rather than pushing output straight... -
I think the problem is at UncommittedSerializer line 207, where it does· Commented on issue
```
((NodeInfo) item).copy(this, CopyOptions.ALL_NAMESPACES, locationId);
```
The second argument should set the option `CopyOptions.TYPE_ANNOTATIONS`. Failure to... -
The problem goes away if you specify `method="xml"` on the xsl:output declaration.· Commented on issue
Because there is no explicit method, the serialization pipeline has to include an extra step (called an `UncommittedSerializer`) which decides what met... -
It seems the problem here is not with the serialization, but with the validation: the outermost element is entering the serialization pipeline with a type annotation of `xs:untyped`.· Commented on issue
There seem to be two things going on here. Firstly, t...
2025-01-23
-
An added note: my memory on this is a bit hazy, but I seem to remember that the original motivation for treating the XLink namespace specially was an application in which different parts of the application attempted to load incompatible ... Bug #6665: Saxon 10 -> 12 migration xsd import issueHello,
We're trying to upgrade from saxon ee 10.6 to saxon ee 12.5. We have a schema that we import via
processor.getSchemaManager().load(new StreamSource(getResource("/path/to/our.xsd")).toString)
While in saxon 10.6 everythi...
2025-01-22
-
Here is the response that I sent by email:
This appears to be a continuation of the thread at https://saxonica.plan.io/issues/5652
The conclusion of that thread, from a quick reading, was that in order to load a non-standard vers... Bug #6665: Saxon 10 -> 12 migration xsd import issueHello,
We're trying to upgrade from saxon ee 10.6 to saxon ee 12.5. We have a schema that we import via
processor.getSchemaManager().load(new StreamSource(getResource("/path/to/our.xsd")).toString)
While in saxon 10.6 everythi... -
Well, the spec says
> If there is a head element, and the include-content-type parameter has the value true, the HTML output method must add a meta element as the first child element of the head element specifying the character encoding... Bug #6664: The include-content-type flag is ignored if the document has no headI haven't tried to read through the serialization spec with great care, I'm just recording the observation. If you serialize `<html><body><p>test</p></body></html>` as HTML with the `include-content-type` property set to `yes`, no conten...
2025-01-21
-
The `register()` call to register the function (VendorFunctionSetPE line 300) gives the argument type as `node()?`, but the function implementation isn't checking for an empty sequence being supplied.`
The documentation at https://www.s... Bug #6662: java.lang.NullPointerException found for saxon:line-numberGiven this simple XML document:
``` xml
<root>
<item>a</item>
<item>b</item>
<item>c</item>
</root>
```
If I run the below command which is an incorrect path in the XML doc:
```
-qs:"saxon:line-number((//item1... -
I'm pretty sure you're right that this shouldn't happen.
However, it's not easy to find in the spec.
The rule that says this is treated as if there were multiple template rules is in ยง6.5:
> If the top-level pattern is a UnionExprP co... Bug #6663: Ambiguous template match reported for a single templateHi, folks!
I will take the time to try and distill a test file for this from a very large code base, unless I am the bug in my understanding and you tell me just to fix my code.
My understanding is that a single template rule with ...
Also available in: Atom
.