® Sponsored by Architecture DWG 98th OGC Technical Committee Washington, DC USA Carl Reed, Joan Maso 10 March 2016 Copyright © 2016 Open Geospatial Consortium

OGC ® Agenda Request for DWG review of TB 12 Engineering Report from Joan Maso: Linked Data and Advanced Semantics for Data Discovery and Dynamic Integration (LDS) Thread in OGC Testbed 12 to author an Engineering Report on the subject of JavaScript, JSON, JSON- LD. Request for DWG Review by Peter Vretanos: Testbed-12 Web Integration Service ER Request for DWG Review by Gobe Hobona. OGC® Testbed-12 Arctic Spatial Data Infrastructure Engineering Report. IETF GeoJSON update. Carl APIs and OGC - PC action to write a white paper. George P. will lead discussion OWS Common - discussion of ways forward. There will be discussion at the PC that resources be spent to contract with a student to edit OWS Common. The discussion on OWS Common in Architecture DWG should be to organize the task description for the student. Carl. JSON and GeoJSON continued discussions on best practice guidance. Copyright © 2016 Open Geospatial Consortium

OGC ® Detailed Meeting Slides are in Architecture DWG Meeting Folder URL For updated meeting slides – Copyright © 2016 Open Geospatial Consortium

® Sponsored by Informational DWG Motions No TC action required Copyright © 2016 Open Geospatial Consortium

OGC ® Copyright © 2016 Open Geospatial Consortium Motion on request for TB 12 ER Review The Architecture DWG agrees to accept the Testbed-12 JavaScript, JSON, JSON-LD Engineering Report for discussion, contributions and review in accordance with the TB12 schedule. Editor to provide schedule for the ER. –Moved: Joan Maso –Second: Frederic –Discussion: See Detailed slides. –NOTUC

OGC ® Motion on request for TB 12 ER Review The Architecture DWG agrees to accept Testbed-12 Web Integration Service Engineering Report for discussion, contributions and review in accordance with the TB12 schedule. Editor to provide schedule for the ER. –Moved Peter Vretanos –Second Joan Maso –Discussion –NOTUC Copyright © 2016 Open Geospatial Consortium

OGC ® Motion on request for TB 12 ER Review The Architecture DWG agrees to accept Arctic Spatial Data Infrastructure Engineering Report for discussion, contributions and review in accordance with the TB12 schedule. Editor to provide schedule for the ER. –Moved Gobe Hobona –Second Joan Maso –NOTUC Now about committing to authoring a section on “What this ER means to the DWG and the OGC” –Discussion Joan – all of the TB12 ERs have a similar request for “what it means to the DWG”. Copyright © 2016 Open Geospatial Consortium

® Sponsored by IETF GeoJSON Update Copyright © 2016 Open Geospatial Consortium

OGC ® Update IETF GeoJSON Revision of draft available here: – Since last fall, 90+ issues discussed and resolved. About 80% of the issues were editorial – geojson/issues?q=is%3Aissue+is%3Aclosedhttps://github.com/geojson/draft- geojson/issues?q=is%3Aissue+is%3Aclosed Now in Working Group Last Call (WGLC) –Two weeks to get any final comments into the WG process –If you join the GeoJSON WG list, you can also “vote”. The IETF uses +1, 0, -1 etc for these WG votes. Copyright © 2016 Open Geospatial Consortium

® Sponsored by API White Paper George Percivall Copyright © 2016 Open Geospatial Consortium

OGC ® Much of the meeting was on discussion of the Open GeoSpatial API White Paper George provided overview of the White Paper Really good and vigorous discussion on definition of an API –Agreement to remove “client” from summary and change to patterns of implementation. –Definition versus language (e.g. IDL viz Java). IDLs can be compiled. –Many different views of what an API is/does. Best if OGC puts a stake in the ground and just move forward. –Perhaps three concepts: Abstract, Binding, Implementation. –Qualify use of API due to all of ambiguities and misuse in the market. Example: Web API. –Action: Please provide comments on the white paper. Copyright © 2016 Open Geospatial Consortium

® Sponsored by OWS Common: The Way Forward Copyright © 2016 Open Geospatial Consortium

OGC ® OWS Common Motion OWS Common should transition from current structure to be compliant with the Mod Spec so that requirements are clearly stated. Having the requirements clearly stated will be very helpful in transitioning from the current OWS Common to meet future and evolving OGC standards requirements. –Moved: John Herring –Second: Joan Maso –Discussion: See detailed slides. Copyright © 2016 Open Geospatial Consortium

OGC ® Actions Members provide comments on the OGC Open Geospatial API White Paper Communicate Architecture DWG OWS Common motion to the Planning Committee. Copyright © 2016 Open Geospatial Consortium