ISO 28005-2 pdf free download
ISO 28005-2-2021 pdf free download.Ships and marine technology一 Electronic port clearance (EPC)一 Part 2: Core data elements.
4.7 Principle for creating a message file with core data elements
Clauses 5 to Z of this document define data types that can be used to construct core data elements. Annex A defines how each core data element shall be defined from the data type. Any selection of core data elements can be used to generate an XML message for exchange of information between ship and shore. ISO 28005-1 specifies how the message shall be constructed and how messages are exchanged.
4.8 Structure ofdata type definitions
4.8.1 General
Each data type is defined in a separate subclause, the structure ofwhich is descibed in 4.8.2 to 4.8.5.
4.8.2 Clause and data type name
All data types defined in this document are given a name that is also included as the first part of the heading for the subclause where the data type is defined.
The data type name follows the specifications for XML tag names[1], with the following additional constraints.
a) The name shall always end with the string “Type”.
NOTE 1 Some core data elements can also have the ending ‘1pe’. In that case, the corresponding core data type has the postfix 1ypeTypeN.
b) Enumerated data types shall have the postfix “ContentType”.
c) This document uses the “Upper Camel Case” in all core data types, i.e. the first letter is upper case and, when the tag name consists ofa number ofconcatenated words, each ofthe words starts with an upper case letter.
d) The name consists only ofcharacters from the sets (A-Z), (a-z) and, exceptionally, (0-9).
NOTE 2 The names have been selected to be generally understandable in the context of ship-to-shore communication for port clearance. The names are in normal British English without any special characters. Names are in singular form except where the data element contains a list of items, in which case the tag name is in plural form.
4.8.3 Definition
Each data type has a definition that is intended to give an unambiguous description of what the data element shall contain and in what context it is valid. This is the first paragraph after the heading of the clause.
4.8.4 Type defined as XSD code
Each data type is defined as a section ofXSD code. This section only covers the actual data type definition and is not a valid XML document in itself. Annex S gives a brief overview of the syntax elements used, but the user ofthis document should refer to Reference [1k] for the definitive descriptions.
NOTE The XSD code has been generated automatically and, as the order ofchild elements in XSD is important and cannot arbitrarily be changed, the ordering in the XSD code is the generated order, and is not always logical.
4.8.5 Representation
Additional information about how the data field shall be formatted is contained in the representation paragraph. This can give, for example, the normative reference to the official sources of enumeration codes.
4.9 Principles for defining enumerated types
Enumerated types, i.e. types that are associated with a fixed set 01 coae values, are detined in one ol three ways.
a) When the code set is small, and not defined and maintained by parties external to this document, the allowed code values are listed in the definition of the data type as XSD constraints.
NOTE 1 For an example of inline listing of enumerated types, see type definition for TimeTypeContentType in 6.13.
b) If the code set is larger, and not defined and maintained by parties external to this document, the code set is included in a normative annex, e.g. Annexes D to 1.
NOTE 2 The definition of the enumerated types can use the same principle as described in item a) above or as an external file as described under item c).
c) When the code set is maintained by an external party, the data type only defines the data type as a token and makes a reference to where the code set can be found and how the code set shall be used in the core data element. An informative annex contains a list of some of the most common codes, e.g. Annexes J to N. Subclause 4h can be used to encode the values in XML or the code set can be included in an XSD file for direct validation of XML messages.
4.10 Character sets for data fields
This document allows all character sets that are supported by XML (see 4.5). Additional restrictions can be specified in the representation part of the data type definitions.
4.11 No use of XML attributes
The data types defined by this document do not use XML attributes. All information is contained within XML start and stop tags.
4.12 Empty tags
Mandatory tags, i.e. tags that are not marked with minOccurs=”O”, shall normally contain valid data. Tags that are optional may be left out of the message, may be empty, i.e. have no end tag, or may have empty content. The receiver of messages shall treat all forms of empty or missing tags the same.
4.13 Defaults for minOccurs and maxOccurs
According to Reference [1], the default values for minOccurs and maxOccurs equal 1. This is used in some parts of ISO 28005 to shorten the type specifications in the data type definition clauses.
4.14 Order of child elements in XSD templates
The XSD templates uses “<xs:sequence>” to list child elements. This means that the XML file shall have child elements in exactly the same order as the XSD code. Optional child elements (minOccurs=”O”) can be omitted.
NOTE The XSD code is automatically generated and the order of child elements is not always logical.ISO 28005-2 pdf download.
