- From: Antoine Zimmermann <antoine.zimmermann@emse.fr>
- Date: Tue, 07 May 2013 11:37:56 +0200
- To: public-rdf-wg@w3.org
Le 07/05/2013 11:17, Andy Seaborne a écrit : > > > On 07/05/13 09:09, Antoine Zimmermann wrote: >> Le 07/05/2013 09:26, Andy Seaborne a écrit : > >>>>> >>>>> Anything else is not a language-tagged string. >>>>> So, it's answer 1. >>> >>> By that argument "@en-US" is a syntax error yet it is the canonical >>> form. >> >> In the abstract syntax "@en-US" would be strongly wrong because of the @ >> character. > > I was using that to indicate a language tag, not that it is part of the > language tag. > >> It does not need be a syntax error in Turtle, but it's an >> error in RDF/XML > > You are saying that xml:lang="en-US" is an *error* in RDF/XML? No, with the @ it would be an error. > > See sec 2.7, Example 8 of the RDF/XML spec and the links to the example8 > files. > > and it links to > http://www.w3.org/TR/REC-xml/#sec-lang-tag > >> or JSON-LD. > > All I can see is "Languages codes are defined in [BCP47]." Link please. Same, I was talking about the @ version of the tag. Each syntax has its own way of indicating a language tag, even allowing upper case, but this does not mean that a language tag in the abstract syntax has to allow all forms existing in concrete syntaxes. > >> One could imagine a syntax where en-US is a >> syntax error. > > A parser produces a graph. The Turtle spec (sec 7) does not say > anything about changing the characters of LANGTAG. > > Let's conduct a survey: > > How many existing systems treat this > > --------------- > <http://example/s> <http://example/p> "xyz"@en . > <http://example/s> <http://example/p> "xyz"@EN . > --------------- > as one triple or as two triples aside from whether they treat the graphs > as equivalent. Well, what does the N-triples spec says? I would like it to say that "xyz"@en and "xyz"@EN both correspond to the language-tagged string that has "en" as its language tag. The other solution is to do what you just proposed in your recent emails, which is to distinguish between equality and equivalence of language tags in Concepts, and reflect the change in the other documents. I prefer keeping the concepts as they are and adding a sentence to the concrete syntaxes, to clarify that what they do allow isn't contradicting concepts. -- Antoine Zimmermann ISCOD / LSTI - Institut Henri Fayol École Nationale Supérieure des Mines de Saint-Étienne 158 cours Fauriel 42023 Saint-Étienne Cedex 2 France Tél:+33(0)4 77 42 66 03 Fax:+33(0)4 77 42 66 66 http://zimmer.aprilfoolsreview.com/
Received on Tuesday, 7 May 2013 09:38:20 UTC