BC MOF FSP Submission schema for use in the Electronic Submission Framework. Copyright (c) 2006 BC Ministry of Forests, All Rights Reserved. Mandatory: Incorporates GML bounding data for GML FeatureCollection type. May be set to null Mandatory: metadata and content of an FSP submission. Top level specification of FSP submission via ESF Conditional: contact name for submitting licensee. Must always be present except for partial submission Conditional: phone number of submitting licensee contact. Must always be present except for partial submission Conditional: email address of submitting licensee contact. Must always be present except for partial submission Mandatory: indicates the number of ESF attachments to be considered as part of this submission. Initial submission must attach a legal FSP document. Value may be 0 or more. Mandatory: Instance of the submission item--a single Forest Stewardship Plan Removes generic gml:featureMember property. Specifies the data for a FSP Conditional: must be present in amendment submissions Conditional: must be present when updating an amendment submission Conditional: must be present in original submission Optional: name supplied by licensee for an amendment Mandatory: set to "I" (Input) for first-time submission; set to "U" if updating FSP in Draft mode; set to "R" for Amendment submission. Conditional: FSP may involve one or more licensees. Must supply for original submission or if license holders in FSP change Optional: Length of plan in years. Defaults to 5 years, but Licensee may specify Optional: Additional months in plan duration beyond planTermYears. Must not occur if planTermYears is not present. Cannot occur if planTermExpiry is present Optional: date on which the FSP should expire. If planTermYears is present, cannot submit planTermExpiry Conditional: One or more MoFR districts responsible for administration of this FSP. Must always be present except for partial submission Mandatory: 'false' for original FSP submission; 'true' if this submission is an FSP amendment Optional:Comment describing what is being amended for this submission. Conditional: Must supply if submission is an FSP amendment; 'true' if his amendment requires ministry approval; 'false' if approval not required Optional: Set true if attached legal document is consolidated (includes all previous amendment information) Optional: set true if this amendment modifies the existing FDU spatial data. Optional: set true if this amendment modifies the existing identified area spatial data. Optional: set true if this amendment modifies the existing stocking standards. Optional: set true if this amendment makes use of the roll-over guidelines outlined in the Forest and Range Practices Act, Section 197. Mandatory: set to true if this is a transitional FSP; else set to false Conditional: 1 or more Forest Development Unit elements must be submitted before plan can be approved Conditional: original submission must contain 1 or more Stocking Standard elements Optional: 1 or more identified areas may be submitted as part of an FSP or amendment. Composition association to a Plan Holder data object. Mandatory: licensee MoFR client Code Composition association to a District Code data object. Mandatory: MoFR code for Org Unit containing FSP Association to an FDU Feature. Specification of a Foreset Development Unit Specifies Forest Development Unit type Mandatory: an FDU must have a name Conditional: list of forest licences with obligations within this FDU; must be provided except for BCTS Mandatory: specifies the spatial boundary of the FDU Composition association to a License data object. Forest license number of obligation holders within this FDU Composition association to a Standards data object. Conditional: a list of pre-existing Stocking Standard IDs May submit SSID of stocking standards already in RESULTS database Conditional: a list of Stocking Standards proposed specifically for this FSP New standards, specific to FSP Specifies the data for a proposed stocking standard Association to an identified area list. Specification of an Identified Area/documentation Specifies Identified Area type Mandatory: an Identified Area must have a name Identifies legislation under which Identified Area is submitted: one of: FRPA196(1), FRPA196(2), FPPR14(4) Optional: specification of an Identified Area Composition association to a BGC data object. Composition association to a standards layer data object. Specifies one layer of a stocking standard Describes submission as (I)nsert or (U)pdate or (A)mendment