Showing:

Annotations
Attributes
Diagrams
Source
Used by
Complex Type gml:BagType
Namespace http://www.opengis.net/gml
Annotations
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.
Diagram
Diagram docindex5.tmp#id53 docindex6.tmp#id34 docindex7.tmp#id48 docindex8.tmp#id50 docindex9.tmp#id33 docindex10.tmp#id32 docindex378.tmp#id663 docindex200.tmp#id664
Type extension of gml:AbstractGMLType
Type hierarchy
Used by
Element gml:Bag
Model gml:metaDataProperty* , gml:description{0,1} , gml:name* , gml:member* , gml:members{0,1}
Children gml:description, gml:member, gml:members, gml:metaDataProperty, gml:name
Attributes
QName Type Fixed Default Use Annotation
gml:id ID optional
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.
Source
<complexType name="BagType">
  <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.</documentation>
  </annotation>
  <complexContent>
    <extension base="gml:AbstractGMLType">
      <sequence>
        <element ref="gml:member" minOccurs="0" maxOccurs="unbounded"/>
        <element ref="gml:members" minOccurs="0"/>
      </sequence>
    </extension>
  </complexContent>
</complexType>
Schema location http://schemas.opengis.net/gml/3.1.1/base/gmlBase.xsd