NOTICE: An analysis of alternatives for internationalized text is available for review and comment in https://htmlpreview.github.io/?https://github.com/opengeospatial/poi/blob/main/21-049/Internationalized_Text.html[HTML] and https://github.com/opengeospatial/poi/blob/main/21-049/Internationalized_Text.pdf[PDF]
This repository is the development space for the draft OGC Point of Interest (POI) Part 1: Conceptual Model Standard. Development of this Standard is taking place in the 21-049 directory. The current draft is available in https://docs.ogc.org/DRAFTS/21-049.html[HTML] and https://docs.ogc.org/DRAFTS/21-049.pdf[PDF] formats.
This Standard is accompanied by a Users Guide. Development of the Users Guide is taking place in the 22-053 directory. The current draft is available in https://docs.ogc.org/DRAFTS/22-053.html[HTML] and https://docs.ogc.org/DRAFTS/22-053.pdf[PDF] formats.
The draft OGC Point of Interest (POI) Part 2: JSON Encoding Standard defines how the POI Conceptual model should be implemented in JSON. Development of this Standard is taking place in the 23-045 directory. The current draft is available in https://docs.ogc.org/DRAFTS/23-045.html[HTML] and https://docs.ogc.org/DRAFTS/23-045.pdf[PDF] formats.
This repository also contains legacy files about and for the purpose of developing the PoI specification(s).
These files are from the following sources:
All contents of this repo beginning from when it was created by the transfer of work from the W3C to end of 2014 when the activity of the POI SWG stopped. These files were moved into a https://github.com/opengeospatial/poi/tree/main/POI-repo-files-Pre-2014[dedicated folder] in order to preserve the prior work of the OGC POI SWG. At the same time as the files were put into their folder on this repo, all the issues created prior to the end of 2014 are labelled and closed.
https://github.com/opengeospatial/templates[OGC Templates GitHub Repository] This is the origin of one file at the top level of this repo, the https://github.com/opengeospatial/poi/blob/main/Draft_PoI_SWG_charter.adoc[Draft PoI SWG charter template]
A folder containing the template for the new POI draft specification.
OGC uses Metanorma software for creating Standards documents.
You can compile documents using either a local installation of Metanorma or optionally a docker-containerized instance of Metanorma.
Confirm that you have Metanorma installed locally on your operating system. If you do not have Metanorma installed, follow the steps at the Metanorma website to install it.
Step 1. Obtain the template for a Draft OGC Standard from the template sub-folder.
Now that you have obtained a copy of the template, you can edit the document. The following steps assume that you have read the authoring guidelines are at https://www.metanorma.org/author/ogc/authoring-guide/
Step 2. Next, edit the asciidoc file document.adoc by filling the document properties: docsubtype, status, abbrev, edition (i.e. version of the document), docnumber (OGC Document Number), keywords, fullname (of the editors).
Step 3. Ensure that the doctype property is set to standard.
Refer to the authoring guidelines for the complete list of document properties.
NOTE: If there are multiple editors, the names of the editors are listed in the sequence fullname, fullname_2, fullname_3,...
To convert the draft document from asciidoc format to HTML and PDF formats, we use the metanorma software to compile the document.
Step 4. From the folder containing the document.adoc file, run the following command.
metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc
NOTE: You need to add this option to retrieve licensed fonts --agree-to-terms
Confirm that you have docker installed on your operating system. If you do not have docker installed, follow the steps at the Get Docker page to install it.
The template for Standards documents is organized as a folder of asciidoc files, with nested folders for sections, abstract tests, requirements and other resources.
To create a copy of the template, follow these steps.
Step 1. Pull the latest version of the Metanorma image on to your local docker installation.
docker pull metanorma/metanorma:latest
Step 2. Generate a copy of the template for OGC Standards by running the following command from a terminal (i.e. from the command prompt).
docker run --rm -v "$(pwd)":/metanorma metanorma/metanorma metanorma new -d standard -t ogc -l https://github.com/metanorma/metanorma-templates-ogc folder_for_standard
NOTE: The -d standard -t ogc flags instruct metanorma that the template is for OGC Standards.
NOTE: The folder_for_standard value can be replaced with whatever you would like to be the name of the folder that contains the copy of the template.
Now that you have generated a copy of the template, you can edit the document. The following steps assume that you have read the authoring guidelines are at https://www.metanorma.org/author/ogc/authoring-guide/
Step 3. Next, edit the asciidoc file document.adoc by filling the document properties: docsubtype, status, abbrev, edition (i.e. version of the standard), docnumber (OGC Document Number), keywords, fullname (of the editors).
Step 4. Ensure that the doctype property is set to standard.
Refer to the authoring guidelines for the complete list of document properties.
NOTE: If there are multiple editors, the names of the editors are listed in the sequence fullname, fullname_2, fullname_3,...
To convert the draft standard from asciidoc format to HTML and PDF formats, we use the metanorma software to compile the document.
Step 5. From the folder containing the document.adoc file, run the following command.
docker run -v "$(pwd)":/metanorma -v ${HOME}/.fontist/fonts/:/config/fonts metanorma/metanorma metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc
NOTE: You need to add this option to retrieve licensed fonts --agree-to-terms