This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1735 - [FS] should BuiltInAttributes be italicized?
Summary: [FS] should BuiltInAttributes be italicized?
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows 2000
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-18 22:15 UTC by Fred Zemke
Modified: 2007-01-16 17:39 UTC (History)
0 users

See Also:


Attachments

Description Fred Zemke 2005-07-18 22:15:30 UTC
8.1.7 Type adjustment
The inferences use an italicized variable called BuiltInAttributes.
Clicking on the hot link takes one to a definition (good) but
the definition does not define an EBNF non-terminal.  Hence
italicization seems inappropriate (see 2.1.2 "Notations for
judgments", where it says "Patterns are written with italicized
words... By convention, all patterns in the Formal Semantics 
correspond to grammar non-terminals.").

One solution would be to regard BuiltInAttributes as a 
keyword.  Simply change it from italics to bold, making the
defined phrase "extended by BuiltInAttributes is".

Another solution would be to relax the notion that every italicized
variable must refer to a BNF non-terminal.  

I'll call this one minor if the chosen solution is to change the font,
and normal (meaning other input might be desirable) if the solution
is that italics can refer to things other than BNF non-terminals,
which appears to be a fundamental formatting decision in the design
of the specification.
Comment 1 Jerome Simeon 2006-03-30 21:08:04 UTC
Fixed by using the same fonts as for the definition of the
BuiltInAttributes (which is an instance of the grammar, not a
non-terminal).

- Jerome