hello

my question is:
I have an attribute (lets name it kfir) that can recieve parameters
ACTION, TIME1, etc (meaning uppercase charcters and numbers together or not together). I dont have a limit on the size of what is written on the xml file. how can I declare the data type when I dont have a limit. (I thought of writing

<xs:restriction base="xs:string">
                        <xs:pattern value="[A-Z0-9][A-Z0-9]"/>
                    </xs:restriction>

or add some more [A-Z0-9] but I want it to be that no matter how long what I will recieve in the xml file, I will know how to handle it.
is there other and better way to declare the data type?

thanks

kfir

__________________
kfir

An asterisk * means any number of times so assuming you need at least one character I think you need: --

Joe (Microsoft MVP - XML)

Try the pattern value="[A-Z0-9]*"

And do get yourself a reference book on XML Schema and read it once through. It's fine asking questions on a forum when you're stuck, but it's not an efficient way to do your basic learning.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

Bit of a daze this morning, a plus + means one or more times so:
--

Joe (Microsoft MVP - XML)

I declared this
<xs:pattern value="([A-Z0-9])+"/>

and my Q is, if I the value that I recieve from the xml could be like this for example
TIME1_NEW or TIME1 or ACTIVE, etc (could be mixed letters and numbers and signals ('_'). at first I declared the type as a string but I dont think that it means the values with '_' sign. my Q is what restriction base do I need to give in order to cover all the possibilities?

thanks

never mind, I managed.
thanks any way

kfir

I'm always rather surprised to see questions like this. Where did you look for the information? Have you read about regular expressions, and not understood the information - or are you just coming here to save yourself the trouble? I can show you how to extend the regular expression to include "_", but my worry is that you'll then just come back with another question asking how to add the next feature.

In short, I need to understand what concept you haven't understood.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference