complexType BagType

complexType {http://www.opengis.net/gml}BagType

Type Heirarchy
{http://www.opengis.net/gml}AbstractGMLType (by extension)
 {http://www.opengis.net/gml}BagType
Derived Types
{http://www.opengis.net/gml}BagType
 {http://www.opengis.net/gml}Bag (by type)
Abstractfalse (This can be used in an instance)
Target Namespacehttp://www.opengis.net/gml
Declared Namespacesxmlns:gml=http://www.opengis.net/gml
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xmlns:sch=http://www.ascc.net/xml/schematron
xmlns:xlink=http://www.w3.org/1999/xlink
xmlns=http://www.w3.org/2001/XMLSchema


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>


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.


complexType BagType


Stylus Studio XML Schema Library Home
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio®, a product from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2006 All Rights Reserved.