W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1645] [FS] tightening the description of the Normalization phase

From: <bugzilla@wiggum.w3.org>
Date: Tue, 19 Jul 2005 22:27:28 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1Dv0Yi-0003iB-3j@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1645





------- Additional Comments From fred.zemke@oracle.com  2005-07-19 22:27 -------
Thanks for the response.  I see your point, SequenceType is part of Core,
but Type is not.  I think the following things can be done to ameliorate this 
confusion for other readers:

1. Change the spelling of Type to FormalType.  Otherwise it is way too
confusing distinguishing "Type" from "type", the latter being the 
ordinary English word which is part of our metalanguage.  I imagine this
confusion must occur repeatedly in spoken English in the working group,
and even if the working group can manage it, what about the public at large?

2. Use some other term than normalization for the conversion of 
SequenceType to FormalType.  That way you can be 100% consistent that
"normalization" refers to phase 3 of static analysis.  For example, you
can provide a judgment "FormalType is formal type for SequenceType"
with FormalType and SequenceType italicized and the rest in bold.
The inference rules for this judgment are as follows:

statEnv |- FormalType is formal type for SequenceType
------------------------------------------------------
statEnv |- FormalType OccurrenceIndicator is formal type for 
           SequenceType OccurrenceIndicator

- (no premise)
--------------
statEnv |- empty is formal type for void()

- (no premise)
--------------
|- statEnv |- AtomicType is formal type for AtomicType

and so forth, converting all the mapping rules of 3.5.4 to inferences.
Received on Tuesday, 19 July 2005 22:27:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC