1. UFNPT Planning and Development Work Plan, Milestones and Timelines

2. UFNPT Objectives
Objective 1 – Develop S-100 Product Specification for undersea feature names (UFN) and registering SCUFN terms in IHO Geospatial Information (GI) Registry
Objective 2 – Establish procedures for the management and registration of UFN and management of proposals made to SCUFN
Objective 3 – Provide recommendations to SCUFN on the management of UFN and use of registers to record proposals and approved names

3. S-100 Product Specification for UFN & terms registry
An S-100 product specification will contain:
Overview - Data product format
Specification scopes - Data product delivery
Data product identification - Metadata
Data content and structure - Data maintenance
Reference systems - Portrayal
Data quality - Additional information
Data capture
Based on recommendations made by the Chair of the GEBCO Guiding Committee At the Technical Sub-Committee on Ocean Mapping (TSCOM), Sub-Committee on Regional Undersea Mapping (SCRUM) meeting in 2014, a paper was submitted at SCUFN 28 by the International Hydrographic Bureau (IHB) for consideration of “Development of an S-100 Product Specification for Undersea Feature Names and Registering SCUFN Terms in the IHO GI Registry”. Initial steps for implementation of this document were made at SCUFN 29 where the formation of a SCUFN PT was created to enhance UFN products and services (HSSC8-07.1c INF3, 2016). The DRAFT ToR were accepted by the Hydrographic Services and Standards Committee (HSSC) at their 8th meeting in November The first objective of the ToR is to consider the Doc. SCUFN28-06B “Development of an S-100 Product Specification for Undersea Feature Names and Registering SCUFN terms in the IHO GI Registry”. “A data product specification is a precise technical description which defines a geospatial data product. It describes all the features, attributes and relationships of a given application and their mapping to a dataset” (S-100 Universal Hydrographic Data Model 3.0.0, 2017). A product specification will contain:

4. S-100 Product Specification for UFN and terms registry

5. Determine Geometry Requirement Determine Feature Classes
Objective 1 – Milestone 1
Determine Geometry Requirement
Vector or Coverage
Determine Feature Classes
Vector
The first requirement when building a product specification is to determine the geometry required. The schematic presented is for a product specification that incorporates both vector and coverage data. The flow for creating coverage data is on the right of the screen, and the flow for vector is on the left. For vector data, once the geometry is determined the feature classes need to be resolved.
Coverage

6. Objective 1 – Milestone 2 Content and structure of coverage
Definitions Exist
Content and structure of coverage No
Yes
Register Definitions in Appropriate Dictionary
Determine Feature Attributes
Coordinate Reference System
Continuing down the left side of the schematic for vector data, after resolving the feature classes, it needs to be determined whether or not definitions for features exist. If not, new definitions for features need to be registered in the feature concept dictionary, or if they already exist, then attributes for features can be determined. Following the flow chart on the right for coverage data, step two involves determining the content and structure or coverage and then selecting the appropriate reference system.

7. Objective 1 – Milestone 3 Product Specification Documentation
Definitions Exist
Product Specification Documentation No
Yes
Register Definitions in Appropriate Dictionary
Determine Enumerants
End
Once the attributes for features of vector data have been determined, again definitions need to be resolved and either defined and registered in the feature concept dictionary, or they already exist and enumerants can be selected. In terms of the product specification for coverage data, the product specification documentation can prepared at this point and once completed, the product specification for the coverage geometry is complete.

8. Objective 1 – Milestone 4 Determine Geometry Types
Definitions Exist No
Determine Geometry Types
Yes
Yes No
Register Definitions in Appropriate Dictionary
Bind Features & Attributes
Determine Geometry Types
After enumerants have been selected, definitions once again need to be resolved, and then features and attributes can be bound in a feature catalogue. The next step involves once again determining the type of vector geometry types that will be used.

9. Objective 1 – Milestone 5 Apply to TSMAD for Addition
Create Application Schema
Product Specification Documentation
Create Application Schema
Coordinate Reference System
If the vector geometries to be used do not currently exist in the IHO GI Registry then an application to the Transfer Standard Maintenance and Applications Development Working Group (TSMAD) will need to be made for inclusion of the geometry. However, if the geometries do exist, the application schema can then be created and a coordinate reference system selected. Finally, the product specification documentation for the vector geometry is ready to be published.
End

10. Objective 2 – Procedures for the management, registration, and proposal management of UFN
To establish procedures for the management and registration of UFN the project team will have to:
Request a register be built within the IHO GI Registry that conforms to the product specification built in Objective 1
Appoint a register manager and define responsibilities
Appoint a control body and define responsibilities
Identify eligible submitting organizations and outline eligibility criteria
Modify as necessary the existing S-100 process for proposal procedures to fit the S1-XXX product specification for undersea features
Objective two of SCUFN PT ToR is to “establish procedures for the management and registration of undersea feature names approved by SCUFN and the management of proposals made to SCUFN”. In order to accomplish this task the project team will have to:

11. Register (Undersea Feature Name) Submitting Organizations
Objective 2 – Milestone 1
Register Manager
Coordinates with:
Other register managers
Submitting organizations
Control body
Register owner
Registry manger
Register Owner
Control Body
Group of technical experts appointed by a Register Owner
Organization that:
Establishes one or more registers
Has primary responsibility for management, dissemination, and intellectual content
Submitting Organizations
Organization qualified to propose changes to content of a register

12. Procedures for the management, registration, and proposal management of UFN

13. Register (Undersea Feature Name) Submitting Organizations
Objective 2 – Milestone 2
Register (Undersea Feature Name)
Receives and reviews proposals
Check register for similar proposals
Coordinate proposals with other register managers within 2 weeks
Generate proposal management record and initiate approval process
Register Manager
Register Owner
Control Body
Decide to accept proposal without change or
Accept subject to changes negotiated with submitting organization
Specifies time limits for the control body to make decisions on proposals
Submitting Organizations
Submit proposals to registers
Negotiate with control body though register managers
Make known decisions taken on proposals by control body

14. Procedures for the management, registration, and proposal management of UFN

15. Register (Undersea Feature Name) Submitting Organizations
Objective 2 – Milestone 3
Register (Undersea Feature Name)
Register Manager
Determine proposal legitimacy and forward to control body
Assign itemIdentifier to new or superseded items
Serve as a point of contact if negotiations for proposal are needed
Register Owner
Control Body
Decide to accept proposal without change or
Accept subject to changes negotiated with submitting organization
Specifies time limits for the control body to make decisions on proposals
Submitting Organizations
Submit proposals to registers
Negotiate with control body though register managers
Make known decisions taken on proposals by control body

16. Procedures for the management, registration, and proposal management of UFN

17. Register (Undersea Feature Name) Submitting Organizations
Object 2 – Milestone 4
Register (Undersea Feature Name)
Register Manager
Serve as a point of contact if negotiations for proposal are needed
Complete/update proposal management record depending on outcome
Register Owner
Control Body
Decide to accept proposal without change or
Accept subject to changes negotiated with submitting organization
Specifies time limits for the control body to make decisions on proposals
Submitting Organizations
Submit proposals to registers
Negotiate with control body though register managers
Make known decisions taken on proposals by control body

18. Objective 3 – Recommendations to SCUFN on management of UFN and use of registers
Review the outcomes of objectives one and two and make endorsements for procedures that work or recommendations to alter aspects to better suit undersea features
Recommendations could include things such as:
Altered timelines for proposal consideration
Addition of a registered item type e.g. Affiliation (Current types Addition, Clarification, Supersession, Retirement)
Addition of a domain(s)
Inclusion of undersea features outside of SCUFN’s current mandate
Objective three of SCUFN PT ToR is to “provide recommendations to SCUFN on management of UFN and use of registers to record proposals and names approved by the Sub-committee”.

19. Next Steps
Select a Vice-Chair for the project team to assist with the objectives of the ToR and creation of an S1-XXX Product Specification
Select a Secretariat to assist with project team communication
Determine how the project team wants to divide the workload so as to achieve the ToR objectives and project milestones
Determine a regular meeting schedule for the project team
Begin work towards creating an S1-XXX for undersea feature names