I18n comments on SPARQL

Version reviewed

http://www.w3.org/TR/2007/WD-rdf-sparql-query-20070326/

Lead reviewer

Felix Sasaki

Notes

These are comments on behalf of the I18N Core WG, unless otherwise stated. The "Followup" column indicates who has been assigned the responsibility of tracking discussions on a given comment.

We recommend that responses to the comments in this table use a separate email for each point. This makes it far easier to track threads.

Comments

ID	Location	Subject	Comment	Followup	Ed. / Subs.
1	Sec. 2.3.1	Adding a reference to BCP47	This section should mention that language tags are defined in BCP47 ("Best Common Practice 47"). There should be a normative reference to BCP47 following the pattern at http://www.w3.org/TR/2007/REC-its-20070403/#bcp47.	FS	S
2	Sec. 2.3.1	Renaming Section on "Matching Language Tags"	The section title Matching Language Tags implies matching against language ranges, see comment 3 at http://www.w3.org/International/reviews/0704-sparql/. However, sec. 2.3.1 does not describe sub tag matching, but only identity of a language tag and given data. Rename proposal: Matching the Identity of Language Tags.	FS	S
3	Sec. 11.4.12	Modification in description of langMatches operator	We propose to replace the second sentence in the first paragraph: RFC4647 defines a case-insensitive, hierarchical matching algorithm which operates on ISO-defined subtags for language and country codes, and user defined subtags.. It would be better to use the terminology basic language range instead of hierarchical matching algorithm. Also, note that matching defined in RFC4647 does not use sub tag information from e.g. the underlying ISO standards. Such information is described in RFC 4646 for the purpose of language tag validation, a process independent of language tag matching. The validation process uses the IANA language sub tag registry. Proposal for replacement of the second sentence: RFC 4647 defines matching of language tags against basic and extended language ranges. This specification implements matching against basic language ranges.	FS	S

Location

Subject

Comment

Followup

Ed. /
Subs.

Discussion threads

Sec. 2.3.1

Adding a reference to BCP47

This section should mention that language tags are defined in BCP47 ("Best Common Practice 47"). There should be a normative reference to BCP47 following the pattern at http://www.w3.org/TR/2007/REC-its-20070403/#bcp47.

Sec. 2.3.1

Renaming Section on "Matching Language Tags"

The section title Matching Language Tags implies matching against language ranges, see comment 3 at http://www.w3.org/International/reviews/0704-sparql/. However, sec. 2.3.1 does not describe sub tag matching, but only identity of a language tag and given data. Rename proposal: Matching the Identity of Language Tags.

Sec. 11.4.12

Modification in description of langMatches operator

We propose to replace the second sentence in the first paragraph: RFC4647 defines a case-insensitive, hierarchical matching algorithm which operates on ISO-defined subtags for language and country codes, and user defined subtags..

It would be better to use the terminology basic language range instead of hierarchical matching algorithm. Also, note that matching defined in RFC4647 does not use sub tag information from e.g. the underlying ISO standards. Such information is described in RFC 4646 for the purpose of language tag validation, a process independent of language tag matching. The validation process uses the IANA language sub tag registry.

Proposal for replacement of the second sentence: RFC 4647 defines matching of language tags against basic and extended language ranges. This specification implements matching against basic language ranges.

Version: $Id: Overview.html,v 1.3 2007/04/19 13:31:12 fsasaki Exp $