Updates Turtle tests to use triple term syntax and reifications

[gkellogg]

… instead of quoted triples.

[niklasl]

I think these are the required updates for the new reifier naming syntax.

[pchampin]

This was discussed during the rdf-star meeting on 2024-08-29:
https://www.w3.org/2024/08/29-rdf-star-minutes.html#t04

[pchampin]

This was discussed during the rdf-star meeting on 12 September 2024.

View the transcript

w3c/rdf-tests#135

gkellogg: first one has been open for a bit. new tests for updated turtle.
… need even more on that.
… waiting for someone else to have an implementation.
… AndyS is working on updates to his parser. Hopefully we can get an approval after that.

AndyS: about at the stage where I can run those tests.

ora: so not to merge yet?

gkellogg: yeah, let's wait until someone else is passing the tests.

---

[afs]

N-triples tests:

ntriples-base* - "base" is a confusing name, especially when copied to nt-ttl-base, because they are not about BASE.
Suggestions: ntriples-langdir named after the terminal or ntriples-textdir.

ntriples-star-bad-reifier-1 tests reifier in the subject position.
ntriples-star-bad-reifier-2 tests reifier in the object position.
ntriples-star-bad-reifier-3 tests both subject and object - was a test of the predicate position intended?

ntriples-star-bad-reifier-4 is unclear. Maybe its testing declaration but it's hard to tell. Simplify to:
<< <http://example/s> <http://example/p> <http://example/o> >> .

ntriples-star-syntax-03 and ntriples-star-syntax-04 are the same.

ntriples-star-nested-bad-annotated-syntax-*.nt don't add much over ntriples-star-bnode-bad-annotated-syntax*.nt because the failure expected is at the first {|.

[gkellogg]

N-triples tests:

ntriples-base* - "base" is a confusing name, especially when copied to nt-ttl-base, because they are not about BASE. Suggestions: ntriples-langdir named after the terminal or ntriples-textdir.

I renamed these all as you suggested.

ntriples-star-bad-reifier-1 tests reifier in the subject position. ntriples-star-bad-reifier-2 tests reifier in the object position. ntriples-star-bad-reifier-3 tests both subject and object - was a test of the predicate position intended?

``ntriples-star-bad-reifier-4 is unclear. Maybe it's testing declaration but it's hard to tell. Simplify to: `<< http://example/s http://example/p http://example/o >> .`

I wasn't able to find these tests in the repository; there are likely some additional tests that would be required. Can you point me to them?

ntriples-star-syntax-03 and ntriples-star-syntax-04 are the same.

ntriples-star-syntax-04 was an old file, and unreferenced; I removed it.

ntriples-star-nested-bad-annotated-syntax-*.nt don't add much over ntriples-star-bnode-bad-annotated-syntax*.nt because the failure expected is at the first {|.

True, if we were to consolidate, which set should remain?

[afs]

I wasn't able to find these tests in the repository; there are likely some additional tests that would be required. Can you point me to them?

rdf/rdf12/rdf-n-triples/syntax/ntriples-star-bad-reifier-syntax-*.nt

ntriples-star-nested-bad-annotated-syntax-*.nt don't add much over ntriples-star-bnode-bad-annotated-syntax*.nt because the failure expected is at the first {|.

True, if we were to consolidate, which set should remain?

The simpler ntriples-star-bnode-bad-annotated-syntax*.nt. Annotations aren't in N-triples.

[gkellogg]

rdf/rdf12/rdf-n-triples/syntax/ntriples-star-bad-reifier-syntax-*.nt

I didn't see it because the name is slightly different: rdf/rdf12/rdf-n-triples/syntax/ntriples-star-bad-reified-syntax-*.nt. I'll take care of your suggestion.

[gkellogg]

This will still need updates for further grammar branches and to reconcile w3c/rdf-turtle#70.

[TallTed]

separators should be space-emdash-space (or space-double hyphen-space), not space-hyphen-space.

[TallTed]

Suggested change

	<span about='../syntax#ntriples-langdir-bad-1' property='mf:name'>N-Triples literal- Bad - undefined base direction</span>
	<span about='../syntax#ntriples-langdir-bad-1' property='mf:name'>N-Triples literal — Bad — undefined base direction</span>

[TallTed]

Suggested change

	<span about='../syntax#ntriples-star-bad-reified-4' property='mf:name'>N-Triples-star - Bad - predicate reified triple</span>
	<span about='../syntax#ntriples-star-bad-reified-4' property='mf:name'>N-Triples-star — Bad — predicate reified triple</span>

[TallTed]

Suggested change

	<span about='../syntax#ntriples-langdir-bad-2' property='mf:name'>N-Triples literal- Bad - upper case LTR</span>
	<span about='../syntax#ntriples-langdir-bad-2' property='mf:name'>N-Triples literal — Bad — upper case LTR</span>

[TallTed]

Suggested change

	mf:name "N-Triples-star - Bad - predicate reified triple" ;
	mf:name "N-Triples-star — Bad — predicate reified triple" ;

[afs]

This is the way the tests (all three generations) are. Developers use hyphen.
Keep it simple in the manifest because of viewing with the wrong character set.

The rest is automatically produced.

(FYI: Chicago style guide prefers no spaces around em-dashes, which then looks bad in this context.)

[TallTed]

As I recall, Chicago style guide paradoxically and frustratingly says to put no spaces around em-dashes, but does put spaces around em-dashes. (Certainly multiple style guides do this.)