{"id":2501,"date":"2021-04-23T09:09:56","date_gmt":"2021-04-23T09:09:56","guid":{"rendered":"https:\/\/www.ogc.org\/news\/public-comment-requested-on-ogc-api-common-candidate-standard-which-outlines-common-elements-for-all-ogc-apis\/"},"modified":"2021-04-23T09:09:56","modified_gmt":"2021-04-23T09:09:56","slug":"public-comment-requested-on-ogc-api-common-candidate-standard-which-outlines-common-elements-for-all-ogc-apis","status":"publish","type":"post","link":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/announcement\/public-comment-requested-on-ogc-api-common-candidate-standard-which-outlines-common-elements-for-all-ogc-apis\/","title":{"rendered":"Public Comment requested on OGC API – Common candidate standard, which outlines common elements for all OGC APIs"},"content":{"rendered":"

OGC API – Common – Part 1: Core serves as a solid foundation upon which all OGC APIs can be built.<\/em><\/p>\n

\"Banner<\/p>\n

The Open Geospatial Consortium (OGC) is seeking public comment on the candidate OGC API – Common – Part 1: Core<\/em> standard. Comments are due by May 24, 2021.<\/strong><\/p>\n

OGC APIs<\/a><\/em> usher in a new age for location information on the web, enabling a much simpler way to share and access location information that is consistent with the architecture of the Web. The OGC API <\/em>family of standards defines modular API building blocks to spatially enable Web APIs in a consistent way. Through the OGC APIs<\/em>, the OGC community is standardizing how location information can be integrated: by any developer, with any other type of information, and into any type of application.<\/p>\n

In the course of developing the family of OGC API <\/em>standards, some elements proved to be common across them all. OGC has documented these common elements in the form of the OGC API – Common<\/em> candidate standard.<\/p>\n

OGC API – Common<\/em> serves as a solid foundation upon which all OGC APIs <\/em>can be built. The candidate standard identifies resources, captures compliance classes, and specifies requirements that are applicable to all OGC API<\/em> standards.<\/p>\n

Since OGC API – Common<\/em> is the foundation for OGC API<\/em> standards, a stable baseline is required prior to developing those standards. Yet the OGC API – Common<\/em> standard cannot be finalized until it has been validated against those same standards. Therefore, the OGC API – Common<\/em> SWG decided that OGC API – Common<\/em> would go through at least two OGC Public Comment Periods. The initial request, in February 2020<\/a>, established a \u201cbeta\u201d version that was stable enough for use by other OGC API<\/em> standardization efforts. Now that there is sufficient implementation experience, this final request seeks comment on the OGC API – Common<\/em> candidate Standard as well as an answer to the question of whether OGC API – Common<\/em> should be a Standard.<\/strong><\/p>\n

An alternative approach to making OGC API – Common<\/em> an official OGC Standard has been proposed where OGC API – Common<\/em> would instead take the form of an official registry of API building blocks fundamental to all OGC API<\/em> Standards. In order to maintain the interoperability between different OGC APIs<\/em>, these building blocks are to be reused when developing OGC API<\/em> Standards. For more information, see this discussion on the OGC API – Common<\/em> GitHub Repo<\/a>.<\/p>\n

OGC Members interested in staying up to date on the progress of this standard, or contributing to its development, are encouraged to join the SWG via this link on the OGC Portal<\/a>.<\/p>\n

The candidate OGC API – Common: Part 1, Core standard<\/a> is available for review and comment on the OGC Portal. Comments are due by May 24, 2021, and should be submitted via the method outlined on the OGC API – Common – Part 1: Core Candidate Standard's public comment request page<\/a>.<\/em><\/p>\n

About OGC<\/strong>
The Open Geospatial Consortium (OGC) is an international consortium of more than 500 businesses, government agencies, research organizations, and universities driven to make geospatial (location) information and services FAIR – Findable, Accessible, Interoperable, and Reusable.
OGC's member-driven consensus process creates royalty free, publicly available geospatial standards. Existing at the cutting edge, OGC actively analyzes and anticipates emerging tech trends, and runs an agile, collaborative Research and Development (R&D) lab that builds and tests innovative prototype solutions to members' use cases.
OGC members together form a global forum of experts and communities that use location to connect people with technology and improve decision-making at all levels. OGC is committed to creating a sustainable future for us, our children, and future generations.
Visit ogc.org<\/a> for more info on our work.<\/p>\n

“<\/p>\n","protected":false},"excerpt":{"rendered":"

OGC API – Common – Part 1: Core serves as a solid foundation upon which all OGC APIs can be built.OGC has documented these common elements in the form of the OGC API – Common candidate standard.Since OGC API – Common is the foundation for OGC API standards, a stable baseline is required prior to developing those standards.Therefore, the OGC API – Common SWG decided that OGC API – Common would go through at least two OGC Public Comment Periods.An alternative approach to making OGC API – Common an official OGC Standard has been proposed where OGC API – Common would instead take the form of an official registry of API building blocks fundamental to all OGC API Standards.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_eb_attr":"","footnotes":""},"categories":[169],"tags":[],"class_list":["post-2501","post","type-post","status-publish","format-standard","hentry","category-announcement"],"acf":[],"_links":{"self":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/2501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/comments?post=2501"}],"version-history":[{"count":0,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/2501\/revisions"}],"wp:attachment":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/media?parent=2501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/categories?post=2501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/tags?post=2501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}