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 1351 - please have a feature to choose between XML 1.1 versus XML 1.0
Summary: please have a feature to choose between XML 1.1 versus XML 1.0
Status: CLOSED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Don Chamberlin
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 04:40 UTC by Felix Sasaki
Modified: 2005-06-09 00:04 UTC (History)
0 users

See Also:


Attachments

Description Felix Sasaki 2005-05-11 04:40:02 UTC
http://www.w3.org/International/2005/02/xquery-review.html Comment ID: 6
Comment 1 Felix Sasaki 2005-05-18 19:09:53 UTC
(In reply to comment #0)
> http://www.w3.org/International/2005/02/xquery-review.html Comment ID: 6

 It is only implementation-defined, whether XQuery supports XML 1.0 or XML 1.1
(defintion of implementation-defined). There should be a feature in XQuery which
allows to choose between these two versions of XML.
Comment 2 Michael Rys 2005-05-18 19:21:39 UTC
What do you mean with "provide a feature"? 

Do you mean a prolog definition? This cannot be done at the query level 
because the semantics is keyed-off what the data model supports. You cannot 
run an XQuery supporting XML 1.1 in its syntax or semantics on XML 1.0 input 
documents or vice-versa without leading to inconsistencies. 

Providing this as implementation-defined behaviour, it is basically an option 
for implementations to provide one or the other (or trying to do both). So in 
this sense it is already a feature.

Best regards
Michael (speaking for myself)
Comment 3 Felix Sasaki 2005-05-30 08:30:33 UTC
(In reply to comment #2)
> What do you mean with "provide a feature"? 
> 
> Do you mean a prolog definition? This cannot be done at the query level 
> because the semantics is keyed-off what the data model supports. You cannot 
> run an XQuery supporting XML 1.1 in its syntax or semantics on XML 1.0 input 
> documents or vice-versa without leading to inconsistencies. 
> 
> Providing this as implementation-defined behaviour, it is basically an option 
> for implementations to provide one or the other (or trying to do both). So in 
> this sense it is already a feature.
> 
> Best regards
> Michael (speaking for myself)

consensus of the i18n-core-wg, telecon 27 may 2005: closed.