|
|
SEF, Schema & Types, a brief overview
The Xml schema that EDIXMLOnline generates from the SEF is comparatively similar
or identical.
The root node of the xml document is EdiDocument. Notice how the TransactionSet
element is of the PurchaseOrder type (above).
Getting familiar with the nomenclature
In general, you will notice that the name of the types and elements in the schema
is pretty much the same as the descriptions of the datasegments and dataelements
in the SEF file, with special characters removed.
The LOOP segment of the SEF, are identified in the schema with a an "ArrayOf" prefix
of the description of the first segment appearing in the loop.
e.g.
For the "PO1" loop you will see "ArrayOfBaselineItemData"
Naming of Types
Any element that can occur more than once in the document is derived from an intermediary
type whose name is prefixed with "ItemFor". See element 2 and 3 above.
Any element that can only occur a maximum of once does not derive from an intermediary
type. See element 1 above.
The intermediary type further references the actual schema type that represents
the element structure.
e.g.
See, again, how the "BaselineItemData" closely resembles its counter part in the
SEF file.
You can easily trace the definitions of element types within the WSDL file.
Caveats
If there are multiple datalements that occur within the same datasegment they will
be renamed in the schema and have a sequential number appended to it.
Class names come from schema types names
The proxy class generators of some development tools like Visual Studio and NetBeans
extrapolate the name of the class(es) based on the name of schema type. In the example
below, notice how the Interchange and the Functional Group classes are named. They
are identical to their schema types, but without special characters.
|
|