search

opengeospatial / poi

OGC Points of Interest Encoding Specification
Apache License 2.0
20 stars 27 forks source link

Draft PoI User Guide Outline #82

Open cperey opened 1 year ago

cperey commented 1 year ago

We need a rough draft of the user guide. What content do we want?

cperey commented 1 year ago

Some options:

Howard: probably need to say something about going from a Conceptual Model to something concrete. What are the options? Schema, JSON, XML? Some general advice that is relevant to all use cases.

Matt: sounds good. This is not the spec. If UML and JSON are the languages for encoding. To be compliant, a developer needs a compliant implementation. But they can use other. Example representations can be included. Examples: generic and specifically following use cases. Created an issue for this #85

Howard: sounds right. Matt: Create a clause 5.

Howard: we need a section to explain the general philosophy that we are adapting existing feature models. This is an adaptation layer on top of it. What do you do if you have an existing feature model, but then you want to build a POI CM on top.? Chuck should write this (or we can take it from the transcript of the November briefing. Created issue #83

cperey commented 1 year ago

Howard: how to deal with attributes that are not defined in the standard but are needed for your use case.

One approach is to use the mechanism in the existing model to write self-describing attributes. Another is to extend the concrete schema beyond the basic CM offers/defines to add the attributes the developer needs.

Howard to write this section. Created a new issue #84