1803 2005-07-22 04:02:12 +0000 [FS] editorial: E.1.4.1 Simply erases 2007-11-04 06:00:04 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Formal Semantics 1.0 Last Call drafts All All ASSIGNED P2 minor --- 1 jmdyck jmdyck public-qt-comments oldest_to_newest 5128 0 jmdyck 2005-07-22 04:02:12 +0000 E.1.4.1 Simply erases Notation / rule 1 / judgment_form_declaration 1 "statEnv |- SimpleValue simply erases to String" It seems like statEnv isn't needed for these judgments. Sem / rule 2 "statEnv |- SimpleValue1 simply erases to String1 SimpleValue1 != ()" This is formatted like one premise, but it's actually two. (Ditto the line after it.) (leftover from last year, comment #263) Sem / rule 3 / conclusion "AtomicValue of type AtomicTypeName" This is ungrammatical. s/AtomicValue/AtomicValueContent/g An AtomicTypeName is not a TypeName. (leftover from last year, comment #264) Sem / rule 3 / conclusion "simply erases to dm:string-value(AtomicValue) of type xdt:untypedAtomic" But this doesn't conform to the judgment form declaration: ... simply erases to String 8362 1 simeon 2006-02-21 19:41:29 +0000 #1 Notation / rule 1 / judgment_form_declaration 1. Removed statEnv from those judgments. #2 Sem / rule 2. // Fixed. #3 Sem / rule 3 / conclusion. // Fixed AtomicValueContent. An AtomicTypeName is a QName which is a TypeName for an atomic type, so I think this is ok. #4 Sem / rule 3 / conclusion // Removed of type xdt:untypedAtomic. - Jerome 9194 2 jmdyck 2006-04-13 04:21:13 +0000 (In reply to comment #1) > > #3 Sem / rule 3 / conclusion. // An AtomicTypeName is > a QName which is a TypeName for an atomic type, so I think this is ok. TypeName does not derive AtomicTypeName, so TypeAnnotation cannot derive "of type AtomicTypeName". 9216 3 simeon 2006-04-13 16:04:30 +0000 As in #1804, I really do not see where the problem is. The values represented by AtomicTypeName are a subset of the values represented by TypeName. - Jerome