FW: W3C Standards Inquiry

Can you assist with this matter, Dan Connolly referred this to you:

Hello,

I would like to verify that the XSDs I have written are indeed aligned
with W3C standards.
The reason I am refereeing this mail to use is due to the fact that
according to our verification tool (XMLSPY 2004) the XSD is valid, but
according to another tool (which is a member of W3C too), the XSD isn't.
If this is the wrong address for this kind of question, please refer me
to the appropriate one and accept my apologies beforehand.

1) Can a restriction element with base:int or base:double have a
minLength | maxLength element? Or is it just for base:string.
Note that the following def. is taken from the link
http://www.w3.org/TR/xmlschema-2/#defn-basetype.
 
XML Representation Summary: restriction Element Information Item
<restriction
  base = QName
  id = ID
  {any attributes with non-schema namespace . . .}>
  Content: (annotation?, (simpleType?, (minExclusive | minInclusive |
maxExclusive | maxInclusive | totalDigits | fractionDigits | length |
minLength | maxLength | enumeration | whiteSpace | pattern)*))
</restriction>

2) Can a complexType contain an element which will contain another
complexType ?
3) Do you have any regulations of redundancy (circulations) between XSDs
by using xsd:include or xsd:reference ? A scenario where A.xsd points to
B.xsd which points to C.xsd which points back to A.xsd


regards,
Ofir Daniel
Product Support Officer
Order Management System (OMS)
Amdocs Product Development Organization (APDO)
Office +972 (0)9 77-64529 Mobile +972 (0)52 838-3488

-----Original Message-----
From: Dan Connolly [mailto:connolly@w3.org]
Sent: Tuesday, July 13, 2004 11:16 PM
To: Ofir Daniel
Subject: Re: W3C Standards Inquiry

On Tue, 2004-07-13 at 12:34, Ofir Daniel wrote:
> Hello,
> 
> I would like to verify that the XSDs I have written are indeed aligned

> with W3C standards.
> The reason I am refereeing this mail to use is due to the fact that
> according to our verification tool (XMLSPY 2004) the XSD is valid, but

> according to another tool (which is a member of W3C too), the XSD
> isn't.
> If this is the wrong address for this kind of question, please refer
> me to the appropriate one and accept my apologies beforehand.

This looks like a good question for xmlschema-dev

http://lists.w3.org/Archives/Public/xmlschema-dev/

> 
>      1. Can a restriction element with base:int or base:double have a
>         minLength | maxLength element? Or is it just for base:string.
>         Note that the following def. is taken from the link
>         http://www.w3.org/TR/xmlschema-2/#defn-basetype.
>          
>         XML Representation Summary: restriction Element Information
>         Item
>        
>         <restriction
>           base = QName
>           id = ID
>           {any attributes with non-schema namespace . . .}>
>           Content: (annotation?, (simpleType?, (minExclusive |
>         minInclusive | maxExclusive | maxInclusive | totalDigits |
>         fractionDigits | length | minLength | maxLength | enumeration
>         | whiteSpace | pattern)*))
>         </restriction>
>        
>        
>      2. Can a complexType contain an element which will contain
>         another complexType ?
>      3. Do you have any regulations of redundancy (circulations)
>         between XSDs by using xsd:include or xsd:reference ? A
>         scenario where A.xsd points to B.xsd which points to C.xsd
>         which points back to A.xsd.
> 
> regards,
> Ofir Daniel
> Product Support Officer
> Order Management System (OMS)
> Amdocs Product Development Organization (APDO) Office +972 (0)9
> 77-64529 Mobile +972 (0)52 838-3488
> 
> The information contained in this message is proprietary of Amdocs,
> protected from disclosure, and may be privileged.
> The information is intended to be conveyed only to the designated
> recipient(s)
> of the message. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, use,
> distribution or copying of this communication is strictly prohibited
> and may be unlawful.
> If you have received this communication in error, please notify us
> immediately by replying to the message and deleting it from your
> computer.
> Thank you.
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/




The information contained in this message is proprietary of Amdocs,
protected from disclosure, and may be privileged.
The information is intended to be conveyed only to the designated recipient(s)
of the message. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, use, distribution or copying of
this communication is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.
Thank you.

Received on Wednesday, 14 July 2004 02:18:48 UTC