Bug 3871 – [FS] editorial: 2.4.4. Top level definitions

Bug 3871 - [FS] editorial: 2.4.4. Top level definitions

Summary:

[FS] editorial: 2.4.4. Top level definitions

Status:	CLOSED FIXED

Product:	XPath / XQuery / XSLT
Component:	Formal Semantics 1.0
Version:	Candidate Recommendation
Platform:	All All

Importance:	P2 minor
Target Milestone:	---
Assigned To:	Michael Dyck
QA Contact:	Mailing list for public feedback on specs from XSL and XML Query WGs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-10-28 04:45 UTC by Michael Dyck
Modified:	2008-08-30 21:59 UTC (History)
CC List:	0 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Dyck 2006-10-28 04:45:03 UTC

2.4.4. Top level definitions

examples
    The examples are confused about whether Definitions are
    separated by whitespace
        2.4.4 / -- / example 4
        2.4.5 / -- / example 4
        3.5.1 / -- / example (4|8|9|12)
        8.1.8 / -- / example 1
    or terminated by a semicolon
        2.4.4 / -- / example (2|6)
        2.4.5 / -- / example 2
    Please pick one. (The latter would be consistent with the use of
    semicolons in Prolog, but you'd need to add a semicolon to the
    production for Definitions.)

before example 6
"is represented as follow"
    s/follow/follows/

example 6
define type SKU restrict xsd:string
    s/restrict/restricts/

example 10
element zip name of type xs:integer
    Delete 'name'

Comment 1 Jim Melton 2007-02-26 00:17:37 UTC

The fix for this bug does not appear in the Recommendation of 23 January 2007. 
It will be considered for a future publication (either an Errata document or
some possible future version of the specification).

Comment 2 Michael Dyck 2008-08-30 21:18:51 UTC

The first point of comment #0 has been entered as FS erratum E042. For
the fix, I chose "terminated by a semicolon", and committed the necessary
changes to the source files for the next edition of the FS document.

Comment 3 Michael Dyck 2008-08-30 21:29:20 UTC

The last point of comment #0 was also raised in Bug 4766 comment #2, and
was fixed via FS erratum E020.

Comment 4 Michael Dyck 2008-08-30 21:58:46 UTC

The remainder this issue has been entered as FS erratum E043, and the
proposed fixes have been committed to the source files for the next edition
of the FS document.  Consequently, I'm marking this issue resolved-FIXED,
and CLOSED.