Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] schema datatype for ip address

From: Saurabh Arora <tanish2k@-----.--->
To: Rakshan Murthy <rakshanm@-------.--->, xml-dev@-----.---.---
Date: 2/2/2006 1:20:00 PM
Rakshan Murthy wrote:
>
>
> Hmm,
> I just needed to sit with xml spy for a bit and now i think I have the 
> solution :
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <!--W3C Schema generated by XMLSpy v2006 sp2 U (http://www.altova.com)-->
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 
> elementFormDefault="qualified">
>
>     <xs:simpleType name="ipaddrstr">
>         <xs:restriction base="xs:string">
>           <xs:pattern 
> value="((1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}(1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])" 
> />
i think your restriction pattern is not correct.
if u want the perfect pattern for a say real ip address , you can use this :

"(([1-9]|1[0-9]{1,2}|2([0-1][0-9]?|2[0-3]?|[0-9])|[3-9][0-9]))(\.([0-9]|1[0-9]{1,2}|2([0-4][0-9]?|5[0-5]?|[0-9])?|[3-9][0-9])){3}"

if you can share what exactly are you doing .. we can share our similar 
work effort.

ciao

>         </xs:restriction>
>     </xs:simpleType>
>
>     <xs:complexType name="ipaddr">
>         <xs:simpleContent >
>             <xs:extension base="ipaddrstr">
>                 <xs:attribute name="type" type="xs:string" 
> use="optional" />
>             </xs:extension>
>         </xs:simpleContent>
>     </xs:complexType>
>
> <xs:element name="ip" type="ipaddr" />
>
> </xs:schema>
>
>
> regards,
> rax
>
>> From: "Rakshan Murthy" <rakshanm@h...>
>> To: xml-dev@l...
>> Subject: [xml-dev] schema datatype for ip address Date: Thu, 02 Feb 
>> 2006 04:23:11 -0600
>>
>>
>> Hi,
>>
>> Im trying to create a schema for the following:
>>
>> <ip type="start">1.1.1.1</ip>
>>
>> Basically, a complexType with a 'type' attribute of string, and a 
>> content which is a restricted pattern.
>>
>> I keep getting validation errors from
>> http://www.w3.org/2001/03/webdata/xsv
>>
>> when i try :
>>  <xs:complexType name="ip">
>>   <xs:simpleContent>
>>   <xs:restriction base="xs:string">
>>     <xs:pattern 
>> value="((1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}(1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])"/> 
>>
>>   </xs:restriction>
>>   </xs:simpleContent>
>>   <xs:attribute name="type" type="xs:string" use="optional" />
>>  </xs:complexType>
>>
>> If i use complexContent, it doesnt allow use of patters to restrict.
>> Anyone have a solution?
>>
>> Thanks,
>> rax
>>
>>
>>
>> -----------------------------------------------------------------
>> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>> initiative of OASIS <http://www.oasis-open.org>
>>
>> The list archives are at http://lists.xml.org/archives/xml-dev/
>>
>> To subscribe or unsubscribe from this list use the subscription
>> manager: <http://www.oasis-open.org/mlmanage/index.php>
>>
>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent