1609 2005-07-15 00:03:26 +0000 two notations for function evaluation (= and =>) 2007-01-16 17:27:40 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Formal Semantics 1.0 Last Call drafts PC Windows 2000 CLOSED FIXED P2 minor --- 1 fred.zemke simeon public-qt-comments oldest_to_newest 4685 0 fred.zemke 2005-07-15 00:03:26 +0000 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. 4711 1 jmdyck 2005-07-15 19:07:29 +0000 (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.) 4875 2 simeon 2005-07-19 16:44:21 +0000 I believe this is editorial. - Jerome 9161 3 mff 2006-04-11 22:13:25 +0000 Already fixed in earlier draft