complexType BagType
diagram index_p1651.png
namespace http://www.opengis.net/gml
type extension of gml:AbstractGMLType
properties
base gml:AbstractGMLType
children gml:metaDataProperty gml:description gml:name gml:member gml:members
used by
element Bag
attributes
Name  Type  Use  Default  Fixed  annotation
idoptional      
documentation
Database handle for the object.  It is of XML type ID, so is constrained to be unique in the XML document within which it occurs.  An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.  This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
annotation
documentation
A non-abstract generic collection type that can be used as a document element for a collection of any GML types - Geometries, Topologies, Features ...

FeatureCollections may only contain Features.  GeometryCollections may only contain Geometrys.  Bags are less constrained  they must contain objects that are substitutable for gml:_Object.  This may mix several levels, including Features, Definitions, Dictionaries, Geometries etc. 

The content model would ideally be
   member 0..*
   members 0..1
   member 0..*
for maximum flexibility in building a collection from both homogeneous and distinct components:
included "member" elements each contain a single Object
an included "members" element contains a set of Objects

However, this is non-deterministic, thus prohibited by XSD.
source <xs:complexType name="BagType">
 
<xs:annotation>
   
<xs:documentation>A non-abstract generic collection type that can be used as a document element for a collection of any GML types - Geometries, Topologies, Features ...

FeatureCollections may only contain Features.  GeometryCollections may only contain Geometrys.  Bags are less constrained  they must contain objects that are substitutable for gml:_Object.  This may mix several levels, including Features, Definitions, Dictionaries, Geometries etc. 

The content model would ideally be
   member 0..*
   members 0..1
   member 0..*
for maximum flexibility in building a collection from both homogeneous and distinct components:
included "member" elements each contain a single Object
an included "members" element contains a set of Objects

However, this is non-deterministic, thus prohibited by XSD.
</xs:documentation>
 
</xs:annotation>
 
<xs:complexContent>
   
<xs:extension base="gml:AbstractGMLType">
     
<xs:sequence>
       
<xs:element ref="gml:member" minOccurs="0" maxOccurs="unbounded"/>
       
<xs:element ref="gml:members" minOccurs="0"/>
     
</xs:sequence>
   
</xs:extension>
 
</xs:complexContent>
</xs:complexType>


XML Schema documentation generated by
XMLSpy Schema Editor http://www.altova.com/xmlspy