You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Maps TSG are re-submitting the navPlace extension to the TRC committee after taking into account the comments from the previous review in issue #72. The two main questions that were raised in the last TRC were around the restriction of navPlace to locations on the Earth and also the use of the properties property in the GeoJSON.
The navPlace remains restricted to the Earth and the following explanation has been added to the extension:
Spatial coordinates for resources on other celestial bodies or contrived worlds can be expressed using the semantic pattern of GeoJSON. However, navPlace adopts the existing GeoJSON specification to promote interoperability with industry standard mapping libraries and methods using WGS84 as the coordinate reference system for projections of the surface of Earth. As such, expressing the location of extraterrestrial entities is not supported by the navPlace property. This extension does not preclude the development of future extensions to address this use case.
Regarding the properties in the GeoJson there was a question whether the extension should require this to be empty so as to limit the possibilities that clients would need to handle when processing the GeoJson. After investigation this was found to be too limiting and would stop the use of existing GeoJson-LD datasets being re-used without modification in the navPlace extension. A particular example of this is with the WhosOnFirst implementation. Discussion on the use of properties in the GeoJson is now covered here:
For further context on the navPlace property and the discussion on the extension please see the previous TRC issue: #72
Proposed Solution
We hope the TRC will approve this extension. We have a number of implementations and also a couple of cookbook recipes demonstrating the new features that will be shared with the TRC once this extension is approved.
The text was updated successfully, but these errors were encountered:
Links
Background and Summary
The Maps TSG are re-submitting the navPlace extension to the TRC committee after taking into account the comments from the previous review in issue #72. The two main questions that were raised in the last TRC were around the restriction of navPlace to locations on the Earth and also the use of the
properties
property in the GeoJSON.The navPlace remains restricted to the Earth and the following explanation has been added to the extension:
Spatial coordinates for resources on other celestial bodies or contrived worlds can be expressed using the semantic pattern of GeoJSON. However, navPlace adopts the existing GeoJSON specification to promote interoperability with industry standard mapping libraries and methods using WGS84 as the coordinate reference system for projections of the surface of Earth. As such, expressing the location of extraterrestrial entities is not supported by the navPlace property. This extension does not preclude the development of future extensions to address this use case.
From https://preview.iiif.io/api/navplace_extension/api/extension/navplace/#11-objectives-and-scope
Regarding the
properties
in the GeoJson there was a question whether the extension should require this to be empty so as to limit the possibilities that clients would need to handle when processing the GeoJson. After investigation this was found to be too limiting and would stop the use of existing GeoJson-LD datasets being re-used without modification in the navPlace extension. A particular example of this is with the WhosOnFirst implementation. Discussion on the use ofproperties
in the GeoJson is now covered here:https://preview.iiif.io/api/navplace_extension/api/extension/navplace/#32-context-considerations-for-geojson-ld-properties
For further context on the navPlace property and the discussion on the extension please see the previous TRC issue:
#72
Proposed Solution
We hope the TRC will approve this extension. We have a number of implementations and also a couple of cookbook recipes demonstrating the new features that will be shared with the TRC once this extension is approved.
The text was updated successfully, but these errors were encountered: