3676 2006-09-08 12:56:29 +0000 fn:subsequence typing rules 2006-10-19 20:07:42 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Formal Semantics 1.0 Working drafts PC Windows XP CLOSED FIXED P2 normal --- 1 tim simeon public-qt-comments oldest_to_newest 11513 0 tim 2006-09-08 12:56:29 +0000 In the typechecking rules for fn:subsequence http://www.w3.org/TR/xquery-semantics/#sec_fn_subsequence we have: statEnv |- QName of func expands to (FN-URI,"subsequence") statEnv |- Expr : Type quantifier(Type) in { * } ------------------------------------------------------ statEnv |- QName(Expr, NumericLiteral, 1) : prime(Type) ? This can also include quantifier +. i.e. statEnv |- QName of func expands to (FN-URI,"subsequence") statEnv |- Expr : Type quantifier(Type) in { *, + } ------------------------------------------------------ statEnv |- QName(Expr, NumericLiteral, 1) : prime(Type) ? Similarly: statEnv |- QName of func expands to (FN-URI,"subsequence") statEnv |- Expr : Type quantifier(Type) in { *, + } ------------------------------------------------------ statEnv |- QName(Expr, $fs:last, 1) : prime(Type) ? and statEnv |- QName of func expands to (FN-URI,"subsequence") statEnv |- Expr : Type quantifier(Type) in { *, + } ------------------------------------------------------ statEnv |- QName(Expr, $fs:position, 1) : prime(Type) ? although in the case of +, the type of the last two could be deduced as Prime(Type)) (I think!) 12041 1 simeon 2006-09-26 14:52:22 +0000 Tim, Despite those rules having been checked by many people (See Bugs #2303, #1968, #1728), I believe you are right that we could and probably should cover '+' as well as '*'. I don't believe you could do better than prime(Type)? since + only guarantees there is at least one item. That said, I don't believe the rules are broken (in the sense of being inconsistent) so I am not sure what the working groups will want to reconsider this, considering the late stage of the process. - Jerome 12050 2 tim 2006-09-26 15:28:58 +0000 Thanks. I think we added these rules to our implementation to prevent failing some of the XQTS tests due to static type failures. 12055 3 simeon 2006-09-26 16:00:18 +0000 Tim, The XSLT and XML Query working groups have considered your comment and decided to accept the suggested changes. Best, - Jerome On behalf of the XSLT and XML Query WGs