You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[@TallTed] When talking about reifiers in text, we must distinguish between the "optional iri production or BlankNode production" and the tilde that precedes them, because when we later want to talk about the reifier, we will mean only the iri production or the BlankNode production; we will not mean the ~plus the iri production or BlankNode production.
...And we should distinguish between the angle brackets < > or parentheses ( ) or even just spaces in which we wrap an IRI, and the IRI itself; i.e., <http://example.com/> is not an IRI — it's an < >-wrapped (or < >-delimited) IRI — the IRI is just http://example.com/, around which we often put some (optional!) wrapper (or delimiter) to make it more human-friendly, as it is thus more visibly distinct from the text in which it appears. This is entirely distinct from and unlike the required~ in triple reification, which is as much (if not more) for the machine as it is for the human, as we have made it a mandatory separator between the object and the reifier.
[@gkellogg] Please consider creating an issue on Turtle for these points. I don't think I agree with your reasoning, as other productions such as IRIREF and LANG_DIR (and many others) include delimiters which are not part of the semantic entity.
The text was updated successfully, but these errors were encountered:
There are many places in the grammar where the term coming out of the syntax includes delimiters. I don't see why the tilde in reifier is any different from the @ in LANG_DIR or < > in IRIREF.
Originally posted by @TallTed and @gkellogg in w3c/rdf-concepts#98 (comment)
The text was updated successfully, but these errors were encountered: