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 3846 - axis child:: of ElementType - processing-instructions and comments
Summary: axis child:: of ElementType - processing-instructions and comments
Status: CLOSED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows XP
: P2 normal
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: 2006-10-18 09:59 UTC by Tim Mills
Modified: 2007-02-14 08:20 UTC (History)
0 users

See Also:


Attachments

Description Tim Mills 2006-10-18 09:59:15 UTC
From 8.2.2.1.3 Inference rules for the child axis

the rule:

statEnv |-  ElementType type lookup OptNillable TypeReference
statEnv |-  OptNillable TypeReference expands to Type1 | · · · | Typen
statEnv |-  Type1 has node content Type1'
· · ·
statEnv |-  Typen has node content Typen'
---------------------------------------------------------------
statEnv |-  axis child:: of ElementType : Type1' | ... | Typen'

makes no mention of processing-instructions and comments.  Should it not make such a mention, in a similar manner to the rule for axis child:: of document?

statEnv |-  axis child:: of document { Type } : Type & processing-instruction* & comment*
Comment 1 Jerome Simeon 2007-02-14 02:26:35 UTC
Tim,
I believe it does produce a type with PI and comments added. The 'expands to' judment which is used in the inference rule you quote, is defined using the 'adjusts to' (Section 8.1.7) judgment which indeed add types for PI and comment nodes. Let us know if that makes sense.
Best,
- Jerome
Comment 2 Tim Mills 2007-02-14 08:20:07 UTC
Thatnks - I hadn't followed through all the judgements quite carefully enough!

I'd be very greateful if you could comment on bug report 4273, as I think this is the only major stumbling block we have with our XQuery implementation.