Saxonica Developer Community

2023-11-30

• 
  Debbie Lockett Saxon

  19:18 · Edited issue

  I'm reopening this bug, as it appears that there is more to do. Validation reports from successful validations are not valid against the schema validation-reports.xsd.
  e.g. the validation report produced when validating books.xml agai... Bug #6086 (In Progress): Is the schema validation-reports.xsd up to date?

  The documentation at https://www.saxonica.com/html/documentation12/schema-processing/commandline.html says:
  > -report:filename
  >
  > This option switches on the capture of validation reporting. Here filename specifies where the valid...
• 
  Debbie Lockett Saxon

  13:02 · Closed issue

  The bug fix was also applied in the Saxon 11.6 maintenance release. Bug leaving bug "resolved" rather than "closed" as the fix has not gone out in a Saxon 10 maintenance release. Bug #5913 (Resolved): Tail recursion overwrites value of variable

  Arising out of a question on Slack on March 7:
  Attached is a zip with test.xsl and test.xspec. The XSLT contains two functions, one of which calls the other, and the second is recursive. The XSpec tests the functions with various inpu...
• 
  Debbie Lockett Saxon

  12:58 · Commented on issue

  The bug fix was also applied in the Saxon 10.9 maintenance release (2023-02-16). Bug #5727: Xqueries with Domino do not work with a document having non namespace aware attributes

  Xquery outputing a complex element does not work with domino, if xml has any attribute that is not namespace aware or its created with a document builder that’s not namespace aware. This seems to be because Node.getlocalName() does not h...
• 
  Debbie Lockett Saxon

  12:51 · Closed issue

  Leave as "resolved" rather than "closed" as fix has not gone out in a Saxon 10 maintenance release. Bug #5951 (Resolved): XQuery with DOMResult - empty prefixed namespace bindings added to children elements

  Hello,
  From Saxon 10 I have failing tests for XQuery transformations that deal with elements without namespace attribute. Such elements can inherit their parent namespace prefix and the namespace binding is reassigned the empty value....
• 
  Debbie Lockett Saxon

  12:50 · Closed issue

  Leave as "resolved" rather than "closed" as fix has not gone out in a Saxon 10 maintenance release. Bug #6146 (Resolved): relative URI resolution in XQuery vs XSLT when loading (XQuery/XSLT) code from the command line over HTTP(S)

  Using SaxonJ HE 12.3, I found that the `net.sf.saxon.Transform`, when taking the `-xsl` option as a HTTP(S) URL, resolves relative URIs in the XSLT code relative to the loaded XSLT stylesheet so e.g.
  ```
  java -cp 'C:\Program Files\Sa...
• 
  Debbie Lockett Saxon

  12:50 · Closed issue

  Leave as "resolved" rather than "closed" as fix has not gone out in a Saxon 10 maintenance release. Bug #6147 (Resolved): Incorrect fingerprint for XML_SPACE_TYPE

  In StandardNames.java, the fingerprint for `XML_SPACE_TYPE` is set to 6, when it should be `XML + 6`.
  The bug is asymptomatic because, by chance, we don't use the fingerprint 6 for anything else.
• 
  Debbie Lockett Saxon

  12:50 · Closed issue

  Leave as "resolved" rather than "closed" as fix has not gone out in a Saxon 10 maintenance release. Bug #6153 (Resolved): XSD blockDefault effect on complex types

  It seems that when a complex type has no `@block` attribute, we (correctly) look at the `@blockDefault` on the containing `xs:schema`, and then (incorrectly) use the value to set the `final` property rather than the `block` (aka `{prohib...

2023-11-29

• 
  Debbie Lockett Saxon

  19:38 · Closed issue

  Marking closed: Saxon 11 documentation already fixed, this was just waiting for the Saxon 12.4 release for the Saxon 12 documentation update. Bug #6204 (Closed): Documentation: EXSLT links are dead

  In the function library documentation, links to EXSLT functions point to the original web site at exslt.org which is now defunct. The specifications can now be found at http://exslt.github.io
• 
  Debbie Lockett Saxon

  18:33 · Closed issue

  I believe all issues have been resolved now. Bug #6202 (Resolved): Invalid attribute names in configuration files are ignored

  Unless you validate your configuration file against the published schema (which most users are unlikely to do), incorrectly-spelled attribute names (in the global section and other similar sections) will go undetected.
  The code iterat...

2023-11-22

• 
  Debbie Lockett Saxon

  14:09 · Commented on issue

  Updates committed to FeatureKeysToConfigFile.xsl, and testing for generated configuration files now added in `run-samples.gradle` - see the `run_config_tests` task (which is added as a dependency for `run_config_samples`, so we will at l... Bug #6202: Invalid attribute names in configuration files are ignored

  Unless you validate your configuration file against the published schema (which most users are unlikely to do), incorrectly-spelled attribute names (in the global section and other similar sections) will go undetected.
  The code iterat...