[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sdo] ISSUE 157: Support for Facets. Proposed Partial Resolution
Hi Ron, What's missing from the core spec are what SDO types each facet pertains to. For example it was not immediately clear to me why MinInclusive was a String property, until I remembered that it can apply to both numerical and date/time XML schema types. Will these XML schema based facets only apply to their SDO counterparts or will I be able to state for a string property MinInclusive="apple" MaxInclusive="car", where "banana' would be a valid value while "dog" would not be? Also should Enumeration be limited to List<String>? I could have an enumeration of other XML schema types: <xs:simpleType name="prime-enum"> <xs:restriction base="xs:int"> <xs:enumeration value="2"/> <xs:enumeration value="3"/> <xs:enumeration value="5"/> <xs:enumeration value="7"/> </xs:restriction> </xs:simpleType> This proposal introduces a backwards compatibility issue, prior to SDO 3.0 when the following XML schema was converted to SDO metadata then the "user-id" property would have been of type "{commonj.sdo}String", with this new proposal the type of the "user-id" property will now be an anonymous subtype of {commonj.sdo}String. <xs:complexType name="customer"> <xs:sequence> <xs:element name="user-id"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:minLength value="8"/> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> -Blaise 4B55CA8D.60009@oracle.com" type="cite">Barack, Ron wrote:1BC7B594EE497146B0CFF2F493B682340722D670E4@DEWDFECCR02.wdf.sap.corp" type="cite"> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]