Re: RDF tests errata

* Eric Prud'hommeaux <eric@w3.org> [2015-07-19 10:45-0400]
> * Eric Prud'hommeaux <eric@w3.org> [2015-07-19 10:17-0400]
> > I'm aware of two errata and a good idea for the RDF1.1 Turtle tests:
> > 
> > 1: invalid character is positive syntax test.
> >   http://www.w3.org/2013/TurtleTests/localName_with_assigned_nfc_PN_CHARS_BASE_character_boundaries.ttl
> > 
> >   Pierre-Antoine noted that the last character is \UE01EF while
> >   <http://tools.ietf.org/html/rfc3987#section-2.2> has:
> >     ucschar        = %xA0-D7FF / %xF900-FDCF / %xFDF0-FFEF
> >                    / %x10000-1FFFD / %x20000-2FFFD / %x30000-3FFFD
> >                    / %x40000-4FFFD / %x50000-5FFFD / %x60000-6FFFD
> >                    / %x70000-7FFFD / %x80000-8FFFD / %x90000-9FFFD
> >                    / %xA0000-AFFFD / %xB0000-BFFFD / %xC0000-CFFFD
> >                    / %xD0000-DFFFD / %xE1000-EFFFD
> > 
> >   The top of this range is unassigned per
> >     <http://www.unicode.org/charts/PDF/UEFF80.pdf>
> >   The last assigned character is VARIATION SELECTOR-256 per
> >     <http://www.unicode.org/charts/PDF/UE0100.pdf>
> >   but that's awkardly in between %xDFFFD and %xE1000.
> >   The last assigned ucschar appears to be U2FA1D per
> >     <http://www.unicode.org/charts/PDF/U2F800.pdf>
> > 
> >   We can change the last character to the end of ucschar UEFFFD
> >   (currently unassigned) or more conservatively, U2FA1D, which
> >   lops off most of ucschar but still tests ranges outside of BMP1.
> > 
> >   Opinions?
> > 
> > 
> > 2: missing prefixes in two negative syntax tests:
> >   http://www.w3.org/2013/TurtleTests/turtle-syntax-bad-missing-ns-dot-start.ttl
> >   http://www.w3.org/2013/TurtleTests/turtle-syntax-bad-missing-ns-dot-end.ttl
> > 
> >   If the implementation doesn't fail on the intended error, it will
> >   fail on the missing prefix.

Propose to replace these two with four tests:

turtle-syntax-bad-PNAME_NS-undeclared-begin [[
  # PN_PREFIX with undeclared FULL STOP in first character
  PREFIX valid: <http://www.w3.org/2013/TurtleTests/valid#>
  PREFIX invalid: <http://www.w3.org/2013/TurtleTests/invalid#>
  
  valid:s valid:p .invalid:o .
]]

turtle-syntax-bad-PNAME_NS-undeclared-end [[
  # PN_PREFIX with undeclared FULL STOP in last character
  PREFIX valid: <http://www.w3.org/2013/TurtleTests/valid#>
  PREFIX invalid: <http://www.w3.org/2013/TurtleTests/invalid#>
  
  valid:s valid:p invalid.:o .
]]

turtle-syntax-bad-PNAME_NS-declared-begin [[
  # PN_PREFIX with undeclared FULL STOP in first character
  PREFIX valid: <http://www.w3.org/2013/TurtleTests/valid#>
  PREFIX .invalid: <http://www.w3.org/2013/TurtleTests/invalid#>
  
  valid:s valid:p .invalid:o .
]]

turtle-syntax-bad-PNAME_NS-declared-end [[
  # PN_PREFIX with undeclared FULL STOP in last character
  PREFIX valid: <http://www.w3.org/2013/TurtleTests/valid#>
  PREFIX invalid.: <http://www.w3.org/2013/TurtleTests/invalid#>
  
  valid:s valid:p invalid.:o .
]]


> > 3: rename negative syntax tests to .err.
> >   http://www.w3.org/2013/TurtleTests/turtle-syntax-bad-*.ttl
> > 
> >   They aren't really turtle files, which becomes clear when you try to
> >   look at them in a browser which cares about that stuff.
> 
> 4: wrong comment on path or dot test:
>   http://www.w3.org/2013/TurtleTests/turtle-syntax-bad-n3-extras-06.ttl
> 
>   says # = is not Turtle which is tested in turtle-syntax-bad-n3-extras-02.ttl
>   turtle-syntax-bad-n3-extras-03.ttl covers N3 dot paths with whitespace.

5: redundant @keywords tests
  http://www.w3.org/2013/TurtleTests/turtle-syntax-bad-n3-extras-08.ttl
  http://www.w3.org/2013/TurtleTests/turtle-syntax-bad-n3-extras-13.ttl

  are redundant against turtle-syntax-bad-n3-extras-07.ttl


> > The plan:
> > 
> >   Per consensus in an INK Domain call, W3C would like to move tests
> >   and implementation reports to github (via a redirect on W3C so we
> >   aren't stuck there). I propose to fix these errata when we get
> >   around to the move. In the mean time, let's gather errata in this
> >   thread for easy tracking.

We can also proxy the implementation reports from the same github repo.

Issues:

  We lose control over media types unless we proxy everything (which I
  guess we can do).


> > -- 
> > -ericP
> > 
> > office: +1.617.599.3509
> > mobile: +33.6.80.80.35.59
> > 
> > (eric@w3.org)
> > Feel free to forward this message to any list for any purpose other than
> > email address distribution.
> > 
> > There are subtle nuances encoded in font variation and clever layout
> > which can only be seen by printing this message on high-clay paper.
> > 
> 
> -- 
> -ericP
> 
> office: +1.617.599.3509
> mobile: +33.6.80.80.35.59
> 
> (eric@w3.org)
> Feel free to forward this message to any list for any purpose other than
> email address distribution.
> 
> There are subtle nuances encoded in font variation and clever layout
> which can only be seen by printing this message on high-clay paper.
> 

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.

Received on Sunday, 19 July 2015 15:18:54 UTC