Future work Implementing JSON GeoJSON in an OGC Standard Engineering Report

2 Copyright © 2015 Open Geospatial Consortium. to execute JSON text dynamically as embedded JavaScript and the possibility of inserting malicious code that need further consideration. The document partially addresses the lack of an agreed method to validate semantically in JSON and possible alternatives for schema documents. The authors are particularly sensible to semantic and syntactic validation and most of the code shown in this document has been validated as much as current technologies allow it. This document proposes some alternatives and recommendations but a formal and clear solution is still needed.

1.4 Forward

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. 2 References The following documents are referenced in this document. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies. OGC 06-121r9, OGC ® Web Services Common Standard, Version 2.0 NOTE This OWS Common Standard contains a list of normative references that are also applicable to this Implementation Standard. IETF RFC 4627, The applicationjson Media Type for JavaScript Object Notation JSON, D. Crockford, http:www.ietf.orgrfcrfc4627.txt OGC 06-103r4, OGC Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture v.1.2.1 OGC 14-009r1, OGC Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context, Pedro Gonçalves, 2014 , https:portal.opengeospatial.orgfiles?artifact_id=57477 OGC 14-055 OWS Context GeoJson Encoding, Pedro Gonçalves, 2015, Soon publicly available for public comments. OGC 12-093 OWS-9 SSI UGAS Conversion Engineering Report. Copyright © 2015 Open Geospatial Consortium. 3 Please check the Bibliography at the end of this document for additional references. 3 Terms and definitions For the purposes of this report, the definitions specified in Clause 4 of the OWS Common Implementation Standard [OGC 06-121r9] shall apply. In addition, the following terms and definitions apply. 3.1 array one of the data types that the value of a JSON key can have. I contains a sorted list of unnamed values NOTE In fact, in JavaScript, an array is an object that has keys with consecutive numerical names. 3.2 declaration associate an JavaScript object with a name of a data type. 3.3 define Describe an JavaScript object data type by providing a list of its key properties, data type declarations and multiplicities. NOTE As you will read later in the text JSON-LD is able to declare but not to define. 3.4 key a JSON text that will represents the name of a variable in the JavaScript Document Object Model. 3.5 object one of the data types that the value of a JSON key can have. It contains a list of property keys. 4 Conventions

4.1 Abbreviated terms

Some more frequently used abbreviated terms: AJAX Asynchronous JavaScript And XML API Application Program Interface