- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 08 Feb 2009 18:45:00 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6540 Summary: Available documents in assertions Product: XML Schema Version: 1.1 only Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: Structures: XSD Part 1 AssignedTo: David_E3@VERIFONE.com ReportedBy: mike@saxonica.com QAContact: www-xml-schema-comments@w3.org CC: cmsmcq@blackmesatech.com In defining the dynamic context for XPath evaluation (section 3.13.4.2) we say that available documents is empty, but available collections and the default collection are implementation defined. There is no logic to making these different. Either all three should be empty, or all three should be implementation defined. I think there are many use cases for writing assertions that make access to external documents; for example one can check that the value of an EMPNR attribute corresponds to a value that is present in some external document or database. However, there are also many difficulties - in particular it means that the validity of the attribute depends heavily on the environment in which validation is performed. Making the values of these context properties implementation-defined would pass the buck to implementors to solve these problems if they can find a way of doing it; I would be inclined to favour this route over banning it out of hand. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 8 February 2009 18:45:09 UTC