- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 14 Jul 2005 04:17:32 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1584 Summary: [FS] technical: 4.1.5 Function Calls: "for all j" Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Formal Semantics AssignedTo: simeon@us.ibm.com ReportedBy: jmdyck@ibiblio.org QAContact: public-qt-comments@w3.org 4.1.5 Function Calls DErr / rule 2 "for all 1 <= j <= m" This explicit universal quantification is unique in the spec, and there's no explanation of how to handle it. Usually, "for all j" is accomplished with an ellipsis, thus: FunctionDecl1 = declare function expanded-QName(Type1, ..., Typen) as Type ... FunctionDeclm = declare function expanded-QName(Type1, ..., Typen) as Type which requires all the signatures in statEnv.funcType(expanded-QName) to be identical, which is presumably forbidden for m > 1. You could avoid this by adding a 'j' subscript to all the Type patterns, but then you'd also have to add a 'j' subscript to the Typei in premise 5, but that only makes sense if premise 5 is "within the scope" of the "for all j", which is getting pretty messy. (Note that this problem goes away if you change funcType to map to a single signature.)
Received on Thursday, 14 July 2005 04:17:34 UTC