Re: minOccurs="1" and maxOccurs="1" in XMLSpy

Thanks Jerry, it worked. Sorry about my sort of misposting here. I couldn't see the Altova user forum earlier. I will post the product-related questions there from now on.

----- Original Message ----
From: Gerald Sheehan <gerald.sheehan@altova.com>
To: Gokhan <gokuiuc@yahoo.com>
Sent: Thursday, January 10, 2008 7:48:24 AM
Subject: RE:


Hi Gokhan,
 
Yes, it is true that minOccurs="1" and maxOccurs="1" are the default values and there is no need to explicitly display them The issue is that when you switch to the Schema View, this information is stripped in order to load the document into this view. If you wish to explicitly see these default attribute values in your schema, please don?t switch to the Schema View or save the file in the schema design view. Instead save all changes in the Text View and should you make any switch to the Schema Design View, re-load the document when you switch back to the Text View by clicking on the Reload icon on the toolbar. You can also set the file type to open in the Text View by default from under the Tools\Options, File Types Tab dialog and refrain from switching to the schema design view. One last possibility would be to put a documentation element for them that says they are the default values of minOccurs & maxOccurs.
 
http://www.altova.com/forum/default.aspx?g=posts&t=7529
 
Best Regards, 
... Jerry Sheehan
... Pre-Sales Engineer
... Altova, Inc.

===================================================================
Altova®  accelerates  application development  and  data management
projects with  software  and  solutions  that enhance  productivity
and maximize results. Uncover why Altova is the preferred choice of
over three million users worldwide! Look into www.altova.com today!
===================================================================

Altova,  XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent,
UModel, DiffDog, DatabaseSpy, AltovaXML, Authentic,  and MissionKit
are trademarks and/or  registered trademarks of  Altova GmbH in the 
United States,  the European Union,  and  numerous other countries.
The information transmitted in this message and/or as an attachment
to it  is intended  only for the  person or  entity to  which it is
addressed and may contain confidential  and/or privileged material.
Any  review,  retransmission,  dissemination  or  other use of,  or
taking of any action in reliance upon,  this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error,  please contact  the sender  and delete the
material from any computer.  Altova GmbH  and  Altova, Inc.  do not
accept legal responsibility  for the contents of this message.  Any
views or opinions  presented are solely  those of the author and do
not  necessarily  represent those of  Altova GmbH and  Altova, Inc.
unless otherwise specifically stated. Thank you! 
 




From: Gokhan [mailto:gokuiuc@yahoo.com] 
Sent: Wednesday, January 09, 2008 4:13 PM
To: xmlschema-dev@w3.org
Subject: 


Hello,
 
I am using XMLSpy 2008. If I create minOccurs="1" or maxOccurs="1" occurrence restraints on a child element, close the schema and reopen it, then XMLSpy removes these occurrence restraints. This only happens for minOccurs="1" and maxOccurs="1". I assume that this removal is done, because "1" is the default value for both, but we need to see it in XMLSpy. Moreover, if XMLSpy removes these restraints and then the schema is saved due to some other change, then we also lose these restraints in the saved schema.
 
StylusStudio 2007 doesn't do this, so I believe that it is a bug in XMLSpy. Or is there a way in the settings to prevent XMLSpy removing minOccurs="1" and maxOccurs="1"?
 
Thanks,
Gokhan



Looking for last minute shopping deals? Find them fast with Yahoo! Search.


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping