| | 19 | The implementation of the Information Model is referred to as ebXML Object Model. It consists of a set of Java Beans representing the objects in the specification mentioned above. Where there are discrepancies between the specification and the XSD mentioned above, preference was given to the definition in the XSD. See [wiki:ebXMLSpecificationXSDDiscrepancies here] for a list of these. |
| | 20 | |
| | 21 | The implementation is structured in the following packages, largely corresponding to the specification: |
| | 22 | |
| | 23 | * org.geonetwork.ebxml.informationmodel.association |
| | 24 | * org.geonetwork.ebxml.informationmodel.classification |
| | 25 | * org.geonetwork.ebxml.informationmodel.cooperatingregistries |
| | 26 | * org.geonetwork.ebxml.informationmodel.core |
| | 27 | * org.geonetwork.ebxml.informationmodel.core.datatype |
| | 28 | * org.geonetwork.ebxml.informationmodel.event |
| | 29 | * org.geonetwork.ebxml.informationmodel.provenance |
| | 30 | * org.geonetwork.ebxml.informationmodel.service |
| | 31 | * org.geonetwork.ebxml.informationmodel.xsd |
| | 32 | |
| | 33 | All of these packages correspond to a section in the specification except the org.geonetwork.ebxml.informationmodel.xsd package, which contains Java Beans to assist in representing XSD datatypes that have no equivalent in the Java language, such as xsd:duration. |
