Bug 1776 – [FS] editorial: 8.2.2.2 Dynamic semantics of axes

Bug 1776 - [FS] editorial: 8.2.2.2 Dynamic semantics of axes

Summary:

[FS] editorial: 8.2.2.2 Dynamic semantics of axes

Status:	CLOSED FIXED

Product:	XPath / XQuery / XSLT
Component:	Formal Semantics 1.0
Version:	Last Call drafts
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:	2005-07-20 02:20 UTC by Michael Dyck
Modified:	2008-08-29 19:08 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 2005-07-20 02:20:18 UTC

8.2.2.2 Dynamic semantics of axes

Sem / rule 5 / conclusion
"axis attribute:: of ElementName { AttributeValue,ElementValue }"
    After "of", insert "element".
(leftover from last year, comment #213)

(very last line of the section)
"dynEnv |- axis Axis of NodeValue => () otherwise."
    Presentationally, this looks like a judgment form declaration. It
    would be nice if you could at least make it *look* like an inference
    rule. E.g., have a single premise saying "otherwise".
(leftover from last year, comment #214)

Comment 1 Jerome Simeon 2006-03-30 17:01:13 UTC

First comment fixed as suggested. Second comment: removed 'otherwise'
and added some clarification in the text before.
- Jerome

Comment 2 Michael Dyck 2006-09-15 05:48:01 UTC

Re second comment: It would still be nice if you could make it look like an
inference rule, as you did at the end of 8.2.3.1.2 (in response to Bug 1778)
and 8.2.3.2.2 (in response to Bug 1780).

Comment 3 Michael Dyck 2008-08-29 19:08:33 UTC

The request in the previous comment has been entered as FS erratum E034, 
and the change has been committed to the source files for the next edition
of the FS document. 

Since that was the only unresolved point in this issue, I'm marking it
resolved-FIXED, and CLOSED.