Specification Name: EDXL Hospital AVailability Exchange (HAVE) 2.0
Description: Defines the XML schema for the EDXL HAVE message exchange Produced by:
Emergency Management HAVE Subcommittee URL: http://docs.oasis-open.org Version: 2.0 WD
Status: SC DRAFT Copyright: 2012-2015, OASIS, http://www.oasis-open.org Last Modified:
05JAN2015 Last Modified by: Darrell O'Donnell, P.Eng.

Guiding Concepts/Principles: Schema Validation: should
provide deep validation capabilities as opposed to being a basic schema where different
groups make up extensions to the point where nothing is valid in between systems.
Extensible: Key areas of the schema should support extensibility in a controlled manner.
The use of managed taxonomies can allow a group to define a new set of services that are
used in a network for example. Simple: Though the standard could support aggregation the
provision of individual facility elements REVIEW: new elements ID and IDREF: References
(IDREF) to unique elements (ID) should be used, especially where establishing of a
hierarchy.

See ISO/DIS 19136 7.2.
The gmlBase schema components establish the GML model and syntax, in particular
-	a root XML type from which XML types for all GML objects should be derived,
-	a pattern and components for GML properties,
-	patterns for collections and arrays, and components for generic collections and arrays,
-	components for associating metadata with GML objects,
-	components for constructing definitions and dictionaries.

See ISO/DIS 19136 Clause 10.
Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. 
All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified.
The geometry model distinguishes geometric primitives, aggregates and complexes. 
Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces.

This schema document provides attribute declarations and
attribute group, complex type and simple type definitions which can be used in
the construction of user schemas to define the structure of particular linking
constructs, e.g.<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
           xmlns:xl="http://www.w3.org/1999/xlink">

 <xs:import namespace="http://www.w3.org/1999/xlink"
            location="http://www.w3.org/1999/xlink.xsd">

 <xs:element name="mySimple">
  <xs:complexType>
   ...
   <xs:attributeGroup ref="xl:simpleAttrs"/>
   ...
  </xs:complexType>
 </xs:element>
 ...
</xs:schema>

See http://www.w3.org/XML/1998/namespace.html and
   http://www.w3.org/TR/REC-xml for information about this namespace.

    This schema document describes the XML namespace, in a form
    suitable for import by other schema documents.  

    Note that local names in this namespace are intended to be defined
    only by the World Wide Web Consortium or its subgroups.  The
    following names are currently defined in this namespace and should
    not be used with conflicting semantics by any Working Group,
    specification, or document instance:

    base (as an attribute name): denotes an attribute whose value
         provides a URI to be used as the base for interpreting any
         relative URIs in the scope of the element on which it
         appears; its value is inherited.  This name is reserved
         by virtue of its definition in the XML Base specification.

    id   (as an attribute name): denotes an attribute whose value
         should be interpreted as if declared to be of type ID.
         This name is reserved by virtue of its definition in the
         xml:id specification.

    lang (as an attribute name): denotes an attribute whose value
         is a language code for the natural language of the content of
         any element; its value is inherited.  This name is reserved
         by virtue of its definition in the XML specification.
  
    space (as an attribute name): denotes an attribute whose
         value is a keyword indicating what whitespace processing
         discipline is intended for the content of the element; its
         value is inherited.  This name is reserved by virtue of its
         definition in the XML specification.

    Father (in any context at all): denotes Jon Bosak, the chair of 
         the original XML Working Group.  This name is reserved by 
         the following decision of the W3C XML Plenary and 
         XML Coordination groups:

             In appreciation for his vision, leadership and dedication
             the W3C XML Plenary on this 10th day of February, 2000
             reserves for Jon Bosak in perpetuity the XML name
             xml:Father

This schema defines attributes and an attribute group
        suitable for use by
        schemas wishing to allow xml:base, xml:lang, xml:space or xml:id
        attributes on elements they define.

        To enable this, such a schema must import this schema
        for the XML namespace, e.g. as follows:
        <schema . . .>
         . . .
         <import namespace="http://www.w3.org/XML/1998/namespace"
                    schemaLocation="http://www.w3.org/2001/xml.xsd"/>

        Subsequently, qualified reference to any of the attributes
        or the group defined below will have the desired effect, e.g.

        <type . . .>
         . . .
         <attributeGroup ref="xml:specialAttrs"/>
 
         will define a type which will schema-validate an instance
         element with any of those attributes

In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
http://www.w3.org/2007/08/xml.xsd.
At the date of issue it can also be found at
http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML Schema
itself, or with the XML namespace itself.  In other words, if the XML
Schema or XML namespaces change, the version of this document at
http://www.w3.org/2001/xml.xsd will change
accordingly; the version at
http://www.w3.org/2007/08/xml.xsd will not change.

Specification Name: OASIS EDXL Common Types ver 1.0
         Description: Defines the W3C schema with commonly used types suc as ValueListURI
         (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
         Produced by: Emergency Management Infrastructure Framework Subcommittee
         URL: http://docs.oasis-open.org
         Version: 1.0  
         Status: Committee Specification Draft
         Copyright: 2010, OASIS, http://www.oasis-open.org
         Last Modified: 9 September 2011
         Last Modified by: Don McGarry - The MITRE Corp.
Update 9 July, 2014 (by Werner Joerg): for compliance with EDXL Naming and Capitalization Guidelines (EM-TC 12/18/2012)

Specification Name: OASIS EDXL extensible Party Information Language (xPIL) profile ver 1.0
Description: Defines the W3C schema for the EDXL Profile representing party information (unique identifiers)
including 	party name and address
(Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
Produced by: Emergency Management Infrastructure Framework Subcommittee
URL: http://docs.oasis-open.org
Version: 1.0  
Status: Committee Specification Draft
Copyright: 2010, OASIS, http://www.oasis-open.org
Last Modified: 12 July 2011
Last Modified by: Don McGarry - The MITRE Corp.
            
Profile Developed From:
Specification Name: OASIS CIQ TC - extensible Party Information Language (xPIL) 
Description: Defines the W3C schema for representing party information (unique identifiers)
including 	party name and address
(Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
Produced by: OASIS Customer Information Quality Technical Committee
URL: http://www.oasis-open.org/committees/ciq
Version: 3.0  
Status: Committee Specification CS02
Copyright: 2007-09, OASIS, http://www.oasis-open.org
Last Modified: 20 September 2008
Last Modified by: Ram Kumar, Chair, OASIS CIQ TC (original file)

Specification Name: OASIS CIQ TC - CIQ V3.0
Description: Defines the W3C schema with commonly used types in the name, address and party schemas
(Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
Produced by: OASIS Customer Information Quality Technical Committee
URL: http://www.oasis-open.org/committees/ciq
Version: 3.0  
Status: Committee Specification CS02
Copyright: 2007-09, OASIS, http://www.oasis-open.org
Last Modified: 20 September 2008
Last Modified by: Ram Kumar, Chair, OASIS CIQ TC

Specification Name: OASIS EDXL extensible Name Language (xNL) profile ver 1.0
         Description: Defines the W3C schema for the EDXL Profile representing party names (Person or Organisation)
         (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
         Produced by: Emergency Management Infrastructure Framework Subcommittee
         URL: http://docs.oasis-open.org
         Version: 1.0  
         Status: Committee Specification Draft
         Copyright: 2010, OASIS, http://www.oasis-open.org
         Last Modified: 12 July 2011
         Last Modified by: Don McGarry - The MITRE Corp.
         
Profile Developed From:
         Specification Name: OASIS CIQ TC - extensible Name Language (xNL) 
         Description: Defines the W3C schema for representing party names (Person or Organisation)
         (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
         Produced by: OASIS Customer Information Quality Technical Committee
         URL: http://www.oasis-open.org/committees/ciq
         Version: 3.0  
         Status: Committee Specification CS02
         Copyright: 2007-09, OASIS, http://www.oasis-open.org
         Last Modified: 20 September 2008
         Last Modified by: Ram Kumar, Chair, OASIS CIQ TC

Specification Name: OASIS CIQ TC - extensible Name Language Types (xNL-types)
Description: Defines the W3C schema that provides enumeration lists to support xNL v3.0
(Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
Produced by: OASIS Customer Information Quality Technical Committee
URL: http://www.oasis-open.org/committees/ciq
Version: 3.0  
Status: Committee Specification CS02
Copyright: 2007-09, OASIS, http://www.oasis-open.org
Last Modified: 20 September 2008
Last Modified by: Ram Kumar, Chair, OASIS CIQ TC 
            
NOTE: This is the schema that users can customise the enumeration lists to meet their
exchange requirements. The enumeration values provided are ONLY SAMPLES and 
is not complete. It is upto the application to decide what the values should be.  To achieve 
interoperability between applications using this specification, it is recommended that an
SLA/agreement is in place as to what the enumeration values will be used in this file

Specification Name: OASIS EDXL extensible Address Language (xAL) profile ver 1.0
          Description: Defines the W3C schema for the EDXL Profile for representing addresses
          (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
          Produced by: Emergency Management Infrastructure Framework Subcommittee
          URL: http://docs.oasis-open.org
          Version: 1.0  
          Status: Committee Specification Draft
          Copyright: 2010, OASIS, http://www.oasis-open.org
          Last Modified: 12 July 2011
          Last Modified by: Don McGarry - The MITRE Corp.
		
	Profile Developed From:
          Specification Name: OASIS CIQ TC - extensible Address Language (xAL) 
          Description: Defines the W3C schema for representing addresses
          (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
          Produced by: OASIS Customer Information Quality Technical Committee
          URL: http://www.oasis-open.org/committees/ciq
          Version: 3.0  
	Status: Committee Specification CS02
	Copyright: 2007-09, OASIS, http://www.oasis-open.org
	Last Modified: 20 September 2008
          Last Modified by: Ram Kumar, Chair, OASIS CIQ TC

Specification Name: OASIS CIQ TC - extensible AddressLanguage Types (xAL-types)
          Description: Defines the W3C schema that provides enumeration lists to support xNL v3.0
          (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
          Produced by: OASIS Customer Information Quality Technical Committee
          URL: http://www.oasis-open.org/committees/ciq
          Version: 3.0  
          Status: Committee Specification CS02
          Copyright: 2007-09, OASIS, http://www.oasis-open.org
          Last Modified: 20 September 2008
          Last Modified by: Ram Kumar, Chair, OASIS CIQ TC 
		
          NOTE: This is the schema that users can customise the enumeration lists to meet their
          exchange requirements. The enumeration values provided are ONLY SAMPLES and 
          is not complete. It is upto the application to decide what the values should be.  To achieve 
          interoperability between applications using this specification, it is recommended that an
          SLA/agreement is in place as to what the enumeration values will be used in this file

Specification Name: OASIS CIQ TC - extensible Party Information Language Types (xPIL-types)
          Description: Defines the W3C schema that provides enumeration lists to support
          xPIL. 
          (Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
          Produced by: OASIS Customer Information Quality Technical Committee
          URL: http://www.oasis-open.org/committees/ciq
          Version: 3.0  
          Status: Committee Specification CS02
          Copyright: 2007-09, OASIS, http://www.oasis-open.org
          Last Modified: 20 September 2008
          Last Modified by: Ram Kumar, Chair, OASIS CIQ TC 
		
          NOTE: This is the schema that users can customise the enumeration lists to meet their
          exchange requirements. The enumeration values provided are ONLY SAMPLES and 
          is not complete. It is upto the application to decide what the values should be. To achieve 
          interoperability between applications using this specification, it is recommended that an
          SLA/agreement is in place as to what the enumeration values will be used in this file

Top Level item for an OASIS Emergency Data Exchange Language Hospital AVailability Exchange (EDXL-HAVE) message.

Information of the Organization that is responsible for the reporting of these facilities.

Organisation Name

Name of the organisation. E.g. ACME Inc.

Name of a subdivision of an organisation (e.g. department)

A container for all party addresses