---

P-Member	APPROVAL OF THE DRAFT AS PRESENTED	APPROVAL OF THE DRAFT WITH COMMENTS AS GIVEN ON THE ATTACHED	DISAPPROVAL OF THE DRAFT FOR REASONS ON THE ATTACHED	DISAPPROVAL (appropriate changes in the text will change vote to APPROVAL)	ABSTENTION (For Reasons Below)	NO RESPONSE
Canada		X
China						X
Italy						X
Japan		X
Korea	X
Netherlands	X
Norway		X
United Kingdom			X
United States		X

Canada

General:

Suggest that proposed normative Annex F, "Relationship between tau and TMDM" belongs more appropriately as a normative part of ISO/IEC 13250 Part 5 - Reference Model. Annex F could then contain an informative reference to this portion of Part 5.

Technical:

Support the idea that TMQL should support boolean operators as described in section 5.2.

Japan

1. General

Nested queries should be supported. Because query-expression and value-expression are disjoint, TMQL cannot formulate nested queries.

Nested queries are used in querying to a tm defined by using TMQL. For example, a tm is defined by using FLWR expression e. A query using FLWR expression "For $v IN tm/..." could be "For $v IN e/..." by replaceing tm with its definition e. But this FLWR expression is NOT TMQL because "e/..." is query-expression not value-expression in TMQL.

2. Technical

"URI" should be changed to "IRI", because an IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) and allows to use non-Latin scripts in it.

3. Editorial

(3.1) Clause 2 Normative references:

Version of Unicode should be 4.0.

(3.2) Clause 2. Normative references:

"IETF RFC 2396, ... " should be changed to "IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax ... , January 2005, available at http://www.ietf.org/rfc/rfc3986.txt".

(3.3) Clause 2. Normative references:

"IETF RFC 2732, ... " should be deleted, because of it is included in IETF RFC 3986.

(3.4) Clause 2. Normative references:

"IETF RFC 3987, Internationalized Resource Identifiers (IRIs), Internet Standards Track Specification, January 2005, available at http://www.ietf.org/rfc/rfc3987.txt" should be added.

(3.5) Clause 6.5 Value Expressions, EXAMPLE:

" ... $1 (identifier does not start with a character) ... "
should be
" ... $1 (identifier does not start with a numereic character) ... ".

(3.6) Clause 7.5 Projection Postfix, EXAMPLE:

"%m // opera <$_[0]/bn > extracts first all operas."
should be
"%m // opera <$_[0]/bn > extracts the first basename of all operas."

(3.7) Clause 8.4.4:

"[61] compexpr" should be "[61] instance_of".

Norway

1	2	(3)	4	5	(6)	(7)
MB1	Clause No./ Subclause No./ Annex (e.g. 3.1)	Paragraph/ Figure/Table/Note (e.g. Table 1)	Type of com-ment2	Comment (justification for change) by the MB	Proposed change by the MB	Secretariat observations on each comment submitted

NO	7		te	A new term should be used instead of "predicates" in path expressions in order to avoid collision with "predicates" in SELECT expressions. Possible alternatives are "qualifier" or "filter".
NO	7		te	The abbreviations "bn", "oc", and "rd" should be changed so that they look less like topic references.
NO	7		te	The syntactic distinction between internal and external occurrences (resp. "rd" and "oc") requires justification since it does not exist this explicitly in the data model or the XTM syntax.
NO	7		te	The path expression language should avoid excessive use of delimiters in order to avoid becoming overly cryptic.

United Kingdom

At this stage a wider consultation is required as to how best to integrate TMQL with existing data querying mechanisms. Every feature defined in TMQL should be demonstrated to be implementable before the standard moves to FCD stage. This could be achieved, for example, by having a clearly defined mapping between TMQL and the relational data model, of the type proposed in the TMRQL proposal.

United States

Acknowledging changes are needed.