- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 24 Oct 2007 06:29:17 +0000
- To: public-sml@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4774
------- Comment #5 from kumarp@microsoft.com 2007-10-24 06:29 -------
Action Item# 132:
Here are some examples of issues that result due to conflicting schemas.
example 1: id constraint conflict
---------------------------------
ID is simple-type in one schema and complex-type in another schema.
<element name="foo">
<sequence>
... ...
</sequence>
<sml:key name="bar" >
<sml:selector xpath="deref(students)/student"/>
<sml:field xpath="ID"/>
</sml:keyref>
</element>
example 2: targetType conflict
------------------------------
doc1 uses xsd-v1 and doc2 uses xsd-v2.
There is a ref from doc1 to doc2. The ref has a targetType=FooType constraint
on it.
FooType definition is different in the 2 conflicting schemas.
<element name="RefElement1" sml:targetType="tns:FooType"/>
Received on Wednesday, 24 October 2007 06:29:24 UTC