STANDARDIZATION of NAUTICAL PUBLICATION WORKING GROUP (SNPWG)

Size: px

Start display at page:

Download "STANDARDIZATION of NAUTICAL PUBLICATION WORKING GROUP (SNPWG)"

Aldous Dawson
7 years ago
Views:

1 INTERNATIONAL HYDROGRAPHIC ORGANIZATION ORGANISATION HYDROGRAPHIQUE INTERNATIONALE STANDARDIZATION of NAUTICAL PUBLICATION WORKING GROUP (SNPWG) [A Working Group of the Hydrographic Services and Standards Committee (HSSC)] Chairman: Jens SCHRÖDER- FÜRSTENBERG Vice-Chairman: Thomas LOEPER Secretary: SNPWG Letter: 04/2014 vacant To SNPWG Members Date 28 August 2014 Dear Colleagues, Subject: Simplification of the SNPWG data model on ual References: The development of the MPA and Radio Signal Product Specifications and the initial check of the S-101 ba line version came up with the need to simplify the current SNPWG data model for ual. The current SNPWG data model of ual employs the following parate complex attributes: ( uaidescription (file reference) ( Content ( The first 2 complex attributes are taken from the S-101 data model. The third attribute is being ud to cover all kinds of ual. It contains the same subattributes as the first two attributes and adds other sub-attributes which provide more about the content. While the first two attributes might be sufficient to encode which is prent on paper charts, nautical publications datats often need more expressive modeling of. On the other hand, allowing three different ways to model may be unnecessarily complicated. The simplified SNPWG approach would employ only the third method for all kinds of ual. In other words, features (and types) would bind only the Content attribute instead of, ualdescription, or Content. The full UML diagram and the revid definitions are provided in the Annex. We know that, if Content is ud everywhere, each instance of Content in a datat results in some extra overhead for data volume and data retrieval, and perhaps a little more work for the human data encoder. There might also be added complexity for portrayal rules and implementing portrayal. However, it is considered worthwhile to be tested. We expect comments, suggestions, improvements and any other contributions on the file at the latest by 30 September, Yours sincerely, Jens Schröder-Fürstenberg, Chairman

2 Annex Full Content UML data model, with examples of its u in feature and types.

3 Enterpri Architect report detailing lected items: Content «ComplexAttributeType» Package: TXTCON_INFORM_Proposal Exactly one of sub-attributes onlineresource or must be completed in one instance of Content. Product specifications may restrict the u or content of onlineresource for curity. For example, a product specification may forbid populating onlineresource. Product specification authors must consider whether applications using the data product may be prevented from accessing off-system resources by curity policies. Inherited Attributes: (none). Constraint: count( + onlineresource) > 0 Attributes (for feature and types) OR Listed Values (for enumerations and codelists) categoryoftext CATTXT onlineresource sourceindication [0..*] «ComplexAttributeType» Package: TXTCON_INFORM_Proposal categoryoftex t onlineresourc e sourceindicati on Provides ual that cannot be provided using other allowable attributes for the feature, in a defined language. The may be provided as a string in sub-attribute, or by encoding the file name of a single external file that contains the in subattribute file reference. The sub-attribute should be ud, for example, to hold the that is shown on paper charts by cautionary and explanatory notes. No formatting of is possible within the sub-attribute. If formatted is required then an associated file referenced by the sub-attribute file reference must be ud. The sub-attribute file reference is generally ud for long strings or tho that require formatting, however there is no restriction on the type of (except for lexical level) that can be held in files referenced by sub-attribute file reference.

4 Inherited Attributes:. Constraint: count( + filereference) > 0 Attributes (for feature and types) OR Listed Values (for enumerations and codelists) language INFORM ISO ISO value A non-formatted digital string. The attribute should be ud, for example, to hold the that is shown on paper charts by short cautionary and explanatory notes. Therefore populated in must not exceed 300 characters. Text may be in English or in a national language defined by the attribute language. No formatting of is possible within the sub-attribute. If formatted, or strings exceeding 300 characters, is required, then the attribute file reference must be ud. filereference FILREF The string encodes the file name of a single external file that contains the. The attribute file reference is generally ud for long strings or tho that require formatting, however there is no restriction on the type of (except for lexical level) that can be held in files referenced by sub-attribute file reference. filelocator FILLOC The string encodes the location of a fragment of or other in a support file. Application schemas must describe how the associated file is identified. The associated file will commonly be named in a file reference co-attribute of the same complex attribute. Each DCEG must specify requirements for the format of the associated file and the mantics of file locator. For example, the value of file locator may be an HTML ID in an HTML file, line number in a file) or a bookmark in a PDF file. headline HEADLN Words t at the head of a passage or page to introduce or categorize

5 categoryoftext «enumeration» Package: MPADomain Inherited Attributes:. Attributes (for feature and types) OR Listed Values (for enumerations and codelists) abstract or summary extract full 1 A statement summarizing the important points of a. 2 An excerpt or excerpts from a. 3 The whole

Paper for consideration by TSMAD Data Quality Model Harmonization

Paper for consideration by TSMAD Data Quality Model Harmonization TSMAD29/DIPWG7-11.7A Submitted by: Executive Summary: DQWG and SNPWG This paper updates TSMAD on the data quality model for nautical charts