This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
2.1.4 Notations for environments The specification uses more than one notation to indicate the evaluation of a static environment member that is a function. See for example 3.1.1.1 "Resolving QNames to expanded QNames" uner "Semantics" the first inference has the following judgment above the line: statEnv.namespace(NCName) = URI-or-EmptyNamespace This means that the statEnv.namespace member is a function. When you evaluate this function for NCName, you get URI-or-EmptyNamespace. Contrast this example with section 7.1.9 "Type Expansion" second inference, second line: statEnv.typeDefn(expanded-QName) => define type ... Sometimes you use = and sometimes you use => for the same meaning, the result of evaluating a function that is a member of an environment.
(In reply to comment #0) > > ... section > 7.1.9 "Type Expansion" second inference, second line: > > statEnv.typeDefn(expanded-QName) => define type ... You must be looking at an old draft. It was '=>' up to the 20050404 draft, but was changed to '=' in the 20050603 draft. (And the last time 'Type expansion' was section 7.1.9 was the 20040220 draft, the previous Last Call.)
I believe this is editorial. - Jerome
Already fixed in earlier draft