<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 2 U (http://www.xmlspy.com) by Bret Champoux (Vivid Solutions Inc) -->
<!-- target namespace is a URL by popular convention.  It is an idenfitier only, such that no pysical resource is required at this URL. -->
<schema targetNamespace="http://www.for.gov.bc.ca/schema/base" xmlns:mof="http://www.for.gov.bc.ca/schema/base" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:gml="http://www.opengis.net/gml" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" version="1">
	<annotation>
		<documentation>BC MOF Base GML Types schema.  Copyright (c) 2002 BC Ministry of Forests,  All Rights Reserved.</documentation>
	</annotation>
	<!-- include MOF SimpleTypes -->
	<include schemaLocation="mof-simpleTypes.xsd"/>
	<!-- import constructs from the GML Feature and Geometry schemas -->
	<import namespace="http://www.opengis.net/gml" schemaLocation="../GML-2.12/feature.xsd"/>
	<import namespace="http://www.w3.org/1999/xlink" schemaLocation="../GML-2.12/xlinks.xsd"/>
	<!-- ========================= Custom Feature Type ========================== -->
	<complexType name="AbstractMOFFeatureType" abstract="true">
		<annotation>
			<documentation>Base type for MOF Features that provides any common MOF feature properties.  Spatial Metadata is the primary example of a common property.</documentation>
		</annotation>
		<complexContent>
			<extension base="gml:AbstractFeatureType">
				<sequence>
					<element ref="mof:spatialMetaData"/>
					<!-- ... any other common Feature properties -->
				</sequence>
			</extension>
		</complexContent>
	</complexType>
	<!-- ========================= Custom Geometry Property Type ========================== -->
	<complexType name="SingleOrMultipleLineStringPropertyType">
		<annotation>
			<documentation>Encloses a choice of either a LineString or MultiLineString geometry.</documentation>
		</annotation>
		<complexContent>
			<restriction base="gml:GeometryPropertyType">
				<choice>
					<element ref="gml:LineString"/>
					<element ref="gml:MultiLineString"/>
				</choice>
			</restriction>
		</complexContent>
	</complexType>
	<!-- ========================= MetaDataTypes ========================== -->
	<element name="spatialMetaData" type="mof:SpatialMetaDataType"/>
	<complexType name="SpatialMetaDataType">
		<annotation>
			<documentation>Type for spatial metadata properties.  Metadata fields are optional, since they are often unknown or not present</documentation>
		</annotation>
		<sequence>
			<element ref="mof:dataSource"/>
			<element ref="mof:mostRecentSourceDate"/>
			<element ref="mof:captureMethod"/>
			<element ref="mof:observationDate"/>
			<element ref="mof:dataAccuracy"/>
			<element ref="mof:description"/>
			<element ref="mof:ccsmCode"/>
			<element ref="mof:horizontalAccuracy"/>
			<element ref="mof:verticalAccuracy"/>
			<element ref="mof:horizontalDatum"/>
			<element ref="mof:verticalDatum"/>
			<element ref="mof:coordinateSystemCode"/>
		</sequence>
	</complexType>
	<element name="dataSource" type="mof:AlphaNumeric10">
		<annotation>
			<documentation>The source of the spatial data, e.g. Field Survey, Air Photos, etc.</documentation>
		</annotation>
	</element>
	<element name="mostRecentSourceDate" type="date">
		<annotation>
			<documentation>Most recent collection date of the source data</documentation>
		</annotation>
	</element>
	<element name="captureMethod" type="mof:AlphaNumeric30">
		<annotation>
			<documentation>The method used to capture the spatial data, e.g. Differential GPS, Tablet Digitizing, etc.</documentation>
		</annotation>
	</element>
	<element name="observationDate" type="date">
		<annotation>
			<documentation>The data the observation was made.</documentation>
		</annotation>
	</element>
	<element name="dataAccuracy" type="mof:NonNegativeInteger2D">
		<annotation>
			<documentation>The data accuracy percentile. Quantifies the percentage of features which are statistically expected to fall within the horizontal and vertical accuracy bounds. Ex: 95</documentation>
		</annotation>
	</element>
	<element name="description" type="mof:AlphaNumeric2000">
		<annotation>
			<documentation>A description that can be used to clarify any of the values in the spatial meta-data.</documentation>
		</annotation>
	</element>
	<element name="ccsmCode" type="mof:AlphaNumeric10">
		<annotation>
			<documentation>The TRIM CCSM code which best describes the feature.  Ex: GA9100032</documentation>
		</annotation>
	</element>
	<element name="horizontalAccuracy" type="mof:Integer3D">
		<annotation>
			<documentation>The horizontal accuracy bound.  Ex: 15</documentation>
		</annotation>
	</element>
	<element name="verticalAccuracy" type="mof:Integer3D">
		<annotation>
			<documentation>The vertical accuracy bound.  Ex: 10</documentation>
		</annotation>
	</element>
	<element name="horizontalDatum" type="mof:AlphaNumeric10">
		<annotation>
			<documentation>The horizontal datum.  Must be one of:Nad83, nad27.</documentation>
		</annotation>
	</element>
	<element name="verticalDatum" type="mof:AlphaNumeric10">
		<annotation>
			<documentation>The vertical datum.  In British Columbia most vertical data uses the Canadian Vertical Datum.  Ex: cvd28</documentation>
		</annotation>
	</element>
	<element name="coordinateSystemCode" type="mof:AlphaNumeric12">
		<annotation>
			<documentation>The system in which the coordinates are observed. Datum code will give the translations and rotations, if any. Note that datum includes the coordinate system (usually implies geodetic), the size of the reference surface (NAD 27 uses the Clark 1866 ellipsoid), the position of the reference surface (translations and rotations) and the scale difference, if any, with respect to the geocenter.</documentation>
		</annotation>
	</element>
</schema>
