← Prev in month ← Prev in thread
Next in thread → Next in month →

Fw: CAM schema

From
David RR Webber <>
Date
2003-11-22T15:56:42+00:00
ID
024f01c3b111$f2676a90$6501a8c0@DRRW01
Thread
Fw: CAM schema
Team,

 

Just closing the loop here.  My thanks to 
George for finding these items,

I'll make the adjustments accordingly.

 

DW.

----- Original Message ----- 

From: George Cristian 
Bina 

To: David RR Webber - XML ebusiness ; David Webber 

Sent: Saturday, November 22, 2003 12:06 AM

Subject: Fw: CAM schema

Hi David,

 

Please find enclosed the message I sent you some 
time ago with issues related with your schema.

 

Best Regards,

 George

----- Original Message ----- 

From: George Cristian 
Bina 

To: David RR Webber - XML ebusiness 

Sent: Monday, June 23, 2003 9:41 AM

Subject: CAM schema

Hi David,

 

Just gave a sample file (AddressExample) a try with 
oXygen and performed a validation against latest CAM schema (r013).

There are a few problems you will see if you do the 
same.

 

1. You must specify the content of the 
structure element. My guess is that you should specify a wildcard model allowing 
for elements from any namespace and use a lax validation hint so that if a 
schema is specified for the content the validation should be 
enabled.

 

<xs:element 
name="Structure">
  <xs:complexType 
mixed="true">
           
<xs:choice 
maxOccurs="unbounded">
                  
<xs:any 
processContents="lax"/>
          
</xs:choice>
   <xs:attribute name="ID" 
type="xs:string"/>
   <xs:attribute name="reference" 
type="xs:string"/>
   <xs:attribute name="taxonomy" 
use="required">
    <xs:simpleType>
     <xs:restriction 
base="xs:NMTOKEN">
      <xs:enumeration 
value="UID"/>
      <xs:enumeration 
value="XSD"/>
      <xs:enumeration 
value="DTD"/>
      <xs:enumeration 
value="RNG"/>
      <xs:enumeration 
value="XML"/>
      <xs:enumeration 
value="EDI"/>
     </xs:restriction>
    </xs:simpleType>
   </xs:attribute>
  </xs:complexType>
 </xs:element>

 

2. context/@condition is specified as required 
while in the sample there is a context element without the condition 
attribute.

 

3. conditional element has no conditioncheck 
attribute while in the sample there is such attribute specified for a 
conditional element.

 

4. Same as 3 for conditional/@itemRef, conditional/@reference, conditional/@registry and conditional/@syntax

 

5. A couple of values are used (Java, SQL, etc.) 
but not defined in the enumeration constraint.

 

 

You can get more information if you check the 
validation with oXygen.

 

Best Regards,

 George

-------------------------------------------------------------
George 
Cristian Bina mailto:
COO - 
sync.ro
Phone  +40-(0)251-461480, 
+40-(0)251-461481
Fax    +40-(0)251-461482
Mobile 
+40-(0)723-224067
SyncRO Soft srl, Bd N. Titulescu 170, Craiova, 1100 - 
Romania
http://www.sync.ro
<oXygen/> XML Editor - 
http://www.oxygenxml.com/
← Prev in month ← Prev in thread
Next in thread → Next in month →