Re: ACTION A-645-07: schema for serialization parameters

On Jun 21, 2016, at 5:24 AM, Abel Braaksma wrote:
> ...
> I'm curious, where did you see the production *without* the ws:explicit? Because in XPath 3.0, 3.1 public CR and 3.1 internal CR I see the following production rules (under section A.2.1 Terminal Symbols, the inline rules in the body of the text do not carry the ws:explicit comments, which is perhaps a bit unfortunate):
> 
> [117]   	URIQualifiedName	   ::=   	BracedURILiteral NCName 	/* ws: explicit */
> [118]   	BracedURILiteral	   ::=   	"Q" "{" [^{}]* "}"	/* ws: explicit */
> 
> In other words, whitespace is prohibited for this production.


Correction accepted; revised schema is attached.  This changes the 
characterization of the last several examples in the test file; they no 
longer become valid, but stay invalid.


  <!--* Was invalid, stays invalid after all (whitespace in the EQName) *-->
  <s:method xml:id="method-i-v-EQ1" value="Q{ http://example.com/nss/foo } bar"/>
  <s:method xml:id="method-i-v-EQ2" value="Q { http://example.com/nss/foo }bar"/>
  <s:method xml:id="method-i-v-EQ3" value="Q { http://example.com/nss/foo } bar"/>
  
  <s:json-node-output-method xml:id="json-i-v-EQ1" value="Q{http://example.com/nss/foo} bar"/>
  <s:json-node-output-method xml:id="json-i-v-EQ1" value="Q {http://example.com/nss/foo}bar"/>
  <s:json-node-output-method xml:id="json-i-v-EQ1" value="Q {http://example.com/nss/foo} bar"/>

 
-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************