_Meeting Minutes

[geofizzydrink]

Minutes 2022-05-05

Participants

Matthew Purss
Nazih Fino
Rehrer, Sarah
Howard Trickey
Amy Youmans
Charles Heazel
Joetta Kreck
Koen De Baets
Abdoulaye Diakite
Christine Perey
Fleming, Ryan
Ryan Fleming

Meeting Started 09:30 EDT

Draft Agenda

• We’ll continue to examine the model and discuss updates in GitHub.

• Hope Chuck will have time in the next 12 hours to do some updates!

Key Discussion Points

• Chuck - not much further progress on POI data model, has been working with indoorGML.

• working to build asciidoc mostly from the data model.

• The role of time.

  • time aspects of the target feature vs time aspects of the poi (as a digital thing/object)
  • expiration time must be required but can be filled with "inf" or "not defined" for use cases where we don't know how long the POI will be supported/needed.

• Symbology is important (but a can of worms). Symbology needs to be an aspect of the core data model (actually it should be the methods/mechanism/rules around assigning/applying symbology to a POI rather than the actual symbols themselves).

Actions

• Chuck to continue elaborating the data model
• Everyone to take a look at the styles spec to continue the symbology discussion in a way where we minimise re-inventing the wheel.

Meeting Closed 10:35 EDT

---

---

Minutes 2022-05-19

Participants

Matthew Purss
Howard Trickey
Christine Perey
Charles Heazel
Koen De Baets
Kyoungsook Kim

Meeting Started 07:30 EDT

Draft Agenda

• We’ll continue to examine the model and discuss updates in GitHub.

• Hope Chuck will have time in the next 12 hours to do some updates!

Key Discussion Points

• Chuck - updated the data model work - no drastic changes of note. Has been working on the JSON encoding of the Hotels Feature Collection of POIs to ensure consistency can be ensured between the JSON type of encoding of a POI and other JSON encodings of the wider Feature Model.
• June Members Meeting - Looks like Scott/Greg have moved the POI SWG session to 1630-1715 (Madrid local time) on the Tuesday (from 1630 Wednesday). This works better for most people. Chuck will be busy with the CITE SC for the first half session, but he will be able to attend and present a status update of the model during the second session (NB: the Tuesday pm session is split into 2x 45 min sessions)
• Agenda setting for June Members Meeting:
  • open/intro/logistics -5min
  • Update on Model - Chuck (latter session) - ~20 or 30min
  • Temporal considerations (first session - Matt to lead discussion) - ~20min (could be compressed if needs be)
  • Digital Twin presentation/discussion????? -- It will be great if we can have a couple of POI Digital Twin - probably urban setting - examples one or more members have done recently to overtly tie into the overall Digital Twin theme for the wider Members Meeting. (depending on response from SWG members this could be from 10min to 30min).
  • Other business - 5min

Actions

• Chuck to continue elaborating the data model
• Everyone to take a look at the styles spec to continue the symbology discussion in a way where we minimise re-inventing the wheel.
• Matt to put together a few slides regarding the temporal issue
• Matt to send out an email calling for presentations of POIs in a Digital Twin context.

Meeting Closed 08:25 EDT

---

---

Minutes 2022-06-09

Participants

Matthew Purss
Howard Trickey
Christine Perey
Charles Heazel
Koen De Baets
Kyoungsook Kim

Meeting Started 07:30 EDT

Draft Agenda

• We’ll continue to examine the model and discuss updates in GitHub.

• Hope Chuck will have time in the next 12 hours to do some updates!

Key Discussion Points

Actions

Meeting Closed 08:25 EDT

---

---

Minutes 2022-06-30

Participants

Matthew Purss
Charles Heazel
Francois Fischer
Joetta Kreck
Fleming, Ryan J CTR (USA)
Howard Trickey
Koen De Baets (Digitaal Vlaanderen - Belgium)
Amy Youmans (AGC)

Meeting Started 07:30 EDT

Draft Agenda

1. Recap from the June OGC Members Meeting
   

2. Data Model Update - Chuck
   

3. Use case Discussion/Exploration
   

4. (Possible) Early Scoping of the Standard Specification Document Drafting activity (if we are all happy that the data model is sufficiently well developed).
   

5. Schedule of POI SWG telecons for the next quarter.
   

6. Other Business
   

Key Discussion Points

• No additional work has been done on the Data Model (Chuck has been on holidays).
• Chuck provided an overview of where we are up to with the Data Model
• Matt provided an overview/update on what was discussed covered during the June Members Meeting POI Session
• Matt tabled an email he received from Jean-Christophe Malapert (Centre National d'Études Spatiales - CNES) with some very well conceived and thought provoking questions about the Draft POI Standard and POIs in general.
  • These questions were discussed in turn and will be included as issues on the POI github repository.
• Matt asked the group if they were happy with the current schedule of meetings. The unanimous view was that the current day/time and tempo of meetings was good for everyone.

Actions

• Matt to post the questions posed by Jean-Christophe as issues in the POI Github repository.
• Matt to schedule and send out calendar invites for POI meetings during the next quarter.

Meeting Closed 08:42 EDT

---

---

Minutes 2022-07-06

Participants

Matthew Purss
Joetta Kreck
Fleming, Ryan J CTR (USA)
Howard Trickey
Amy Youmans (AGC)

Meeting Started 07:30 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• Brief discussion of github issues related to use case scenarios.
• The concept of aggregation of POIs to enable efficient and simple filtering for portrayal purposes (either by semantic or spatial/zoom level/Distance classification) was raised by Joetta.
• The issue of POI geometries straddling the antimeridian was discussed. There are ways (although they are messy) of dealing with this issue using the current Feature Model. Also, referencing the geometry by DGGS ZoneIDs is another way to get around this issue - DGGS (and their ZoneIDs) are not limited by the effects of the antimeridian - i.e. there is no discontinuity in ZoneIDs across the antimeridian like there is with coordinate representations.
  • Moving Features will present a challenge as they cross the antimeridian. A potential workaround, again, could be to use/tag the moving feature (and it's location in space-time) to the zoneIDs of a DGGS.

Actions

• Joetta to post her POI aggregation use case to github (and Chuck) to test if the current Data Model can adequately fulfil that use case or whether there needs to be some additional field(s)/construct(s) included in the data model to do so.

Meeting Closed 08:08 EDT

[geofizzydrink]

---

---

Minutes 2022-07-14

Participants

Matthew Purss
Fleming, Ryan J CTR (USA)
Howard Trickey
Amy Youmans (AGC)
Chuck Heazel
Christine Perry

Meeting Started 07:30 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• Matt provided a brief update of the discussions we had during last weeks telecon.
• Chuck provided an update on the Data Model. There are two principle conformance classes - one that describes the underlying feature object that the POI represents; and, another that describes the POI Feature itself.
• Howard raised the valid concern regarding the apparent complexity of the data model in terms of potential uptake from developers. Chuck pointed out that while the data model for POI has some complexity to it, because it makes extensive use of the feature data model, this is different to the usability of implementations of the feature data model (e.g. most GIS software include an implementation of most, if not all, of the feature model but when people use those implementations much of the complexity is hidden from view).

Actions

• Group: we should all test out the data model and json schema implementations to validate the Data Model against the identified POI use case scenarios.
• Christine to create a Google Doc to plan a circular message requesting people to test and validate the data model. The aim is to have some feedback from validation testing ahead of the next OGC Members Meeting.

Meeting Closed 08:23 EDT

[geofizzydrink]

---

---

Minutes 2022-07-22

Participants

Matthew Purss
Fleming, Ryan J CTR (USA)
Howard Trickey
Amy Youmans (AGC)
Chuck Heazel
Christine Perry
Joetta Kreck

Meeting Started 07:30 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• Howard raised the valid concern regarding the apparent complexity of the data model in terms of potential uptake from developers. We need to understand and evaluate how easy it is for developers to implement this data model as is to meet their use case requirements vs having to drill down into the underlying standards in order to implement aspects of the POI data model. For example, various ways one might represent and aggregate time constructs in relation to a POI - how far down the rabbit burrow of temporal standards do they need to go in order to adequately represent temporal aspects of POIs.
  • As far as the POI standard goes this issue can be addressed (at least for some common use case scenarios) as part of the informative "best practices" content we can include in the POI standard specification document. Hopefully, to provide the reader/implementer with tangible examples of how this standard can be implemented against some common use cases. This informative text will likely provide a useful starting place for an implementer to begin the process of implementing their specific use case (which might be different to the examples we publish with the standard).

Actions

• Chuck: the asciidoc content on the github repo to reflect the current state of the UML model
• Christine: work with Scott Simmons to schedule the OGC POI Briefing Webinar
• Christine: to engage with Greg and/or Gobe regarding the metanorma workflow to generate the pdf/html versions of the draft standard from the asciidoc content/template that is already on the github repo.
• Group: we need to make sure we are happy with abstract for OGC POI Briefing Webinar before the notice is sent out to the OGC and wider community.
• Group: Contribute to the use case examples google doc Christine has shared with the group.

Meeting Closed 08:30 EDT

[geofizzydrink]

---

---

Minutes 2022-08-04

Participants

Matthew Purss
Francois Fischer
Howard Trickey
Chuck Heazel
Koen De Baets

Meeting Started 07:30 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• Koen - CI_Address component ISO 19115 - can we split street name & street number (+ maybe also split unit number)?
• Chuck - we can both extend and restrict the standard fields/elements under the standard. The standard has be the baseline (lowest common dominator) but it can be extended. In the UML model POI_Property can include "additional attributes". Can also have many POI_Properties.
• Howard - main use case - interchange between POIs. Current standard not doing this comprehensively.
  • Chuck - What additional properties do we need to standardise? we can't do them all but we can define those additional properties that we all agree need to be specifically defined.

Actions

• Howard to post a github issue on the POI interchange use case

Meeting Closed 08:10 EDT

[geofizzydrink]

---

---

Minutes 2022-08-11

Participants

Matthew Purss
Francois Fischer
Howard Trickey
Chuck Heazel
Koen De Baets
Christine Perry
Amy Youmans (AGC)

Meeting Started 07:30 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• Chuck led us through the current updates to the POI Specification Document. There are still some issues with autogenerating specification elements from the data model for "subsections". Chuck is looking into how to resolve this. Chuck has requested the SWG to download the MSWord version of the draft spec and using tracked changes mark up the current draft version to send back to him to capture and implement/resolve changes in the github "single point of truth" content.
• Howard + others - discussion on the interchange related github issue Howard posted (Are more POI properties needed to be standardized for the POI data interchange use case? #70). Are we able to encode all of the identified fields using the POI Data Model and its supporting standards? It appears so.
  • how do we provide guidance to implementers on how to apply the general POI data model to their use case scenario?
    • Potential options include:
      1. We constrain the general POI Data Model to meet these requirements - at the risk of reducing the wider use of the POI standard.
      2. We keep the general POI Data Model as is and include an informative section/annex that describes, with examples, how to apply the POI Data Model to specific use case scenarios.
      3. We keep the standard as is and write a companion "User Guide"/"Best Practices" document that describes the application of the POI Data Model - in more detail and depth than that of option 2.
      4. We define the general POI Data Model as the "Core" Conformance Class, and then include a number of optional conformance classes that normatively define how the "core" data model is to be applied to specific use case scenarios.

Actions

• MP to post the question to the SWG regarding - single general conformance class vs core conformance class + additional domain specific specialisation conformance classes.
• SWG to review the MSWord version of the draft POI spec and send any suggested changes back to chuck to implement.

Meeting Closed 08:22 EDT

[geofizzydrink]

---

---

Minutes 2022-08-18

Participants

Matthew Purss
Francois Fischer
Howard Trickey
Joetta Kreck
Koen De Baets
Amy Youmans (AGC)
Chuck Heazel
Christine Perey

Meeting Started 07:30 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• MP overview of last meeting.
• CP reached out to Ronald Tse (Ribose) re engagement with POI SWG - particularly around time encodinds (e.g. Standardising Business hours for POIs).
• CH has been working on metanorma integration - no updates to POI data model or spec.
• MP - October Members Meeting
  • Are anyone from the SWG going to be in Singapore? (it appears No)
  • CP do we really need a "face-to-face" meeting in October given our current tempo and progress? (it appears No)
  • AY - no real need for October "face-to-face"; however, these sessions do present a good outreach opportunity - Is that enough of a meeting to hold a session.
• CP - POI webinar preperations...
  • Our call to action appears to be ready https://docs.google.com/document/d/1SyvZewdtW8xfy3fW8xhjVWgt6lyroaGauUGCF6DIuyc/edit
  • We have a draft Spec - Is it ready to expose to a friendly audience?
  • When do we do the webinar?
  • Do we hold the webinar in conjunction with, or just before the October meeting? or, do we bring it forward a few weeks ahead of the October meeting or push it until a few weeks afterwards?
  • We NEED to have OGC marketing of this to make it a real success. We need have a conversation with OGC staff as to the best time to market and hold the webinar?
  • Scott raised the question: what "best/least worst" time of day for the webinar. Where do we expect the majority participants to be based?
    • why not have two webinar sessions - one EU morning/midday'ish and one Asia Pacific/US morning/midday'ish.

Actions

• MP to post the question to the SWG regarding - single general conformance class vs core conformance class + additional domain specific specialisation conformance classes.
• SWG to review the MSWord version of the draft POI spec and send any suggested changes back to chuck to implement.
• CP to get in touch with Scott re: preparations for webinar.
• MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo.

Meeting Closed 08:32 EDT

[geofizzydrink]

---

---

Minutes 2022-08-25

Participants

Matthew Purss
Koen De Baets
Howard Trickey
Chuck Heazel
Christine Perey
Francois Fischer

Meeting Started 07:35 EDT

Draft Agenda

1. Update on Data Model Development
   

2. Update/Discussion on use cases and their alignment with the Draft Data Model
   

3. Update/Discussion on POI Implementation Standard Drafting activities
   

4. Other Business
   

Key Discussion Points

• MP provided a brief overview of what we discussed in our last meeting
• CP raised the issue that although we have been getting some positive engagement with OGC Staff (via Scott directly), key OGC staff we will be relying on to help us get the webinar/workshop over the line have not yet responded to emails from CP.
• MP raised the issue of a Pull Request submitted by Kunlin Yu (Syrius Robotics) which we need to resolve some conflicts with the Master Branch. CH agreed to look at the Pull Request, verify if it indeed needs to be applied, and, if so, resolve the conflicts to implement the PR.
• MP stepped through the open issues - Some of these we have resolved (both through discussion and the data model/spec) and so the issues need to be closed. Others still need more consideration - MP to clean up the open issues list accordingly.

Actions

• SWG to review the MSWord version of the draft POI spec and send any suggested changes back to chuck to implement.
• MP to invite Ronald Tse to next weeks POI SWG to help foster the continued discussion regarding standardised representations of business hours from the perspective of a POI.
• MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo.
• MP to post the question to the SWG regarding - single general conformance class vs core conformance class + additional domain specific specialisation conformance classes.

Meeting Closed 08:35 EDT

[geofizzydrink]

---

---

Minutes 2022-09-08

Participants

Matthew Purss
Koen De Baets
Howard Trickey
Francois Fischer
Ryan Fleming
Christine Perey
Chuck Heazel

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP provided a brief overview of what we discussed in our last meeting and the Current set of Action Items.
• CP provided an update on her engagement with OGC staff re: the preparation and scheduling of the POI Webinar/Workshop. Prospective dates are 22 September or 27/28 October. Selection of a Date for the webinar is contingent on the draft POI spec + supporting documentation being ready in time to circulate with prospective participants at least a week in advance.
• MP highlighted some of the issues observed in the current version of the draft spec - most of which appear to be issues related to the translation of information from the POI Data Model to the published document formats. CH will work on resolving these issues ASAP.
• CH informed the SWG that he would be severely time constrained during September and the lead-up to the OGC Members Meeting in the first week of October. So it will be much more realistic and achievable for us to aim for holding the webinar/workshop(s) on 27/28 October (one during EU daytime and one during US/Asia Pacific daytime).
• MP offered to help tidy up some of the non-data model related parts of the draft POI spec document (e.g. Terms & Definitions)
• FF/KDB mentioned that it would be useful to generate some "real-world" example POIs using the draft Data Model to serve as a focus for discussion during the workshop(s) on the adequacy of the ISO derived POI data model and whether there needs to be changes or extensions made to it in order to meet the requirements of the typical POI use case scenarios.
• MP/CH raised the question of in the final POI spec do we have a mandatory conformance class "Core" (i.e. the core general POI data model) plus a set of optional conformance classes in the same document that describe and validate the different encodes of the "Core" data model (e.g. JSON, XML, GML encodings etc...). There was general (but not overwhelming) support for this idea. A possible alternative will be to have a POI - Part 1: Core Spec and a POI - Part 2: Encodings set of documents. It was agreed that we will work towards defining these conformance classes and make a final decision regarding the overall document structure at a later date.

Actions

• MP to invite Ronald Tse to next weeks POI SWG to help foster the continued discussion regarding standardised representations of business hours from the perspective of a POI.
• MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo.
• CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• MP to tidy up some of the non-Data Model components of the draft POI spec.
• CH to validate the GeoJSON POI schema to make sure that it still conforms to the draft Data Model.
• SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model.

Meeting Closed 08:30 EDT

[geofizzydrink]

---

---

Minutes 2022-09-15

Participants

Matthew Purss
Joetta kreck
Christine Perey
Howard Trickey
Chuck Heazel
Koen De Baets

Francois Fischer
Ryan Fleming
Chuck Heazel

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP provided a brief overview of what we discussed in our last meeting and the Current set of Action Items.
• CH updated the GeoJSON POI schema and confirmed that it still conforms to the draft Data Model.
• SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model.
  • KDB - will check and validate Hotels POI example
  • HT - will check and validate the Interchange POI Use case
  • CP we should create a space on the portal to collect material for the webinar/Community Briefing (MP Done https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265).
  • CP would be good to show a Moving Features/Objects POI use case example in addition to the Hotels and Interchange examples. Maybe some military examples (Joetta may have something).
  • Rough order of the briefing
    • overview and intro of the draft spec (~15 min)
    • presentation of 3 example use case scenarios (all leveraging the draft spec) (~30 min - ~10min per example)
    • discussion + Q&A (~15 min)

Actions

• MP to invite Ronald Tse to next weeks POI SWG to help foster the continued discussion regarding standardised representations of business hours from the perspective of a POI.

• MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo.

• CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.

  • CH will work at manually fixing the Data Dictionary entries in the draft spec ahead of the Briefing.

• MP to tidy up some of the non-Data Model components of the draft POI spec.

• SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model.

  • KDB going to do some work on the Hotel use case example
  • HT going to do some work on the Interchange use case example
  • (we will need to maybe do a request of SWG members) to do some work on a Moving Features use case Example.
  • CH working on data dictionary editing of draft spec
  • MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc....
  • We will need someone to start working on a briefing slide deck (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265)

Meeting Closed 08:25 EDT

[howardtrickey]

I don't have access to upload documents to the portal. I made an example json file for the poi interchange (aka poi publishing) use case. I made a pull request on the github portal (I also don't have write access to the main poi github repository) to put it into the 21-049/examples folder, and people may want to look at it / edit it / comment on it before we decide it is a file to use in the webinar. - Howard Trickey

…

On Thu, Sep 15, 2022 at 8:25 AM Matthew Purss ***@***.***> wrote: ------------------------------ ------------------------------ Minutes 2022-09-15 Participants Matthew Purss Joetta kreck Christine Perey Howard Trickey Chuck Heazel Koen De Baets Francois Fischer Ryan Fleming Chuck Heazel Meeting Started 07:30 EDT Draft Agenda 1. Review of Action Items 2. Update on Data Model Development 3. Update/Discussion on use cases and their alignment with the Draft Data Model 4. Update/Discussion on POI Implementation Standard Drafting activities 5. Other Business Key Discussion Points - MP provided a brief overview of what we discussed in our last meeting and the Current set of Action Items. - CH updated the GeoJSON POI schema and confirmed that it still conforms to the draft Data Model. - SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model. - KDB - will check and validate Hotels POI example - HT - will check and validate the Interchange POI Use case - CP we should create a space on the portal to collect material for the webinar/Community Briefing (MP Done https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265 ). - CP would be good to show a Moving Features/Objects POI use case example in addition to the Hotels and Interchange examples. Maybe some military examples (Joetta may have something). - Rough order of the briefing - overview and intro of the draft spec (~15 min) - presentation of 3 example use case scenarios (all leveraging the draft spec) (~30 min - ~10min per example) - discussion + Q&A (~15 min) Actions - MP to invite Ronald Tse to next weeks POI SWG to help foster the continued discussion regarding standardised representations of business hours from the perspective of a POI. - MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo. - CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion. - CH will work at manually fixing the Data Dictionary entries in the draft spec ahead of the Briefing. - MP to tidy up some of the non-Data Model components of the draft POI spec. - SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model. - KDB going to do some work on the Hotel use case example - HT going to do some work on the Interchange use case example - (we will need to maybe do a request of SWG members) to do some work on a Moving Features use case Example. - CH working on data dictionary editing of draft spec - MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc.... - We will need someone to start working on a briefing slide deck (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265 ) Meeting Closed 08:25 EDT — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXMNEVBJNGEDYVTQR3IFLODV6MITXANCNFSM5VE6WJEQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[geofizzydrink]

---

---

Minutes 2022-09-21

Participants

Matthew Purss
Howard Trickey
Chuck Heazel
Francois Fischer

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP provided a brief overview of what we discussed in our last meeting and the Current set of Action Items.
• CH updated the GeoJSON POI schema and confirmed that it still conforms to the draft Data Model.
• KDB did some work on the Hotel use case example - emailed through to MP - will add to both the portal and github repo.
• HT did some work on the Interchange use case example - had some issues uploaded to the OGC POI SWG Portal so created a pull request to the github repo - CH approved and merged with the main branch.
• MP fixed the OGC POI SWG Portal access issue for HT - Will also go through the membership contacts list and make sure that all of the active members who have been participating during the SWG telecons this year are set to at least a "voting member" status.
• MP will be unavailable to host the POI SWG meeting scheduled for 6 October. CH also unavailable and since it is during the OGC members meeting week a decision was taken to cancel that meeting - MP to send out notification.

Actions

• MP to invite Ronald Tse to next weeks POI SWG to help foster the continued discussion regarding standardised representations of business hours from the perspective of a POI.

• MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo.

• CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.

  • CH will keep working at manually fixing the Data Dictionary entries in the draft spec ahead of the Briefing.

• MP to tidy up some of the non-Data Model components of the draft POI spec.

• SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model.

  • KDB going to do some work on the Hotel use case example
  • HT going to do some work on the Interchange use case example
  • (we will need to maybe do a request of SWG members) to do some work on a Moving Features use case Example.
  • CH working on data dictionary editing of draft spec
  • MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc....
  • We will need someone to start working on a briefing slide deck (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265)

Meeting Closed 08:15 EDT

[geofizzydrink]

---

---

Minutes 2022-09-21

Participants

Matthew Purss
Howard Trickey
Chuck Heazel
Christine Perey
Koen De Baets
Amy Youmans

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP provided a brief overview of what we discussed in our last meeting and the Current set of Action Items.
• CP raised the ongoing issues (and growing frustration) in gaining traction with OGC Marketing staff to advertise and promote the POI Webinar scheduled for 27-28 October.
  • Group discussion was had:
    • on the agenda for the webinar;
    • Focus and presenter for the Moving Features use case example (AY identified as a possible contributer/presenter - although she has some reservations regarding her availability/time capacity to prepare such a use case example in time)
    • Presentation order
      • Intro - MP/CP - 5 min
      • POI Data Model and current state of Spec - CH - 20 min
      • Hotel POI Use Case - KDB - 5 min
      • Interchange POI Use Case - HT - 5 min
      • Moving Features Use Case - AY (or maybe Kyoungsook Kim) - 5 min;
      • Q&A - 20 min
    • Presenter availability; and,
    • in light of the practical need to "ideally" advertise the webinar at least a month in advance to allow participants to adjust their schedules and attend it was agreed by the SWG that we should push the webinar date back until mid-November or early-December at the earliest.
    • CP to liaise with Scott Simmons regarding OGC Marketing support and rescheduling the webinar to November (or later) siting the delay in promotional activities and our desire to ensure participants have sufficient lead time to prepare as the primary reason(s) for the delay.
• There will be no POI SWG telecon next week 6 October (OGC Members Meeting week)
  • MP will be unavailable to host the POI SWG meeting scheduled for 6 October.
  • CH also unavailable until after 14 October
  • MP will send out calendar invites for SWG telecons for the next 3 months (same day/time as usual)

Actions

• CP to invite Ronald Tse to next weeks POI SWG to help foster the continued discussion regarding standardised representations of business hours from the perspective of a POI.

• MP to copy POI webinar data model testing blurb text into a suitable readme on the github repo.

• CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.

  • CH will keep working at manually fixing the Data Dictionary entries in the draft spec ahead of the Briefing.

• MP to tidy up some of the non-Data Model components of the draft POI spec.

• SWG to provide example POI schema implementations of a number of use case scenarios. This will assist and provide some focus to the workshop discussions regarding the Data Model - and will provide an evidence basis for the SWG to make an informed decision regarding possible extension/alteration of the ISO derived POI Data Model.

  • KDB going to do some work on the Hotel use case example
  • HT going to do some work on the Interchange use case example
  • (we will need to maybe do a request of SWG members) to do some work on a Moving Features use case Example.
  • CH working on data dictionary editing of draft spec
  • MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc....
  • We will need someone to start working on a briefing slide deck (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265)

Meeting Closed 08:15 EDT

[geofizzydrink]

---

---

Minutes 2022-10-13

Participants

Matthew Purss
Howard Trickey
Koen De Baets
Joetta Kreck
Christine Perey
Amy Youmans

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• POI briefing - Nov 17 0900 EST & 1900 EST
• Powerpoint template for POI Briefing slides https://portal.ogc.org/files/?artifact_id=94382

Actions

• CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.

  • CH will keep working at manually fixing the Data Dictionary entries in the draft spec ahead of the Briefing.
  • MP to tidy up some of the non-Data Model components of the draft POI spec.
  • CH working on data dictionary editing of draft spec
  • MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc....

• MP to tidy the Briefing Call to Action text and copy POI webinar data model testing blurb text into a suitable readme on the github repo.

• MP to reach out to KK re moving features example.

• HT, KDB & MP to work on their slides for the POI Briefing - aim to have completed by 3 November. (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265)

Meeting Closed 08:20 EDT

[howardtrickey]

FYI, I uploaded some slides for the POI Publish/Interchange use case to our portal, along with the example json file. We can perhaps go over these on Thursday. I will not be able to make the meeting the week after this week. - Howard

…

On Thu, Oct 13, 2022 at 8:20 AM Matthew Purss ***@***.***> wrote: ------------------------------ ------------------------------ Minutes 2022-10-13 Participants Matthew Purss Howard Trickey Koen De Baets Joetta Kreck Christine Perey Amy Youmans Meeting Started 07:35 EDT Draft Agenda 1. Review of Action Items 2. Update on Data Model Development 3. Update/Discussion on use cases and their alignment with the Draft Data Model 4. Update/Discussion on POI Implementation Standard Drafting activities 5. Other Business Key Discussion Points - POI briefing - Nov 17 0900 EST & 1900 EST - Powerpoint template for POI Briefing slides https://portal.ogc.org/files/?artifact_id=94382 - - Actions - CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion. - CH will keep working at manually fixing the Data Dictionary entries in the draft spec ahead of the Briefing. - MP to tidy up some of the non-Data Model components of the draft POI spec. - CH working on data dictionary editing of draft spec - MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc.... - MP to tidy the Briefing Call to Action text and copy POI webinar data model testing blurb text into a suitable readme on the github repo. - MP to reach out to KK re moving features example. - HT, KDB & MP to work on their slides for the POI Briefing - aim to have completed by 3 November. (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265 ) Meeting Closed 08:20 EDT — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXMNEVBZ5QFEBRRANEP3BGLWC7477ANCNFSM5VE6WJEQ> . You are receiving this because you commented.Message ID: ***@***.***>

[geofizzydrink]

---

---

Minutes 2022-10-20

Participants

Matthew Purss
Howard Trickey
Chuck Heazel
Koen De Baets
Ronald Tse
Joetta Kreck
Amy Youmans

Apologies

Christine Perey

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Brief overview of the POI SWG and it's revised goal as well as the draft data model and spec to give Ronald Tse some context to the workings of the POI SWG.
• Briefly Discussed the Business Hours usage patterns - Ronald Tse provided some very useful perspectives on this.
• Discussed and edited the POI Briefing memo and registration page text.
• POI briefing - Nov 17 0900 EST & 1900 EST
• NB: Powerpoint template for POI Briefing slides https://portal.ogc.org/files/?artifact_id=94382

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
  • MP to tidy up some of the non-Data Model components of the draft POI spec.
  • MP working on terms & defs section of draft spec + some of the other sections such as document history, contributing organisations etc....
• MP to email Scott Simmons and Greg Buelher the finalised Briefing material documents.
• HT, KDB & MP to work on their slides for the POI Briefing - aim to have completed by 3 November. (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265)

Meeting Closed 08:20 EDT

[geofizzydrink]

---

---

Minutes 2022-10-27

Participants

Matthew Purss
Chuck Heazel
Koen De Baets
Christine Perey

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP - Overview of Action Items
• MP - Powerpoint slides to be merged into a single master slide deck during/following the POI SWG meeting on 3 Nov.
• CP potential POI interested parties for the briefing:
  • https://www.ordnancesurvey.co.uk/business-government/tools-support/points-of-interest-support
  • Others???
• CP comment - we should have a link to the data model in the briefing registration page.
  • CP emailed Greg/Scott with a link to add to the registration page.
• KDB - working on use case slide deck for briefing - will upload when finished.

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• HT, KDB & MP to work on their slides for the POI Briefing - aim to have completed by 3 November. (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265 )

Meeting Closed 08:37 EDT

[geofizzydrink]

---

---

Minutes 2022-11-03

Participants

Matthew Purss
Chuck Heazel
Koen De Baets
Kyoung-Sook Kim
Howard Trickey
Amy Youmans
Joetta

Christine Perey

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP - Overview of Action Items
• Presentation order
  • Intro - MP/CP - 5 min
  • POI Data Model and current state of Spec - CH - 20 min
  • JSON Schema represenation of POI Data Model - CH 10 min
  • Use case Examples:
    • Hotel POI Use Case - KDB - 5 min
    • Interchange POI Use Case - HT - 5 min
    • Moving Features Use Case - AY (or maybe Kyoungsook Kim) - 5 min;
  • Discussion - 10 min

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• CH to work up a slide deck to show the application of the UML model through the JSON Schema.
• MP to create a Master Slide Deck and to fold all of the individual presentations into the Master Slide Deck (to be uploaded to the OGC portal https://portal.ogc.org/index.php?m=projects&a=view&project_id=440&tab=2&artifact_id=102265 )

Meeting Closed 08:37 EDT

[geofizzydrink]

---

---

Minutes 2022-11-10

Participants

Matthew Purss
Chuck Heazel
Koen De Baets
Howard Trickey
Amy Youmans
Joetta Kreck
Christine Perey

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP - Overview of master slide deck for next weeks POI Briefing

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• MP - send out a meeting invite to presenters for the evening session (30 prior to briefing start time)
• All - make sure we all register for the briefing so we get the gotomeeting link.

Meeting Closed 08:25 EDT

[geofizzydrink]

---

---

Minutes 2022-12-01

Participants

Matthew Purss
Chuck Heazel
Koen De Baets
Howard Trickey
Christine Perey

Meeting Started 07:35 EST

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• CP/MP Review of outcomes from webinar and immediate next steps
• CH - "build" issues nice to resolve but not critical to publication of the standard
• CH - we need to resolve the github issues, address any changes in the data model these github issues related to and put out a draft for public comment with a user guide
• HT - are we going to get substantial feedback from the public comment phase? does POI resolve a key use case for the community?
• HT/CH - User Guide document is needed and will be beneficial to the standard - particularly demonstrating a user community need for the standards.
• CH - include a section for each major use case in the users guide.

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• ALL - Collect Use Cases and engage with submitters to engage in drafting the user guide and/or spec
• CH - will create a new section in the github repo for the user guide document
• ALL - Review and resolve outstanding github issues.
• CH - create a tag for issues "Recommend to Close" (or something similar) so that we can identify open issues that have been answered but not documented as such.

Meeting Closed 08:12 EST

[geofizzydrink]

---

---

Minutes 2022-12-08

Participants

Matthew Purss
Chuck Heazel
Koen De Baets
Howard Trickey

Christine Perey

Meeting Started 07:35 EST

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• MP - OGC Members Meeting Feb - Frascati. We secured a slot on Tuesday 21 February from 17:10 to 18:00.
• MP - led review of existing github issues.

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• ALL - Collect Use Cases and engage with submitters to engage in drafting the user guide and/or spec

Meeting Closed 08:32 EST

[geofizzydrink]

---

---

Minutes 2023-01-19

Participants

Matthew Purss
Francois Fischer
Koen De Baets
Howard Trickey
Christine Perey
Amy Youmans

Apologies

Chuck Heazel

Meeting Started 07:30 EST

Draft Agenda

1. Review of Action Items
   

2. Update on Data Model Development
   

3. Update/Discussion on use cases and their alignment with the Draft Data Model
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• ALL discussed actions (logged as issues) from last week's meeting.
  • Research and explore TN-ITS initiative and how it is relevant to POI  #78
  • Study approach and how to coordinate with Overture project #77
  • Explore possibility of joint meeting with OGC Routing SWG #76
  • Is Model's use of POIProperty too cumbersome or even proper? #75
• CP - Drafting outline of user guide document
  • New issues/actions created and assigned (see below) to progress the drafting of the User Giude Document (https://github.com/opengeospatial/poi/tree/main/22-053)

Actions

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75

New Actions - 19 Jan 2023

• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85

Meeting Closed 08:15 EST

[geofizzydrink]

---

---

Minutes 2023-01-26

Participants

Matthew Purss
Koen De Baets
Howard Trickey
Christine Perey
Amy Youmans

Apologies

Chuck Heazel

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Meetings in Feb/Mar
  • 2 Feb - normal meeting - focus on drafting "Developers" Guide (https://github.com/opengeospatial/poi/tree/main/22-053) and Open Github Issues
  • 9 Feb - Invited Discussion on Best Practice/User Guides (Jerome St Louis and/or Clemens Portele - CP emailed on 26 Jan to invite)
  • 16 Feb - normal Meeting
  • 23 Feb - OGC Members Meeting Week
  • 2 Mar - normal Meeting

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85

Meeting Closed 08:00 EST

[geofizzydrink]

---

---

Minutes 2023-02-09

Participants

Matthew Purss
Chuck Heazel
Koen De Baets
Howard Trickey
Christine Perey
Amy Youmans

Guest

Clemens Portele

Apologies

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Meetings in Feb/Mar
  • 2 Feb - normal meeting - focus on drafting "Developers" Guide (https://github.com/opengeospatial/poi/tree/main/22-053) and Open Github Issues
  • 9 Feb - Invited Discussion on Best Practice/User Guides (Jerome St Louis and/or Clemens Portele - CP emailed on 26 Jan to invite)
  • 16 Feb - normal Meeting
  • 23 Feb - OGC Members Meeting Week
  • 2 Mar - normal Meeting

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85

Meeting Closed 08:00 EST

[geofizzydrink]

---

---

Minutes 2023-02-16

Participants

Matthew Purss
Amy Youmans
Howard Trickey
Koen De Baets
Christine Perey

Chuck Heazel

Guests

Apologies

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Meetings in Feb/Mar
  • 2 Feb - normal meeting - focus on drafting "Developers" Guide (https://github.com/opengeospatial/poi/tree/main/22-053) and Open Github Issues
  • 9 Feb - Invited Discussion on Best Practice/User Guides (Jerome St Louis and/or Clemens Portele - CP emailed on 26 Jan to invite)
  • 16 Feb - normal Meeting
  • 23 Feb - OGC Members Meeting Week - NO POI SWG MEETING this week.
  • 2 Mar - normal Meeting

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85
• Collect and compare guides for implementers of other standards #86
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Capture and recommend how to use prior work (standards) for attributes not standardized in POI CM #88
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92

Meeting Closed 08:10 EST

[geofizzydrink]

---

---

Minutes 2023-03-02

Participants

Matthew Purss
Chuck Heazel
Howard Trickey
Koen De Baets
Amy Youmans

Guests

Apologies

Christine Perey

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Meetings in Feb/Mar
  • 2 Feb - normal meeting - focus on drafting "Developers" Guide (https://github.com/opengeospatial/poi/tree/main/22-053) and Open Github Issues
  • 9 Feb - Invited Discussion on Best Practice/User Guides (Jerome St Louis and/or Clemens Portele - CP emailed on 26 Jan to invite)
  • 16 Feb - normal Meeting
  • 23 Feb - OGC Members Meeting Week - NO POI SWG MEETING this week.
  • 2 Mar - normal Meeting

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85
• Collect and compare guides for implementers of other standards #86
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Capture and recommend how to use prior work (standards) for attributes not standardized in POI CM #88
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92

Meeting Closed 08:30 EST

[geofizzydrink]

---

---

Minutes 2023-03-08

Participants

Matthew Purss
Chuck Heazel
Howard Trickey
Christine Perey
Joetta Kreck

Koen De Baets
Amy Youmans

Guests

Apologies

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Meetings in Feb/Mar
  • 2 Feb - normal meeting - focus on drafting "Developers" Guide (https://github.com/opengeospatial/poi/tree/main/22-053) and Open Github Issues
  • 9 Feb - Invited Discussion on Best Practice/User Guides (Jerome St Louis and/or Clemens Portele - CP emailed on 26 Jan to invite)
  • 16 Feb - normal Meeting
  • 23 Feb - OGC Members Meeting Week - NO POI SWG MEETING this week.
  • 2 Mar - normal Meeting

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85
• Collect and compare guides for implementers of other standards #86
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Capture and recommend how to use prior work (standards) for attributes not standardized in POI CM #88
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92

Meeting Closed 08:30 EST

[geofizzydrink]

---

---

Minutes 2023-03-23

Participants

Matthew Purss
Howard Trickey
Koen De Baets
Joetta Kreck
Francois Fischer

Chuck Heazel
Christine Perey

Amy Youmans

Guests

Apologies

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

• Meetings in Feb/Mar
  • 2 Feb - normal meeting - focus on drafting "Developers" Guide (https://github.com/opengeospatial/poi/tree/main/22-053) and Open Github Issues
  • 9 Feb - Invited Discussion on Best Practice/User Guides (Jerome St Louis and/or Clemens Portele - CP emailed on 26 Jan to invite)
  • 16 Feb - normal Meeting
  • 23 Feb - OGC Members Meeting Week - NO POI SWG MEETING this week.
  • 2 Mar - normal Meeting

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85
• Collect and compare guides for implementers of other standards #86
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Capture and recommend how to use prior work (standards) for attributes not standardized in POI CM #88
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92

Meeting Closed 08:30 EST

[geofizzydrink]

---

---

Minutes 2023-03-30

Participants

Matthew Purss
Howard Trickey
Koen De Baets
Joetta Kreck
Chuck Heazel

Guests

Apologies

Meeting Started 07:34 EST

Draft Agenda

1. Review of Action Items / Open Issues
   

2. Update of work towards Drafting the Best Practice / Developer / Publisher Guide
   

3. Update(s) on Data Model Development
   

4. Update/Discussion on POI Implementation Standard Drafting activities
   

5. Other Business
   

Key Discussion Points

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Study approach and how to coordinate with Overture project #77
• Explore possibility of joint meeting with OGC Routing SWG #76
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write first draft of clause on how to deal with attributes that are not defined in the standard #84
• Write (or retrieve) example representations #85
• Collect and compare guides for implementers of other standards #86
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Capture and recommend how to use prior work (standards) for attributes not standardized in POI CM #88
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92

Meeting Closed 08:30 EST

[geofizzydrink]

---

---

Minutes 2023-04-13

Participants

Matthew Purss
Chuck Heazel
Howard Trickey
Koen De Baets
Joetta Kreck

Guests

Apologies

Meeting Started 07:34 EST

Draft Agenda

1. Review of Minutes from last meeting
   

2. Review of Github Issues
   

3. Discussion/inclusion of any new Github Issues
   

4. Update on Status of the Data Model
   

5. Update on Status of the Standard Specification
   

6. Update on Status of the User Guide
   

7. Other Business
   

Key Discussion Points

• Koen took us through his updates to the User Guide
• Howard took us through his updates to the User Guide
  • There was some discussion regarding the use of extended attribute notations in the "properties" object. The ISO recommendation is that wherever possible one should list the "properties" of a "feature" as a simple key:value pair. If this cannot be achieved then it is ok to extend the schema.
  • Based on feedback Howard will tidy up the JSON example for his section.

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• Syles/Symbology considerations for Data Model #61
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Can the POI standard support both geometry and time descriptions in an normalised and optimal way? #67
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92
• Include in Conceptual Model a List of Recommended Property Types #94
• Is proximity an attribute of conceptual model or can it be useful in some use cases? #95
• Is there need for including Priortization in the POI CM? #96

Meeting Closed 08:15 EST

[geofizzydrink]

---

---

Minutes 2023-04-20

Participants

Matthew Purss
Christine Perey

Guests

Apologies

Chuck Heazel
Howard Trickey
Koen De Baets
Joetta Kreck

Meeting Started 07:34 EST

Draft Agenda

1. Review of Minutes from last meeting
   

2. Review of Github Issues
   

3. Discussion/inclusion of any new Github Issues
   

4. Update on Status of the Data Model
   

5. Update on Status of the Standard Specification
   

6. Update on Status of the User Guide
   

7. Other Business
   

Key Discussion Points

• Christine responded to Francis' email requesting to schedule for a presentation on POI implementations.
• Christine responded to the earlier request from Overture to engage with the POI SWG

Actions and Open Github Issues

• [on hold until after the briefing] CH to resolve the "build" issues translating the POI Data Model into the spec document templates - aiming for late September/early October for completion.
• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• Syles/Symbology considerations for Data Model #61
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Can the POI standard support both geometry and time descriptions in an normalised and optimal way? #67
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of clause 6.1 - Find a Restaurant Use Case #80
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Revise text (explain differently to remove "latter capability") #89
• Provide an example using the terminology and concepts introduced in the Introduction section #90
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92
• Include in Conceptual Model a List of Recommended Property Types #94
• Is proximity an attribute of conceptual model or can it be useful in some use cases? #95
• Is there need for including Priortization in the POI CM? #96

Meeting Closed 07:55 EST

[geofizzydrink]

---

---

Minutes 2023-04-27

Participants

Matthew Purss
Chuck Heazel
Howard Trickey
Christine Perey
Koen De Baets
Amy Youmans

Guests

Apologies

Joetta Kreck

Meeting Started 07:30 EST

Draft Agenda

1. Review of Minutes from last meeting
   

2. Review of Github Issues
   

3. Discussion/inclusion of any new Github Issues
   

4. Update on Status of the Data Model
   

5. Update on Status of the Standard Specification
   

6. Update on Status of the User Guide
   

7. Other Business
   

Key Discussion Points

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• Syles/Symbology considerations for Data Model #61
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Can the POI standard support both geometry and time descriptions in an normalised and optimal way? #67
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Is Model's use of POIProperty too cumbersome or even proper? #75
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Revise text (explain differently to remove "latter capability") #89
• Insert links to the specifications cited in Introduction (as footer or bibliography) #91
• Add to the Scope section that the User Guide includes more than just explaining POI-CM #92
• Include in Conceptual Model a List of Recommended Property Types #94
• Is proximity an attribute of conceptual model or can it be useful in some use cases? #95
• Is there need for including Priortization in the POI CM? #96

Meeting Closed 08:30 EST

[geofizzydrink]

---

---

Minutes 2024-02-01

Participants

Matthew Purss
Howard Trickey
Stijn Tallir
Christine Perey
Amy Youmans

Guests

Apologies

Joetta Kreck
Francois Fischer

Meeting Started 07:30 EST

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CH is travelling, so no update this week.

• CH - working on the abstract test suite, once complete will do a final validation pass and we are then good to send the spec up to the OAB.

  • Will be away from 16 Jan to 6 Feb - may not get much done during this period.

• MP - we have a slot reserved for the POI SWG during the March Members Meeting in Delft. 50min (short) session ~5:40pm to 6:30pm local time. Depending on any votes we need to call at the SWG level regarding the Spec and User Guide, we could possibly use this session to present both an overview of the POI spec/data model and the reference implementations of it.

• CP - will be at the meeting in person and can host the meeting from the room.

• HT - will be able to attend in person.

• MP - hoping to be able to make it as well but still very uncertain on travel budget.

• ST - hoping to be able to make it in person but will definitely be there online if that doesn't work.

Draft Agenda for Members Meeting

• Into & Logistics (chair/host) - 5 min

• CH & HT can probably present an overview of the spec.

• ST can present - Title TBA

• HT can present - Title TBA

• Other Business (chair/host) - 5 min

• HT - has prepared a POI JSON file with 24 example POIs for the Delft Members Meeting

  • CP - question over multiple geometries (such as access points) and how they might be encoded as OGC POI's (e.g. separate POIs vs include additional geometry info as part of the payload).
  • HT - question over the best way to include language designation "tags" - we should follow this up with CH when he's back on deck - however, probably not needing us to halt the progression of the spec to OAB.
  • HT - [ACTION] fix the example in the user guide - software generated JSON has highlighted a number of errors in the User Guide example.

• ST - currently pulling together a similar example to HT using data from Flanders (including internal bespoke POI structures - that can be presented in the OGC POI schema). Expecting to have a nice demo of this ready by the Members Meeting.

[TO DO]

• SWG - we need to start working to manually edit and fill in points 1-4 of Issue To Do #111 (i.e. the initial sections of the spec document).

  • CH - suggested process for the SWG driven editing:
    • clone repo
    • edit content
    • pull-request
    • merge
    • If we edit-> merge regularly there should not be many (if any) conflicts with the sections we will be manually editing.

• [ACTION] - those writing examples please review the text of the draft spec to make sure there is enough information to properly assist someone to implement the standard.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:20 EST

[geofizzydrink]

---

---

Minutes 2024-02-08

Participants

Matthew Purss
Howard Trickey
Christine Perey
Amy Youmans
Chuck Heazel
Stijn Tallir

Guests

Gabor Soros

Apologies

Joetta Kreck
Francois Fischer

Meeting Started 07:30 EST

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• GS - poi examples so that he can present as part of his Augmented Reality Demo (webxr) for the OGC Members Meeting - showing the use of geopose to display and embed poi information.

• CH - abstract test suite is done!

  • working on final validation pass and we are then good to send the spec up to the OAB.

• Everyone [ACTION] review latest version of the built spec doc (should be autogenerated overnight - EST).

• SWG Vote - Next Meeting, once we've reviewed - Motion to send the Draft Standard up to the OAB for technical and OGC Architecture review proir to release for public comment.

  • once we have public comments back will need to review and address any/all comments before we can send the Standard up to the TC for Approval.

• MP - we have a slot reserved for the POI SWG during the March Members Meeting in Delft. 50min (short) session ~5:40pm to 6:30pm local time. Depending on any votes we need to call at the SWG level regarding the Spec and User Guide, we could possibly use this session to present both an overview of the POI spec/data model and the reference implementations of it.

• CP - will be at the meeting in person and can host the meeting from the room.

• HT - will be able to attend in person.

• MP - hoping to be able to make it as well but still very uncertain on travel budget.

• ST - hoping to be able to make it in person but will definitely be there online if that doesn't work.

Draft Agenda for Members Meeting

• Into & Logistics (chair/host) - 5 min

• CH & HT can probably present an overview of the spec.

  • NB: CH has a clash with the OAB closed session which is happening in parallel - will endeavour to be in the POI session to provide spec overview but if one of us will need to do that in his stead.

• ST can present - Title TBA

• HT can present - Title TBA

• Other Business (chair/host) - 5 min

• HT - has prepared a POI JSON file with 24 example POIs for the Delft Members Meeting

  • CP - question over multiple geometries (such as access points) and how they might be encoded as OGC POI's (e.g. separate POIs vs include additional geometry info as part of the payload).
  • HT - question over the best way to include language designation "tags" - we should follow this up with CH when he's back on deck - however, probably not needing us to halt the progression of the spec to OAB.
  • HT - [ACTION] fix the example in the user guide - software generated JSON has highlighted a number of errors in the User Guide example.

• MP created the POI SWG folder under the March Members Meeting folder on the OGC Portal - so we can upload presentations and related resources prior to the meeting. https://portal.ogc.org/index.php?m=projects&a=view&project_id=82&tab=2&artifact_id=107035

• ST - currently pulling together a similar example to HT using data from Flanders (including internal bespoke POI structures - that can be presented in the OGC POI schema). Expecting to have a nice demo of this ready by the Members Meeting.

• HT - Issue raised with him regarding the use of multiple schemas for the payload.

  ---

  • We need to discuss this from Jan-Erik Vinje:
    If there is still room to modify the structure of this standard I have the following comments:

1. Its good that the usesSchema of the haspayload field is an array! That allows for multiple schemas wich can make a lot of sense. A poi can be associated with multiple payload structures, something that I would think allows for wonderful flexibility.
2. It seems bad that the payload data appears to exists as arbitrary sibling fields to the "usesSchema" array inside of the haspayload field and that it therefore could easily be conflicts betwen the fields of different schemas.

Proposal: If one is to allow for multiple schemas of parallel payload data inside one poi the payloads should be separated I propose an array called "payloads" where the objects in the array are look like something like this this {"schema":"schemaURL", payload:<Array/Object/Value>}

---

• CH - intention is that the different schemas are different representations of essentially the same thing.
  • Maybe raise it as a question to the OAB regarding all specs and data models that enable/allow multiple schema definitions to be included in the body of a response.

[TO DO]

• SWG - we need to start working to manually edit and fill in points 1-4 of Issue To Do #111 (i.e. the initial sections of the spec document).

  • CH - suggested process for the SWG driven editing:
    • clone repo
    • edit content
    • pull-request
    • merge
    • If we edit-> merge regularly there should not be many (if any) conflicts with the sections we will be manually editing.

• [ACTION] - those writing examples please review the text of the draft spec to make sure there is enough information to properly assist someone to implement the standard.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:20 EST

[geofizzydrink]

---

---

Minutes 2024-02-15

Participants

Matthew Purss
Howard Trickey
Christine Perey
Stijn Tallir
Chuck Heazel

Guests

Apologies

Joetta Kreck
Francois Fischer
Amy Youmans

Meeting Started 07:30 EST

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CH - abstract test suite is done!

  • working on final validation pass and we are then good to send the spec up to the OAB.

• Everyone [ACTION] review latest version of the built spec doc (should be autogenerated overnight - EST).

  • current list of issues with the spec document include:
    • keywords - expand
    • submitting orgs - "Digital Flanders" not "Flancers" - CH [DONE]
    • sanity check on terms and defs list
    • sanity check on refs to ISO / other standards - need to make sure is in the normative references section.
    • req 26 - note about multiple schemas in the payload - why would this be and some examples of that (e.g. json schema + yaml schema == same schema different representation) - CH will fix
    • Abstract Test - A.13 broken link CH will fix
    • doc history - needs to be updated CH to fix

• SWG Vote - Next Meeting, once we've reviewed - Motion to send the Draft Standard up to the OAB for technical and OGC Architecture review proir to release for public comment.

  • once we have public comments back will need to review and address any/all comments before we can send the Standard up to the TC for Approval.

• HT - has prepared a POI JSON file with 24 example POIs for the Delft Members Meeting

  • CP - question over multiple geometries (such as access points) and how they might be encoded as OGC POI's (e.g. separate POIs vs include additional geometry info as part of the payload).
  • HT - question over the best way to include language designation "tags" - we should follow this up with CH when he's back on deck - however, probably not needing us to halt the progression of the spec to OAB.
  • HT - [ACTION] fix the example in the user guide - software generated JSON has highlighted a number of errors in the User Guide example.

• MP created the POI SWG folder under the March Members Meeting folder on the OGC Portal - so we can upload presentations and related resources prior to the meeting. https://portal.ogc.org/index.php?m=projects&a=view&project_id=82&tab=2&artifact_id=107035

• ST - has pulled together a similar example to HT using data from Flanders (including internal bespoke POI structures - that can be presented in the OGC POI schema). Expecting to have a nice demo of this ready by the Members Meeting.

• HT - Issue raised with him regarding the use of multiple schemas for the payload.

  ---

  • We need to discuss this from Jan-Erik Vinje:
    If there is still room to modify the structure of this standard I have the following comments:

1. Its good that the usesSchema of the haspayload field is an array! That allows for multiple schemas wich can make a lot of sense. A poi can be associated with multiple payload structures, something that I would think allows for wonderful flexibility.
2. It seems bad that the payload data appears to exists as arbitrary sibling fields to the "usesSchema" array inside of the haspayload field and that it therefore could easily be conflicts betwen the fields of different schemas.

Proposal: If one is to allow for multiple schemas of parallel payload data inside one poi the payloads should be separated I propose an array called "payloads" where the objects in the array are look like something like this this {"schema":"schemaURL", payload:<Array/Object/Value>}

---

• CH - intention is that the different schemas are different representations of essentially the same thing.

  • Maybe raise it as a question to the OAB regarding all specs and data models that enable/allow multiple schema definitions to be included in the body of a response.

• [ACTION] - those writing examples please review the text of the draft spec to make sure there is enough information to properly assist someone to implement the standard.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:50 EST

[cmheazel]

Matt, Here is an updated status --- * keywords – expand [DONE but additional keywords would be welcome] * submitting orgs - "Digital Flanders" not "Flancers" - CH [DONE] * sanity check on terms and defs list * sanity check on refs to ISO / other standards - need to make sure is in the normative references section. [Metanorma did not identify any unresolvable references in the build] * req 26 - note about multiple schemas in the payload - why would this be and some examples of that (e.g. json schema + yaml schema == same schema different representation) - CH [DONE, also included a short discussion of hasDefinition] * Abstract Test - A.13 broken link CH [DONE] * doc history - needs to be updated CH [DONE] Chuck From: Matthew Purss ***@***.***> Sent: Thursday, February 15, 2024 8:58 AM To: opengeospatial/poi ***@***.***> Cc: Charles Heazel ***@***.***>; Comment ***@***.***> Subject: Re: [opengeospatial/poi] Meeting Minutes (Issue #58)

…

________________________________

________________________________ Minutes 2024-02-15 Participants Matthew Purss Howard Trickey Christine Perey Stijn Tallir Amy Youmans Chuck Heazel Guests Apologies Joetta Kreck Francois Fischer Meeting Started 07:30 EST Draft Agenda 1. Review of Minutes from last meeting 2. Update on Status of the Data Model 3. Update on Status of the Standard Specification 4. Update on Status of the User Guide 5. POI Standards Roadmap + ISO 19155 6. Review of Github Issues 7. Discussion/inclusion of any new Github Issues 8. Other Business Key Discussion Points * MP - review from last meeting. * CH - abstract test suite is done! * working on final validation pass and we are then good to send the spec up to the OAB. * Everyone [ACTION] review latest version of the built spec doc (should be autogenerated overnight - EST). * current list of issues with the spec document include: * keywords - expand * submitting orgs - "Digital Flanders" not "Flancers" - CH [DONE] * sanity check on terms and defs list * sanity check on refs to ISO / other standards - need to make sure is in the normative references section. * req 26 - note about multiple schemas in the payload - why would this be and some examples of that (e.g. json schema + yaml schema == same schema different representation) - CH will fix * Abstract Test - A.13 broken link CH will fix * doc history - needs to be updated CH to fix * SWG Vote - Next Meeting, once we've reviewed - Motion to send the Draft Standard up to the OAB for technical and OGC Architecture review proir to release for public comment. * once we have public comments back will need to review and address any/all comments before we can send the Standard up to the TC for Approval. * HT - has prepared a POI JSON file with 24 example POIs for the Delft Members Meeting * CP - question over multiple geometries (such as access points) and how they might be encoded as OGC POI's (e.g. separate POIs vs include additional geometry info as part of the payload). * HT - question over the best way to include language designation "tags" - we should follow this up with CH when he's back on deck - however, probably not needing us to halt the progression of the spec to OAB. * HT - [ACTION] fix the example in the user guide - software generated JSON has highlighted a number of errors in the User Guide example. * MP created the POI SWG folder under the March Members Meeting folder on the OGC Portal - so we can upload presentations and related resources prior to the meeting. https://portal.ogc.org/index.php?m=projects&a=view&project_id=82&tab=2&artifact_id=107035<https://url.emailprotection.link/?bNxblswQSIiLtJO7OY02ojbVqOE2fkK48e3GMC8mBcQFseeON6uBCyryLrfmWJe-y0k8ftV0LF1dCJdJjFhEPzyFPS4EEJo--VaclWTF8WB_SpqREZFZ8cpmOhEeBgpIjdv8FlH48HaQ7OkSvETCiFzqz9Vna1reXS2AO7LX7-80~> * ST - has pulled together a similar example to HT using data from Flanders (including internal bespoke POI structures - that can be presented in the OGC POI schema). Expecting to have a nice demo of this ready by the Members Meeting. * HT - Issue raised with him regarding the use of multiple schemas for the payload.

________________________________ * We need to discuss this from Jan-Erik Vinje: If there is still room to modify the structure of this standard I have the following comments: 1. Its good that the usesSchema of the haspayload field is an array! That allows for multiple schemas wich can make a lot of sense. A poi can be associated with multiple payload structures, something that I would think allows for wonderful flexibility. 2. It seems bad that the payload data appears to exists as arbitrary sibling fields to the "usesSchema" array inside of the haspayload field and that it therefore could easily be conflicts betwen the fields of different schemas. Proposal: If one is to allow for multiple schemas of parallel payload data inside one poi the payloads should be separated I propose an array called "payloads" where the objects in the array are look like something like this this {"schema":"schemaURL", payload:<Array/Object/Value>}

________________________________ * CH - intention is that the different schemas are different representations of essentially the same thing. * Maybe raise it as a question to the OAB regarding all specs and data models that enable/allow multiple schema definitions to be included in the body of a response. * [ACTION] - those writing examples please review the text of the draft spec to make sure there is enough information to properly assist someone to implement the standard. Actions and Open Github Issues * #40<https://url.emailprotection.link/?bbQLCjQ1CAYOsQLQxoMBilPxERmcH3sB03u1d_RmDBhjf4OMmJyYqciSrD5UxsBKBwQ10j6Cit_bknTeR0msENqW8WWGHHatDf3iWYBH1sjGpn2pta-vlbCNzVP23qUaH> * #56<https://url.emailprotection.link/?bpXvwcnpXKhEXcDs3vr98vM2VoYosBudKXOs6QE63kv5yzai73HQma0yuB6ECIrCzr1sXGKX_CWEToiQzu7KuVSJQckHxSQqtzvGe8bTX812NUAhSGZ1muDd_KD3uqO-R> * #57<https://url.emailprotection.link/?b5vBDtGuqtf-roaBGcKxTGv-MxU82m7am3gDFvRPlPDCMjgPIIygpNSaWoLZdY9XIPJEWok9ucJM16a6-3VmNZ4ksZC0sKNdXl6IxN1FBj_UN-C-0tlZ8TU8NnjGvNq5g> * #58<https://url.emailprotection.link/?bia0_6i9iT6K2nl9dDFLEy9aT8QMK63xgvm15Qa0aywvFPJOSDEBaIy4agPqnLBQoE415oBsOP2xyosVxxc7hFUvCLAqdcKoKzK62pejaLu7SwG1F3aUA_KPZ6s9Ky7qc> * #63<https://url.emailprotection.link/?bKk5L7G-h-e0bRtCc_Cl3fteBcpJt2s_tT6v3j0DTzcKtKqUgVhd_zK0qcKhODrgL9NOYX3Hl93nqD15C5xlhPeVjRTRrx70szdvL2oHybydU_Kn7172DvitgMVrcxrwI> * #65<https://url.emailprotection.link/?bpXvwcnpXKhEXcDs3vr98vM2VoYosBudKXOs6QE63kv5yzai73HQma0yuB6ECIrCzqmCo0BBH5YXLIkGyoroqSypiQINlJGyfJrl9ll3cL3QfLtbC-UyHnAsGb4OgrtIa> * #70<https://url.emailprotection.link/?brhoqe2W_ivvO16nrUANWkz7eDdKrwFeLTzu6EInfGmNZk3ONNFYOyuzzzFkbnbjL_rezRXULZieLu3rGloAxdzMX8d-9sOyl82LqpcSJ9yztDSYFp4TGqgSLqd0DvKy4> * #72<https://url.emailprotection.link/?bD2IZIVjiwp3_39znV7PvXMRiIVYNvoK0Nn3Lr0GQO3H96tfSZzXfSuRmWLJUf-0KXcS8eQzAJqM9vDfFbCoRLfUsse3nIAZmYbb0Gt6J85FPWvDVUiAh6o3fYRf6eVGb> * #78<https://url.emailprotection.link/?bCogHXiJDIylqNil764GxygwozTPxPZ6GjVvOQlvkimN7gaIZwS5OAJLkzq23tRGT9vME8H0eQZEd8hncxtT8Swg6Zm2Ubl0e8HWiuli-Pyc-kJnQcxz-DQVaA5EtM2v7> * #81<https://url.emailprotection.link/?bWJJU4lY_CvKdfPiVS8oPSdD55-wDVDB5i0VQm7JzZ85-B1oGOT_IwKVjhmHvdOR12nMt21IuqGaTJ5KEucu-_KsOvPWI2pNGBLg_g6NGhTLup20-O0bEmVRPZP2mmx9J> * #82<https://url.emailprotection.link/?bghMQUGbyqz_tcne23Lkp2CxCJdbKdG6leFVtq7dt4EMEyWYO6LS7nMdIEHvT7f6FtGx-960vbXTzPlzEWVfvS2yMkRkTLmf6hRGNGAOgQqAEy1ExBh-vzva9FOyFQXa5> * #83<https://url.emailprotection.link/?by2K7lMoAr2mUMutkN-yixxyNcRX9xTFkAJeleUEgFWVOhej0E3auCzGvZEeNbRQZLjYRPTjcqW9jUgrKlhHJsqKlPNN9noLftp5yHHXeHyXxgUxwelPkrOmwtiaSQdO0> * #85<https://url.emailprotection.link/?bia0_6i9iT6K2nl9dDFLEy9aT8QMK63xgvm15Qa0aywvFPJOSDEBaIy4agPqnLBQoLULoNGVGQhkHfVju_IZAZK6rKLvrjkEarEJMWb0HVYfpDORRdrA3ZVelVkVF4KOo> * #87<https://url.emailprotection.link/?bCogHXiJDIylqNil764GxygwozTPxPZ6GjVvOQlvkimN7gaIZwS5OAJLkzq23tRGTYfvLiXpUgtt430KE2HawLLDh0ZgugcGwqH-P6PkhUpKI9F03m4I37xKZu8I8718H> * #94<https://url.emailprotection.link/?b1m66UmJBeVYvw9T-T2sXKdmCppAmhh4dDuNl9bSd3577fTbAKYJZ2zY2POf4qTRErt3hjmNyBvlbbAymu2mHlCNovCXpAij99X_8FlUDvYJUINcIdje5BJHK0S8iNH2u> * #96<https://url.emailprotection.link/?b1qywykQZCllTvxR-68AtvazPnxWVQj9MYx1bkIrWIvfPr1-k4I_U8X1lijMtBOvxUFncng_owfyzVxyflENJ_XHC6nYTIVOTVTFhwEz7m3VKGdfNJwh6x1UQH-Ff2omA> * #103<https://url.emailprotection.link/?bw0d1JDb5Cw_rZ6mj5nYRmubZ8ZqlsyN1hCNGv0yNTW-lancuNB1BOagUc4w7h5uwzUErwHVv-85gnDhCkywE4wUqy045c4jUS0QsNNFYySylbMeb_7tUm11WH3Ci4JwC> * #104<https://url.emailprotection.link/?bTQln1GyMBn5nYbycRYPRgqxSLbcs94tenn26j-iguejIMXowdAJUuH3ZAiE-DkA0eqrV2Mlk8nRuzLBan1EbBzHawLGOcgBDkkyz5pJfGrFcddqtCjkUDrDDVhUgfJKC> Meeting Closed 08:50 EST — Reply to this email directly, view it on GitHub<https://url.emailprotection.link/?bF4RPVfDDloWngtCaKNabokrA2RKLVilUus7XFZBm0s-H6qpNuk81uKq8X3etjdt8UDlTNMyLtO4wOxvKg59ATkVI2fOZwJuUhreva_FbFc3JOpuQpB4JBxkB3aqVlHZM>, or unsubscribe<https://url.emailprotection.link/?b10w8h3343sjxA0rdKUp02GyO1zi99j48kzyQ-nxMpAc8OiTD58zWK5-CCHf5kqvidMA4uwMIh3GeeULuZeKltTZb0TRpg29SW4bdmQBUhTJohevJM5jZPHvyUhZcD0LZDuq7jj8za9rGA3SDJnVQT-Y04pZacLoAxV7Gy1f1db0AgNdAGmpFkM7uBw_Vk3rKtGbxC8clZbfC95EPHLOAJGgSawO1YyebN6dHunwBrz1bbTg2jrejfJatVnRqNzAs>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[geofizzydrink]

---

---

Minutes 2024-02-29

Participants

Matthew Purss
Howard Trickey
Stijn Tallir
Chuck Heazel

Guests

Apologies

Christine Perey
Joetta Kreck
Francois Fischer
Amy Youmans

Meeting Started 07:30 EST

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CH - we should set up a dedicated issue to track all communications and comments related to the spec and it's passage through the OGC Publication Process.

  • [DONE] - 21-049 - Public Comments - Carl Reed #123

• HT - we should get the Spec Overview presentation sorted for the Members Meeting POI SWG Session.

  • Starting with the webinar presentation we delivered in December 2022 as a basis will be a good start. However, we need to update to reflect the evolution of the Data Model.
    • https://portal.ogc.org/files/?artifact_id=102930
  • Demo for the March Members Meeting is coming along nicely.

• CH - We could/should use the presentation we need to work up for the OAB for the overview during the Members Meeting Session ( Monday 25 March 5:40 PM - 6:30 PM (local time) ).

  • We should try to keep the discussion on the underlying architecture and data model to a minimum so that we have plenty of time to showcase the demos of POI's actually in the wild.
  • Will be travelling during March - will let us know what schedule and availability particularly for the OAB.
  • Will talk to Scott Simmons to make sure the POI spec is not booked for an OAB meeting when Chuck cannot attend.
  • OAB have scheduled the POI Spec for the meeting on 12 March.
    • CH will be travelling, but will be in Fort Collins so will be able to attend the meeting with Scott. Will confirm with Scott on this.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:08 EST

[geofizzydrink]

---

---

Minutes 2024-03-07

Participants

Matthew Purss
Howard Trickey
Stijn Tallir
Chuck Heazel
Christine Perey

Guests

Apologies

Joetta Kreck
Francois Fischer
Amy Youmans

Meeting Started 07:30 EST

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CH - ran through presentation to OAB for the POI spec

  • expecting the meeting to be at 11am EST 12 March
  • need to have an example implementation up our sleeves
  • HT - can POI SWG members attend - yes
  • CP [ACTION] - will send out meeting details to everyone

• CP - 2 demos at delft

  • 1 - myGeoVerse
  • 2 - Gabor - Open Spatial Computing
  • request was for another demo looking using POI for navigation
  • Demo to add POI's on the fly - two different types of POI
  • 2022 state of the art example of POI based on workshop 12 months earlier
  • reached out to a member of faculty of TU Delft - asked them if they know of any datasets that we could use.
  • ST to reach out regarding exposing some Open Street Map material as POIs.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:22 EST

[geofizzydrink]

---

---

Minutes 2024-03-14

Participants

Matthew Purss
Howard Trickey
Chuck Heazel

Guests

Apologies

Stijn Tallir
Christine Perey
Joetta Kreck
Francois Fischer
Amy Youmans

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CH - Spec reviewed by OAB on 12 March

  • Generally well received
  • A couple of minor text and definition item issues identified
    • CH will fix.
  • Scott Simmons will be in touch re press release for the public comment period
  • Once the Press Release is ready we'll go out to public comment for 30 days.
  • Comments "May" come back and will need to be reviewed and addressed.
  • Once comments are responded to we will be good to send the spec up to the TC and PC for approval and publication.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 07:50 EDT

[geofizzydrink]

---

---

Minutes 2024-03-21

Participants

Matthew Purss
Howard Trickey
Stijn Tallir
Chuck Heazel
Christine Perey

Guests

Apologies

Joetta Kreck
Francois Fischer
Amy Youmans

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CH - Press Release is under control for the release to public comment - we're now just waiting in the queue for it to go out and start the public comment period.

• CP - Presentation for Monday - CH will deliver (10-12 min) on the data model, HT will deliver (10-12 min) on implementation from Google's perspective, ST will deliver (~10min) on Digital Flanders implementation of the standard, and finally Ali will provide an overview and demo of MyGeoVerse showcasing POIs through an app.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 07:50 EDT

[geofizzydrink]

---

---

Minutes 2024-04-11

Participants

Matthew Purss
Howard Trickey
Christine Perey

Guests

Apologies

Joetta Kreck
Francois Fischer
Amy Youmans
Stijn Tallir
Chuck Heazel

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CP - gave an overview of the Delft POI Session.

  • We should reach out throughout the OGC and POI-friendly community to try to get some more comments and feedback on the POI conceptual model
    • Reach Out Action: IndoorGML #133
    • Reach Out Action: ISG DWG #134
    • Reach Out Action: Ecere  #135
    • Reach Out Action: Overture Maps #136
  • we should create a wikipedia page for the POI Conceptual Model.
    • It should be managed by the OGC
    • need to reach out to OGC Staff to seek advice on establishing and maintaining such a page.
    • We should create a google doc to draft a POI Wikapedia page before submitting it for publication.
    • Use the SensorThings API as a model template for us to use - https://en.wikipedia.org/wiki/SensorThings_API
    • Reach Out Action: Create a Wikipedia Page #137
  • We should hold another webinar on POI
    • HT - we may have issues getting people enthused to come along and attend.
    • Reach Out Action: Produce a Webinar about POI Conceptual Model #138

• MP - Co-Chair nominations have gone out for the POI SWG in line with the 3rd Round of OGC WG Chair elections/re-confirmations. The list of nominee's will be voted on in around 30 days from now.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 07:50 EDT

[geofizzydrink]

---

---

Minutes 2024-04-18

Participants

Matthew Purss
Howard Trickey
Christine Perey
Amy Youmans
Stijn Tallir
Chuck Heazel

Guests

Apologies

Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - review from last meeting.

• CP - preview of the high level agenda for the POI SWG session in Montreal.

• • Status of feedback/ comments on Public Call - Outreach to those who need to review/respond
  • Ki-Joune Li - HT has reached out, but not hear back yet
  • ISG DWG - MP will reach out to the ISG DWG to request some feedback on the spec
  • Ecere - MP will reach out to the Ecere to request some feedback on the spec

• CP - Webinar schedule/plans - See thread

  • Date/time - 15 May - time TBD (tentative is 1300 UTC)
  • Chuck’s availability - pencilled in for 15 May
  • Slides - proposal is to use the same slides as we used for the Delft Meeting.

• CP - draft Wikipedia page here: https://docs.google.com/document/d/1TipZW2yj31FqJ7Hbqz8Ni01KWRXNW3OHwchUNDvUbm0/edit#heading=h.dspxuoeveiys

• HT - Carl Reed could be someone we talk to about getting the POI wikipedia page reviewed.

• MP - we should ask the question of the OGC Staff how they best want to manage a POI Wikipedia page (e.g. does the SWG manage it on behalf of the OGC or does the OGC want to manage it as part of their overall publication activities).

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:15 EDT

[geofizzydrink]

---

---

Minutes 2024-04-25

Participants

Matthew Purss
Howard Trickey
Stijn Tallir
Christine Perey

Guests

Apologies

Amy Youmans
Chuck Heazel
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Key Discussion Points

• MP - public comments re data model POI Data model feedback #143

1. Multilingual Support:
   How are multilingual names and descriptions handled in the POI model?

   • No multilingual descriptions - these are largely drawn from the ISO standards, which are primarily in English - CH @cmheazel please check.
   • MP I'm not sure if there are any restrictions on multilingual content being included for the parameters of a POI.

2. Enums Standard:
   Are there plans to support Standard Enums in the model?
   For Eg: https://schema.org/MedicalSpecialty

   • No "code lists"/"enums" in the data model - CH @cmheazel please confirm

3. Multidimensional Data:
   How are places at the same location(latitude, longitude) but different height/ depth handled in the model?
   For eg, places on flyovers(streetlight) or underwater POI etc

• This is a "Feature" issue not a "POI" issue.
• Support for multi-dimensional data are provided through the feature description and not the poi data model itself.
• we should provide an example of a 3D/4D POI showing how this is handled.

4. Containment:
   If a POI contains another, like a building at a location may contain multiple shops at the same level. How is this handled?

   • The cascading feature model deals with this. A Feature can be contained by another Feature. Each Feature object can be a POI as well as the containing Feature.
   • We need to provide a concise answer to this with examples to explain and show that a POI can be a feature itself and therefore referenced as the "hasFeatureOfInterest" of another POI.

5. Opening hours are part of the base standard model, is there a plan to add Payment info/ Currency info/ Ratings etc in the base model too?

   • MP - These would be included in the Payload to the POI.

• CP - we should close the loop with Micah re the webinar.

  • CP [ACTION - Done] - email Micah to sort out content and details of the webinar.
  • MP [ACTION] - reply to that email with the public announcement text to advertise the webinar.

• MP - review from last meeting.

• CP - preview of the high level agenda for the POI SWG session in Montreal.

• • Status of feedback/ comments on Public Call - Outreach to those who need to review/respond
  • Ki-Joune Li - HT has reached out, but not hear back yet
  • ISG DWG - MP will reach out to the ISG DWG to request some feedback on the spec
  • Ecere - MP will reach out to the Ecere to request some feedback on the spec

• CP - Webinar schedule/plans - See thread

  • Date/time - 15 May - time TBD (tentative is 1300 UTC)
  • Chuck’s availability - pencilled in for 15 May
  • Slides - proposal is to use the same slides as we used for the Delft Meeting.

• CP - draft Wikipedia page here: https://docs.google.com/document/d/1TipZW2yj31FqJ7Hbqz8Ni01KWRXNW3OHwchUNDvUbm0/edit#heading=h.dspxuoeveiys

• HT - Carl Reed could be someone we talk to about getting the POI wikipedia page reviewed.

• MP - we should ask the question of the OGC Staff how they best want to manage a POI Wikipedia page (e.g. does the SWG manage it on behalf of the OGC or does the OGC want to manage it as part of their overall publication activities).

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:54 EDT

[geofizzydrink]

---

---

Minutes 2024-05-02

Participants

Matthew Purss
Chuck Heazel
Howard Trickey
Stijn Tallir
Christine Perey

Guests

Apologies

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting

• CP - Draft Wikapedia page for POI

  • https://docs.google.com/document/d/1TipZW2yj31FqJ7Hbqz8Ni01KWRXNW3OHwchUNDvUbm0/edit#heading=h.dspxuoeveiys
  • Needs 5 references to be able to publish to wikipedia
    1. draft standard
    2. feature model
    3. uml
    4. tc/211
    5. OGC
  • Concept of web domain for POI
    • CH - let's reach out to OGC staff to ask the question of which other SWGs have successfully done this to promote OGC Standards.
    • MP - we want to be careful that we don't appear to be going outside of the OGC to promote an OGC Standard.

• HT - Internationalisation of POIs

  • CH - will need to make sure there is nothing in the model that precludes the ability to refer to multiple instances of objects with language codes.
  • CH - the overall problem appears to be solved for the web - i.e. language header info allows specific language versions of a webpage to be viewed.
  • HT - POIs will operate differently to a webpage - where the data provider might construct a single POI with different language variants.
  • CH [ACTION] - review data model to make sure that each element can support multiple instances with specific language codes.
  • HT [ACTION] - flesh out the user guide examples. We should explicitly state a language tag to these elements - will email this to CH.
  • ST - coming from a country with multiple official languages it makes sense to have a single POI object that has multiple instances of elements for specific languages.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:45 EDT

[geofizzydrink]

---

---

Minutes 2024-05-09

Participants

Matthew Purss
Chuck Heazel
Howard Trickey

Guests

Apologies

Stijn Tallir
Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting
• HT - Work on the internationalisation has been ongoing asynchronously with CH. There are still some things to consider and write up in both the response to comment(s) and the user guide. Work will continue on these over the next week.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 07:50 EDT

[geofizzydrink]

---

---

Minutes 2024-05-16

Participants

Matthew Purss
Chuck Heazel
Howard Trickey

Guests

Apologies

Stijn Tallir
Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting

• HT - Work on the internationalisation has been ongoing asynchronously with CH. There are still some things to consider and write up in both the response to comment(s) and the user guide. Work will continue on these over the next week.

• CH - lets recast the "User Guide" as an OGC "Best Practice" document.

  • [ACTION] - CH will check the correct process for this in the OGC Policies and Procedures
  • recasting as a Best Practice (an Official OGC Document) will give HT the due recognition he deserves.

• CH - finalising responses to comments and will post a PR once done.

• HT - will finish response to the "internationalisation - language" and "payment methods" comments.

• JSON encoding - CH suggests using GeoJSON as the base template for the POI JSON schema.

  • maybe look into FG-JSON as a way to express geometries in other CRSs (other than WGS84). Possibly as a separate implementation/profile.
  • CH will look into the JSON schema expression of POI.

• MP - send out meeting invites for POI SWG Sessions.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:00 EDT

[geofizzydrink]

---

---

Minutes 2024-05-23

Participants

Matthew Purss
Chuck Heazel
Howard Trickey
Stijn Tallir

Guests

Apologies

Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting

• CH - PR posted with responses to comments. still a couple of responses that need a little more work.

  • SWG no objection to the approval of the PR
  • CH will merge the PR later today.

• HT/CH - Internationalisation

  • HT - will have time next week to add more details regarding internationalisation
  • Next POI SWG meeting we should have more to discuss on this issue.
  • ST - maybe recast this as "multi-lingual" not "internationalisation" - Belgium has three (3) national languages so the term "internationalisation" isn't really a good description of this issue from the perspective of Belgium.

• MP - send out meeting invites for POI SWG Sessions.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:13 EDT

[geofizzydrink]

---

---

Minutes 2024-05-30

Participants

Matthew Purss
Chuck Heazel
Stijn Tallir
Howard Trickey
Christine Perey

Guests

Apologies

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting

• HT - has a little more clean-up work to do on the Best Practice PR and then will merge.

• ST - will look into describing a single or multi- POI database integration use case to include in the Best Practice.

• CH - PR with responses to comments for the POI Standard has been merged.

• MP - Do we push out the Spec and Best Practice (through the TC) together or one after the other?

• HT - has a proposal in the Best Practice PR to handle multi-lingual support

  • leverage the POI payload to handle multi-lingual variants of the object names.
  • CH - can be done with a minor update to the UML but will require a full build of the spec document.
    • Does the SWG agree with this approach? - SWG agrees
    • Abstract Feature Class needs to change (increase cardonality from 1 to >1)

• CP - webinar went very well and the video is posted.

• JSON encoding - CH probably easier for us to hand craft the JSON schema rather than the normal approach of outputing from the UML model.

  • CH - we will need to write the narrative around the schema for the implementation spec document.

• Part 2 = JSON encoding

• Part 3 = RDF encoding

• Part 4 = Google Proto-Buff encoding

• CP working with Micah to get the public promotion of POI done.

  • need to wait for the main spec to be published before we can post a Wikipedia page for the POI spec

• MP - send out meeting invites for POI SWG Sessions.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:25 EDT

[cperey]

@geofizzydrink can you please update attendance to capture that I participated in today's meeting? Thanks!

[geofizzydrink]

---

---

Minutes 2024-06-06

Participants

Matthew Purss
Chuck Heazel
Stijn Tallir

Guests

Apologies

Howard Trickey
Christine Perey

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting

• Things for us to do:

  • HT - clean up the Best Practice PR and then merge.
  • ST - describing a single or multi- POI database integration use case to include in the Best Practice.
  • CH - issue has been created with the agreed actions items to implement the International/multi-language labelling - Issue Abstract Basic Types #148
  • MP - JSON encoding schema.

• June Members Meeting POI Session - Agenda

  • intro - 5min
  • overview/status update of the main spec - 15 min
    • repeat of HT presentation from Delft/Workshop
  • overview/status update of the best practice - 30 min
    • HT & ST
    • Does the POI community think this is a best practice?... or are there additional/better practices that they would like to put forward.
  • JSON Encoding Discussion - 15 min
  • POI Standards Roadmap Discussion - 15 min
  • other busines - 10 min

Possible extensions to the POI Standard

• Part 2 = JSON encoding

• Part 3 = RDF encoding

• Part 4 = Google Proto-Buff encoding

• need to wait for the main spec to be published before we can post a Wikipedia page for the POI spec

• MP - send out meeting invites for POI SWG Sessions.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:25 EDT

[geofizzydrink]

---

---

Minutes 2024-06-13

Participants

Matthew Purss
Stijn Tallir
Christine Perey

Guests

Apologies

Howard Trickey
Chuck Heazel

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:08 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - brief overview of the last meeting

• Things for us to do:

  • HT - clean up the Best Practice PR and then merge.
    • Apology for this week (on a flight) will be at the meeting next week.
  • ST - describing a single or multi- POI database integration use case to include in the Best Practice.
    • Has made significant changes to text and created a PR up to the repo
    • MP Merged with main branch.
  • CH - issue has been created with the agreed actions items to implement the International/multi-language labelling - Issue Abstract Basic Types #148
  • MP - JSON encoding schema.
    • no progress - will work something up for the Members meeting session next week.

• June Members Meeting POI Session - Agenda

  • intro - 5min
  • overview/status update of the main spec - 15 min
    • repeat of HT presentation from Delft/Workshop
  • overview/status update of the best practice - 30 min
    • HT & ST
    • Does the POI community think this is a best practice?... or are there additional/better practices that they would like to put forward.
  • JSON Encoding Discussion - 15 min
  • POI Standards Roadmap Discussion - 15 min
  • other busines - 10 min

Possible extensions to the POI Standard

• Part 2 = JSON encoding

• Part 3 = RDF encoding

• Part 4 = Google Proto-Buff encoding

• need to wait for the main spec to be published before we can post a Wikipedia page for the POI spec

• MP - send out meeting invites for POI SWG Sessions.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:25 EDT

[geofizzydrink]

---

---

Minutes 2024-06-27

Participants

Matthew Purss
Stijn Tallir
Howard Trickey
Chuck Heazel

Guests

Apologies

Christine Perey

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:08 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• need to wait for the main spec to be published before we can post a Wikipedia page for the POI spec

• HT - discussed Best Practice PR

  • group discussion on titles of use cases in the Best Practice
  • will rewrite section on non-standard attributes
  • will write a discussion on the workflow/pathway to generating POIs for the Google use case.

• ST - no problems.

  • could maybe include a discussion on the workflow/pathway to generate POIs in bulk for the Digital Flanders user case.

• CH - drop Annexe D

  • make sure that there are not any references in the doc left pointing to Annex D
  • Every character class can have 2 or more instances throughout the model - PR will merge this in
  • FeatureID is a "scoped name" - a special class (other than a character string).

Suggested Standards Publication Process from here to September

• tidy up the conceptual model (as per present discussion)
• complete best practice guide
• POI Standard should go back to the OAB for a review - because we're making changes to the model that they have previously accepted.
• For September Members Meeting
  - post Standard doc and Best Practice Doc in Pending Docs
  - Make a motion to send the docs up to the TC for approval.
  -

HT - Next weeks meeting will be on 4th July - suggest we cancel in view that US members will be on holiday. MP will cancel and send a notice out.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:29 EDT

[geofizzydrink]

---

---

Minutes 2024-07-11

Participants

Matthew Purss
Howard Trickey
Chuck Heazel
Christine Perey

Guests

Apologies

Stijn Tallir

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:35 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• need to wait for the main spec to be published before we can post a Wikipedia page for the POI spec

• HT - was rewriting doc as a Best Practice guide - hit a blocker

  • not sure how best to represent the Internationalisation in JSON
  • created an issue More detail on internationalized strings #152
  • Will be unavailable for POI SWG meetings for the next 4 weeks.
  • CP - suggested we take a break from weekly POI meetings for the summer and reconvene on 8 August.

• CP - Montreal discussions with Linda van den Brink re POIs and Features API

  • MP - No examples of an OGC API Features server serving collections of POIs
    • There should be no real barrier to a POI being represented and served as a "Feature" via an OGC API Feature server.
    • The challenge is more related to the choice of data encodings the implementer of the API has implementented (e.g. GeoJSON, JSON-FG, JSON-LD, etc...)
    • But these are data encodings only. Any Feature object can be represented in any of these data encodings. POI (being a type of feature itself) is also able to be represented in these encodings.
    • The additional properties of a POI (e.g. the "payload") could/should be encoded as an additional JSON property included in the data encoding as additional detail.
  • CH - A POI is a standardised Feature Type that is derived from and consistent with the Feature Model.
  • MP - [ACTION] - will have a go at creating a POI via OGC API Features Demo - between now and the November Members Meeting.

• CH - PR's User Guide update in Choose Restaurant case #150 and Basic Types and internationalized text #151 - all complete and ready to merge

  • SWG happy for CH to proceed and Merge.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:52 EDT

[geofizzydrink]

---

---

Minutes 2024-08-22

Participants

Matthew Purss
Chuck Heazel
Stijn Tallir

Guests

Apologies

Christine Perey
Howard Trickey

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.
• CH - PR's merged
• MP need to hear from HT re the internationalisation strings in the Best Practice examples.
• [ACTION] MP to implement example POI outputs from OGC API Features server - first cut hopefully done by next week (maybe the week after). Aim is to have a working Demo that correctly shares POIs from OGC API Features Servers for the November Members Meeting.
• MP - will be in Seoul for the November Members Meeting - will try to secure a POI SWG session at a reasonable time for members.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 07:50 EDT

[geofizzydrink]

---

---

Minutes 2024-08-29

Participants

Matthew Purss
Chuck Heazel
Stijn Tallir
Howard Trickey
Knut Jetland
Christine Perey

Guests

Apologies

Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.

• HT - Internationalisation of POI's

  • response to a comment received during the public comment period
  • created a new object to cater for internationalised character strings
  • switched to a method of flagging the "language" of a string identifier
  • works well for JSON but has issues with XML
  • This is a problem that should have already been solved by others in the OGC community - but it doesn't appear to have been done.
  • Preference is for a return to the "internationalised string"
    • a more complex structure with the language attached.
  • CP - we should raise an issue within the OGC to work collectively to fill the gap
  • CH [ACTION] - will post an issue related to this to the OAB
    - User Guide is not normative so we can update this issue at any time, as a solution comes to hand, without having to wait for the publication process.
  • HT - new chapter on "past and present methods of shareing data" - this chapter can be used to flag and discuss a number of these unresolved issues and what is the current best practice to attempt to handle these.
  • ST - have we looked into the metadata standards?
    • There is a treatment of internationalised text.
    • HT there seems to be some gaps with those standards around describing the data
      • we are hoping/looking for the OGC to make a statement regarding how the Feature ID parameter of the Feature model to include the ability/option to use an internationalised string rather than a generic character string.

• MP - November Members Meeting - will try to secure a 1330-1500 (seoul time) slot for the POI SWG.

• MP - [ACTION] complete the example POI output from OGC API Features server (hopefully) by next week.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:25 EDT

[geofizzydrink]

---

---

Minutes 2024-09-05

Participants

Matthew Purss
Chuck Heazel
Stijn Tallir
Howard Trickey

Guests

Apologies

Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.

• HT - will have time to progress the Best Practice Guide later today.

• MP - Initial discussion on the examples of POI output from an OGC API Features server - example POI output from OGC API Features server #153

  • HT & CH - depending on the data encoding being output the "crs" for the geometry of the POI should also be included (e.g. for FG-JSON).
  • HT - for inclusion into the Best Practice Guide we should make sure only specified properties are included in the POI Feature object - with all other property items included (and defined in terms of schema) in the POI Payload.

• CH [ACTION-COMPLETE] - post an issue related to "internationalised string" to the OAB - Done.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:25 EDT

[geofizzydrink]

---

---

Minutes 2024-09-19

Participants

Matthew Purss
Chuck Heazel
Stijn Tallir
Howard Trickey

Guests

Apologies

Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.
• HT - progressing the Best Practice Guide
  • [REQUEST] Other people in the POI SWG to take a look at the "current best practice" section to enable informed discussion next week.
  • Seeking advice for the "name" and "address" fields

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 07:50 EDT

[geofizzydrink]

---

---

Minutes 2024-09-26

Participants

Matthew Purss
Stijn Tallir
Howard Trickey
Christine Perey

Guests

Apologies

Chuck Heazel
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.

• HT - walked through the "current practices" section of the Best Practice Guide

• GROUP - discussion on different methods/approaches to describing alternate names

• [ISSUE] - The autogenerated html/pdf versions of the Asciidoc files in the repo are not being updated properly - should happen every 24 hrs but last time the "Best Practice Guide" was built was 10 months ago.

  • CP has send an email to Greg and Gobe regarding this issue.

• ST - The Inspire Metadata spec has a useful method of dealing with internationalisation.

  • MP - we should check if this is an INSPIRE vs ISO Metadata approach. If both we can mention that, but if only described by the INSPIRE specs we should make that clear.

• HT - Will update the "current Practices" section with the above examples and flesh out the "non-standard attributes" section for next week's meeting.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:37 EDT

[geofizzydrink]

---

---

Minutes 2024-10-10

Participants

Matthew Purss
Chuck Heazel
Howard Trickey

Guests

Apologies

Christine Perey
Stijn Tallir
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.
• MP - update and discussion of CP's email regarding the OAB meeting where international parameters issue was raised.
  • ST (via email) - this issue is addressed in the INSPIRE standards (based on ISO 19115:2003)

Hi,
Regarding the discussion point from our last meeting: "MP - we should check if this is an INSPIRE vs. ISO Metadata approach. If both, we can mention that, but if it’s only described by the INSPIRE specs, we should make that clear."
Here’s how "Geographic Information — Metadata ISO 19115:2003" addresses multilingual support, as outlined in (informative) Annex J:
Multilingual Support for Free Text Metadata Elements
In this International Standard, a free text element may include multiple instances of information in different languages. Where the language differs from the language defined for the entire dataset, it can be identified, along with an optional attribute specifying the language variant used in a particular country, and the character set if it differs from the dataset default.
The rest of this Annex lists the metadata elements that support free text in multiple languages and provides an example of how these elements may be used.
Kind regards,
Stijn Tallir

Product Owner Historische Kaartlagen, Business Analist DataPublicatie, Functioneel Analist Metadata

Geo- en Open Data Diensten – Team Datamanagement

Afdeling Data-Oplossingen

• HT - depending on how we address this it will either be a "breaking" change to OGC legacy standards - or alternatively (and not as elegant a solution) an extension (non-breaking) that enables backward compatibility of existing implementations.
  • CH - we should respond to the OAB with preferably a single POI SWG solution to this issue and put it to the OAB to seek comment and input from other SWGs.
    • Noting ST's email referencing a solution that has already been published as an international standard will help our case with the OAB (i.e. it's not something we just dreamed up).
    • will check a full text copy of ISO 19115:2003 to make sure there are no other related things we need to consider - noting that this is now a superseded standard (replaced by ISO 19115:2017).
    • MP will have a look on the ISO portal to see if we can gain access to a version of ISO 19115:2017 to make sure the internationalisation treatment has not been changed between revisions of the ISO standard.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:20 EDT

[geofizzydrink]

---

---

Minutes 2024-10-24

Participants

Matthew Purss
Stijn Tallir

Guests

Apologies

Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer
Chuck Heazel
Howard Trickey

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.
• MP - set draft agenda for OGC Members Meeting POI Session
  • Intro & Logistics - 5 min
  • Discussion: Internationalisation - 60 min
  • Demonstration: POI's delivered via OGC API Features - 15 min
  • Other Business - 10 min
• ST - How does the INSPIRE solution to internationalisation compare with both the ISO 19115 approach and the approach HT has proposed?

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:10 EDT

[geofizzydrink]

---

---

Minutes 2024-11-21

Participants

Matthew Purss
Stijn Tallir
Chuck Heazel
Howard Trickey

Guests

Apologies

Christine Perey
Amy Youmans
Joetta Kreck
Francois Fischer

Meeting Started 07:30 EDT

Draft Agenda

1. Review of Minutes from last meeting
2. Update on Status of the Data Model
3. Update on Status of the Standard Specification
4. Update on Status of the User Guide
5. POI Standards Roadmap + ISO 19155
6. Review of Github Issues
7. Discussion/inclusion of any new Github Issues
8. Other Business

Response to comments
webinar
POI Domain name

Key Discussion Points

• MP - review of previous minutes.

• ST - How does the INSPIRE solution to internationalisation compare with both the ISO 19115 approach and the approach HT has proposed?

• [ACTION] - ALL OF US review the internationalisation discussion document Chuick has committed to the repo and provide comments and SWG approval before we send this to the OAB. Comments need to go into Issue More detail on internationalized strings #152

• HT - Address perameters in a POI handling the internationalisation of streetnames. Recommendation in the Best Practice Guide.

Motions from Members Meeting

SWG Motion
The POI SWG, having reviewed the analysis of alternatives (AOA) prepared by Howard Trickey, recommends that this AOA be provided to the OGC Architecture Board (OAB) to inform their discussions on internationalized text.

Motion: Gilles Cebelieu
Second: Stijn Tallir
Discussion:
Stijn Tallir - The INSPIRE Directive extended the early ISO 19115 and 19119 standards to meet EU-specific multilingual and interoperability needs, and later ISO versions evolved to incorporate similar multilingual and internationalization features, aligning more closely with INSPIRE's approach.
Chuck Heazel – The INSPIRE Directive applies to all EU nations and demonstrated to work well across the entire EU as a federated model for standards implementation. Therefore, we recommend the adoption of the INSPIRE approach to the Internationalization of text.

TC Motion - Request for eVote
The POI SWG recommends that the OGC Technical Committee approve an electronic vote to approve release of [OGC 21-049] “The OGC Points of Interest (POI) Conceptual Model Standard” as an OGC Standard.
Pending any final edits and review by OGC staff

Motion: Chuck Heazel
Second: Howard Trickey
Discussion:
A Best Practice document will accompany this standard and is expected to be ready for publication in December.

There was no objection to unanimous consent.

Actions and Open Github Issues

• Resources #40
• Use of Date and Time in POIs  #56
• What are Requirements for Time-sensitive PoI? #57
• _Meeting Minutes #58
• What happens/should happen to a POI that crosses/straddles the antimeridian? #63
• Can POIs be clustered/aggregated in a hierarchy? #65
• Are more POI properties needed to be standardized for the POI data interchange use case? #70
• "free" scheme for "category" #72
• Research and explore TN-ITS initiative and how it is relevant to POI  #78
• Write first draft of the clause with PoI publication use case #81
• Draft PoI User Guide Outline #82
• Clean up Philosophical Approach section of Nov briefing Transcript  #83
• Write (or retrieve) example representations #85
• Create an example for how to use POI CM in the case of automatically segmented 3D models of spaces #87
• Include in Conceptual Model a List of Recommended Property Types #94
• Is there need for including Priortization in the POI CM? #96
• Possibility to provide feedback on EU delegated regulation on EU-wide multimodal travel – new specifications for information services"" #103
• Data Model Examples for specific POIs #104

Meeting Closed 08:10 EDT