Re: ForCES model xml schema boolean type defition error

Jia Fenggen <[email protected]>
Newsgroups gmane.ietf.forces
Message-ID <[email protected]>
Yes,I also think that it's very strange to have three synonyms for that.Is 
there an alias mechanism in schema so that we could define one base boolean 
type and use alias to reflect all the other forms,if there is not then i 
prefer to make things easy to take one of 1) to 3) representation.
Yours,Fenggen
>From: "Joel M. Halpern" <[email protected]>
>Reply-To: "Joel M. Halpern" <[email protected]>
>To: [email protected]
>Subject: Re: ForCES model xml schema boolean type defition error
>Date: Fri, 22 Sep 2006 09:48:38 -0400
>
>The model draft has expired.  I am working on a revision, to include 
>all comments that have been received.
>And all changes I previously stated would be made.  It will be a few 
>weeks, but not many.
>
>With regard to the usage of booleanType, you raise an interesting 
>question.  I can see three answers.
>1) Change group="no"/"yes" to group="0"/"1".
>2) Change booleanType to only allow "no" and "yes".
>3) Change booleanType to "false" and "true", and find all uses and 
>fix them to "false/"true" as well.
>4) change boolean type to allow "0", "1" and "no", "yes", and 
>"true", "false".
>
>given that the enumeration definition doesn't actually specify 
>semantics, just allowed syntax, I am tempted to go with the last 
>alternative, so that the most meaningful form can be used in 
>whatever context the booleanType is being used.
>
>But it is arguably pretty strange to have three synonyms for that
>Yours,
>Joel
>
>At 07:17 AM 9/22/2006, Jia Fenggen wrote:
>>I use Altova XMLspy to check the model xml schema and find out an 
>>error in the definition of boolean,in the schema,we define boolean 
>>type has two enumeration value as "0" and "1":
>>       <xsd:simpleType name="booleanType">        <xsd:restriction 
>>base="xsd:string">          <xsd:enumeration value="0"/>          
>><xsd:enumeration value="1"/>        </xsd:restriction> 
>></xsd:simpleType> but when we use this to define outputPortType and 
>>inputPortType,we use "no",so the altova complain error,we could 
>>change the booleanType enumeration to correct this error.
>><xsd:simpleType name="booleanType">        <xsd:restriction 
>>base="xsd:string">          <xsd:enumeration value="no"/>          
>><xsd:enumeration value="yes"/>        </xsd:restriction>       
>></xsd:simpleType>
>>probably this issue has been change,if that is the case,sorry for 
>>the noise.
>>BTW,today i access the ietf website only to find that the model 
>>draft is not on the draft list,could anyone told me why?
>>Yours,Fenggen
>>
>>_________________________________________________________________
>>浜ㄤ涓澶х靛欢绯荤 MSN Hotmail  
>>http://www.hotmail.com
>>

_________________________________________________________________
璐逛杞 MSN Explorer:   http://explorer.msn.com/lccn
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.