https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2023-04-13T09:04:53ZSaxonica Developer CommunitySaxonJS - Bug #5974: SaxonJS documentation does not address namespaceshttps://saxonica.plan.io/issues/5974?journal_id=235232023-04-13T09:04:53ZJohn Lumleyjohn@saxonica.com
<ul></ul><p>Joel,</p>
<p>The key is given in the documentation for <em>Compiling stylesheets using Saxon-EE</em> <a href="https://www.saxonica.com/saxon-js/documentation2/index.html#!starting/export/compiling-using-XJ" class="external">https://www.saxonica.com/saxon-js/documentation2/index.html#!starting/export/compiling-using-XJ</a>
where a SEF is exported using the <code>-ns:##html5</code> command line option:</p>
<ul>
<li>
<code>-ns:##html5</code> declares that an unprefixed element name will match either a name in the XHTML namespace, or a name in no namespace. This is to ensure that the resulting behavior is close to that defined by the special rules in the HTML5 specification for XSLT and XPath running against an HTML5 DOM. This command line option is new in Saxon 10, and its use is necessary for SEFs which are to be run under SaxonJS 2 in the browser.</li>
</ul>
<p>I pretty much always use this.</p>
<p>I'll leave Debbie or Norm to decide on any documentation changes and move this issue to the Saxon-JS project.</p> SaxonJS - Bug #5974: SaxonJS documentation does not address namespaceshttps://saxonica.plan.io/issues/5974?journal_id=235252023-04-13T09:17:24ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Project</strong> changed from <i>Saxon</i> to <i>SaxonJS</i></li><li><strong>Category</strong> set to <i>Documentation</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li></ul><p>There is also further in depth explanation about the use of the <code>-ns</code> option at <a href="https://www.saxonica.com/saxon-js/documentation2/index.html#!xdm/nodes" class="external">https://www.saxonica.com/saxon-js/documentation2/index.html#!xdm/nodes</a>, which you might find useful.</p>
<p>But you are definitely right that we could improve the documentation on this issue, this is indeed something that frequently trips people up (probably everyone?!).</p>
<p>Adding a FAQ section is a good idea, and it seems like adding some more warnings/pointers about this (e.g. from the pages you mentioned) would be useful.</p> SaxonJS - Bug #5974: SaxonJS documentation does not address namespaceshttps://saxonica.plan.io/issues/5974?journal_id=235312023-04-13T15:35:06ZJoel Kalvesmaki
<ul></ul><p>Thanks John and Debbie for the extra pointers, which I hadn't known about.</p>
<p>When I work with a new technology, I tend to go straight for the examples, and then, as needed, visit other parts of the documentation. Any annotations proximate to, or within, those examples are key for orientation.</p>
<p>Such a great technology. I hope it gets widely adopted!</p> SaxonJS - Bug #5974: SaxonJS documentation does not address namespaceshttps://saxonica.plan.io/issues/5974?journal_id=248662023-10-12T16:58:24ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>Debbie Lockett</i></li><li><strong>Applies to JS Branch</strong> <i>2, Trunk</i> added</li><li><strong>Fix Committed on JS Branch</strong> <i>2, Trunk</i> added</li></ul><p>Documentation updates committed. SaxonJS 2 documentation online will be updated with the 2.6 maintenance release.</p> SaxonJS - Bug #5974: SaxonJS documentation does not address namespaceshttps://saxonica.plan.io/issues/5974?journal_id=248802023-10-13T14:22:29ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Fixed in JS Release</strong> set to <i>SaxonJS 2.6</i></li></ul><p>Bug fix applied in the SaxonJS 2.6 maintenance release.</p>