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 16180 - should schZ014_a be valid?
Summary: should schZ014_a be valid?
Status: NEW
Alias: None
Product: XML Schema Test Suite
Classification: Unclassified
Component: Microsoft tests (show other bugs)
Version: 2006-11-06
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema Test Suite mailing list
URL:
Whiteboard:
Keywords: needsDrafting
Depends on:
Blocks:
 
Reported: 2012-03-01 16:49 UTC by Andreas Meissl
Modified: 2012-12-04 00:51 UTC (History)
2 users (show)

See Also:

Attachments

Description Andreas Meissl 2012-03-01 16:49:45 UTC 
I don't find a clause in the XSD 1.1 spec which makes test schZ014_a of set MS-Schema2006-07-15 invalid. The most likely one - src-import.1.2 - isn't violated in my opinion, because a namespace attribute is present, but with empty value. 

Section 3.17.2 XML Representations of Schemas says: "...supplying an empty string for targetNamespace is incoherent, and is not the same as not specifying it at all."

So in my opinion also src-import.1.1 isn't violated, because the empty value of the present namespace attribute is not the same as a not specified targetNamespace.
Comment 1 Michael Kay 2012-04-13 16:18:41 UTC 
Personal response: I would contend that there are three "reasonable" interpretations of <xsl:import namespace=""/>:

(a) it's an error

(b) it's equivalent to omitting the namespace attribute

(c) it's equivalent to omitting the xsl:import element

I think the spec currently doesn't give any support to any of these interpretations, and my preference would be for (a).

Saxon currently adopts (b), which means this schema document is invalid because the namespace is the same as the target namespace of the containing schema document.
Comment 3 David Ezell 2012-05-04 16:34:06 UTC 
Resolved: to make the empty string invalid in the spec, and mark the bug as needsDrafting.