This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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
#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
(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".
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