Jump to content

scotcarl

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About scotcarl

  • Rank
    Newbie
  1. Not that I don't agree, bcos under most circumstances I would also consider that min and max would be well suited to being an attribute, however in this situation it serves my purposes better to have it set up the way I have in the example. Also, fixing the problem with the min/max ellements does not solve the same problem that exists with the ordering of the Height/Width elements.The example that I gave in the origional post is actually a smaller snippet of a larger element definition, which is basically an extension of the same thing. I only included the small section of code bcos I didn't
  2. Hello to everyone in XML schema land.I am only new to the world of XML and schemas, so forgive me if I am asking a stupid question.I seem to have run into a limitation when creating a schema, and I do not see any logical reason for the limitation, so I'm hoping there is a way around it.The problem I have is as follows.I have written the following section of schema code. <xsd:element name="Size"> <xsd:complexType> <xsd:sequence> <xsd:choice> <xsd:sequence> <xsd:element name="minHeight" minOccurs="0" type="xsd:int"/> <xsd:element name="maxHei
×
×
  • Create New...