OGC seeks public comment on Symbology Conceptual Core Model (SymCore)
The Symbology Conceptual Core Model (SymCore) is the basis for defining symbology rules for the portrayal of geographic data. The model is modular and extensible (one core model, many extensions), and also encoding agnostic (one symbology model, many encodings).
The work by the SymCore Standards Working Group that led to this proposal was done as a continuation of the OGC Symbology Encoding standard (SE 1.1), only with a focus on modularity and extensibility.
SymCore provides a consistent approach that:
- Provides the flexibility required to achieve adequate symbology rules for a variety of information communities, e.g. aviation symbols, weather symbols, thematic maps, etc, and;
- Achieves high-level styling interoperability without encoding dependencies.
As such, Symcore defines a more general and portable symbology model for use across the broad OGC standards baseline that can be applied to geospatial datasets as well as online geospatial data and mapping services.
Potential implementations of SymCore are expected to enhance OGC standards such as the Web Map Service, Web Feature Service, GeoPackage, and others. By sharing a common core, and using the extension mechanism, integration of these standards for the purposes of cartographic representation could be greatly simplified.
Last year, authors of the SCCM standard requested early public feedback in advance of finalizing the candidate standard to ensure that the work was reflecting the community’s needs. This announcement marks the start of the formal public comment period as the standard moves towards adoption.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template