Defining type and ids

Copyright © 2015 Open Geospatial Consortium. 105

11.5 Sharing the context with several instances

Even if this was not illustrated before in this document the context part of a JSON-LD file can be stored in an independent file and included and shared by more than one instance. This way is context document part could be storied in the schemas.opengis.net and imported for each instance. 12 Recommendations This is the list of recommendations exposed before and collected here as a reference: Recommendation 1: Consider extending JSON schema to fully describe the properties of a feature type, including units in alphanumeric properties and CRS in the geometric attributes instead of having to repeat them in each instance. Target: OWS Common Recommendation 2: Consider the possibility that OGC assists the IETF team in moving the JSON Schema forward. Target: Architecture.DWG and OWS Common Recommendation 3: Consider the possibility that OGC defines specific types for OGCSIO geometry types. Target: Architecture.DWG and OWS Common Recommendation 4: Consider the combined use of JSON schema and the context section of a JSON-LD file possibly in combination with the ontologies linked to it as a means for validating a JSON file in the OGC. The next OGC Testbed could include a test on this approach as an activity. Target: Testbed-12 Recommendation 5: Consider the possibilities of using the namespace URIs in context section of a JSON-LD file as a means to connect to formal ontologies structured in OWL SKOS or other RDF encoding as a way to validate complex types in JSON files in the OGC. The next OGC Testbed could include a test on this approach as an activity. Target: Testbed-12 Recommendation 6: Consider TopoJSON as a model to create a JSON encoding that is different not just an extension, because addresses a topic that GeoJSON can not consider but can be mapped and automatically converted into a GeoJSON file using for example a JavaScript library. Target: OWS Common Recommendation 7: Connect work in previous testbeds about a WPS profile for topological applications with the TopoJSON to study the applicability and interoperability of TopoJSON in OGC standards such as WPS and WFS. Target: Testbed 12 Recommendation 8: Produce an OGC best practice for converting XML documents into JSON based on OGC 14-009r1 and some other considerations exposed in this ER. Target: OWS Common Recommendation 9: Include adding type keys to JSON objects as a good practice to makethe transition to JSON-LD and RDF easier. It is also good practice that type names are qualified with a abbreviated namespaces e.g.: ows:ServiceIdentification that could be later dereferenced using JSON-LD context. Target: OWS Common with OAB