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

Hello,
=0D
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.
=0D
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.
 =0D
XML Representation Summary: restriction Element Information Item
<restriction=0D
  base = QName=0D
  id = ID=0D
  {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 ?=0D
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,=0D
Ofir Daniel=0D
Product Support Officer=0D
Order Management System (OMS)=0D
Amdocs Product Development Organization (APDO)=0D
Office +972 (0)9 77-64529 Mobile +972 (0)52 838-3488=0D

-----Original Message-----
From: Dan Connolly [mailto:connolly@w...]=0D
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,
> =0D
> 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=0D
> 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=0D
> isn't.
> If this is the wrong address for this kind of question, please refer=0D
> 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/

> =0D
>      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.
>          =0D
>         XML Representation Summary: restriction Element Information
>         Item
>        =0D
>         <restriction=0D
>           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>
>        =0D
>        =0D
>      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.
> =0D
> regards,
> Ofir Daniel
> Product Support Officer
> Order Management System (OMS)
> Amdocs Product Development Organization (APDO) Office +972 (0)9=0D
> 77-64529 Mobile +972 (0)52 838-3488
> =0D
> The information contained in this message is proprietary of Amdocs,=0D
> 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=0D
> recipient, you are hereby notified that any dissemination, use,=0D
> distribution or copying of this communication is strictly prohibited=0D
> and may be unlawful.
> If you have received this communication in error, please notify us=0D
> immediately by replying to the message and deleting it from your=0D
> 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=0D
this communication is strictly prohibited and may be unlawful.=0D
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.

From bryce@s...  Wed Jul 14 02:43:29 2004
Return-Path: <bryce@s...>
X-Original-To: xmlschema-dev@l...
Delivered-To: xmlschema-dev@l...
Receiv