This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1749 - [FS] editorial: 7.1.8, 7.1.9, 7.1.10, 7.1.11
Summary: [FS] editorial: 7.1.8, 7.1.9, 7.1.10, 7.1.11
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-19 06:23 UTC by Michael Dyck
Modified: 2007-01-16 17:41 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2005-07-19 06:23:00 UTC
7.1.8 The fs:item-sequence-to-untypedAtomic function
7.1.9 The fs:item-sequence-to-untypedAtomic-PI function
7.1.10 The fs:item-sequence-to-untypedAtomic-text function
7.1.11 The fs:item-sequence-to-untypedAtomic-comment function

"by applying the normative rules in [XQuery] Section 3.7.3.(2|5|4|6)"
    Again, lots of rules there. In each case, I think you mean the points
    under "The content expression of a computed [...] constructor is
    processed as follows". Maybe, after "normative rules", insert "for
    processing the content expression".

"There are no special static typing rules for this function."
    So STA should instead treat the function as if it were a user-defined
    function declared with the given signature?
Comment 1 Jerome Simeon 2006-03-29 22:07:27 UTC
Fixed as suggested. The answer to the second question is yes. Added
the following sentence to clarify:

<<
Static type analysis for this function should be performed as for a
built-in function declared with the given signature.
>>

- Jerome