...
- datatypes.xsd - the data elements that are definitions of atomic data types. That is, the elements that are made from raw data types, and cannot be broken down further. Examples are the landing report id data element, and the weight data element. They contain data, but not structure. Atomic data elements may have attributes. For example, the condition code data element is a simple number containing the code, such as 1. The condition code data element has a attribute for _name-, which contains the name of the condition.
- dateelements.xsd - commonly used data elements that hold groups of individual elements, and that are used in multiple types of reports. For example, the cfec_permit data element, that is made up of the fishery, permit number, and year sequence. The data_elements may have both required and optional elements. While the XML schema defines elements as optional, the eLandings business rules determine when elements are required for particular reports.
- landingreport.xsd - the landing report data element definitions.
- productionreport.xsd - the production report data element definitions.
- logbook.xsd - the electronic logbook data element definitions.
The eLandings system includes other XSD files that provide data element definitions that are used internally. Interfacing systems do not need these data elements.
XML Definitions for Interfacing Systems
The XML elements that are needed for system interfaces are
The landing_report XML definition defines landing report data files that are extracted from eLandings and imported to another system. It is also used for files that are prepared by an external system and submitted to eLandings. Elements of the landing_report document and their usage are defined on the Landing Report Data page.
...