Member Orientation 101st OGC Technical Committee Taichung, Taiwan

Member Orientation 101st OGC Technical Committee Taichung, Taiwan
Scott Simmons 4 December 2016 Copyright © 2016 Open Geospatial Consortium

This is a two-part presentation
A very short description of what is happening this week and how OGC Technical Committee meetings operate A more thorough description of the OGC and our activities Copyright © 2016 Open Geospatial Consortium

Copyright © 2016 Open Geospatial Consortium
But first, who am I? I am the Executive Director of the Standards Program, which means that I look after coordinating standards activities and chair the Technical and Planning Committees BS and MS in Geology I started as a petroleum geologist and learned GIS for very practical reasons 27 years work in oil & gas, engineering, and defense; assumed this position in the OGC in January 2015 But don’t worry, I was an active OGC member for over 10 years Oil is here GIS circa 1990 Copyright © 2016 Open Geospatial Consortium

The Technical Committee (TC)
Where the formal standards development consensus discussion and approval process occurs. Comprised of a number of Domain Working Groups (DWGs, pronounced “dwigs”) and Standards Working Groups (SWGs, pronounced “swigs”) Work is guided by the TC Policies and Procedures ✓ Copyright © 2016 Open Geospatial Consortium

The Three Week Rule Under the TC Policies and Procedures, any document that is to be discussed and voted on by the members must be submitted at least three weeks prior to a given meeting. The TC can vote to suspend this policy for a specific document vote. This requires a 2/3 majority of the voting Members present in order to override the Policies and Procedures Copyright © 2016 Open Geospatial Consortium

Where to submit documents for discussion
On the portal in the Pending Documents tab Members attending a TC meeting are strongly encouraged to review the documents in the Pending Documents catalog and read those of interest. These documents form the foundation for many of the discussions and votes that occur at an OGC TC meeting. To obtain the current list of pending documents, go to: Copyright © 2016 Open Geospatial Consortium

Schedules and agendas Defining the master schedule is a very fluid process Group chairs begin making meeting time requests almost as soon as the previous meeting ends According to OGC procedures, the master schedule is supposed to be “firm” 3 weeks prior to the meeting; the agenda is known to change up to the morning of the opening plenary Meetings are filling very quickly these days: “firm” is often 6 weeks prior! Final meeting schedule is provided when you register for the meeting. Changes occurring during the meeting are posted on the bulletin board near the OGC meeting registration desk Copyright © 2016 Open Geospatial Consortium

Votes happen all the time in the OGC
Votes can occur in any of the following venues: At the opening or closing Technical Committee plenary In any of the Working Groups In any of the TC sub-committees Votes can happen at face to face meetings or by electronic vote. There are rules regarding who can vote, when, and it what forum. These cases are now defined…. Copyright © 2016 Open Geospatial Consortium

Votes in a Domain Working Group
Can happen in face-to-face (F2F) meetings or by e-vote Anyone can vote in a DWG vote Simple majority of those present carries the vote No notice is required for votes in F2F meetings A notice is required for any DWG e-votes However, only one vote per member organization! Motions can be made on any topic, typically DWG votes are to release documents for TC approval or to state a position Copyright © 2016 Open Geospatial Consortium

Votes in a Standards Working Group
Can happen in F2F meetings or by e-vote Only voting members of the SWG can vote Simple majority of the official members carries the vote No notice is required for votes in F2F meetings A notice is required for any SWG e-votes SWG votes are all about the business of advancing a Standard Copyright © 2016 Open Geospatial Consortium

Votes in a TC Plenary A number of votes will occur in a TC Plenary. There will also be a variety of votes, including all the voting types identified in the previous slide. Therefore, it is important to know who can vote and when. The next slide has a table of voting types and who can vote. Don’t worry – Greg Buehler and I will keep track of the rules in TC Plenary votes! Copyright © 2016 Open Geospatial Consortium

Table of votes that can occur in a TC Plenary
Vote Type Who can Vote White Paper, Discussion Paper, or Engineering Report Any member Approval of Domain WG Charter Election of TC reps to the PC Best Practices Paper TC Voting Member Only Vote Type Who can Vote Approval of new standard electronic vote TC Voting member only Approval of a revision to standard e-vote Changes to TC P&P Architecture Board Election Copyright © 2016 Open Geospatial Consortium

The Open Geospatial Consortium
Not-for-profit, international voluntary consensus standards organization; leading development of geospatial standards Founded in 1994. 520+ members and growing 50+ standards Thousands of implementations Broad user community implementation worldwide Alliances and collaborative activities with ISO and many other SDO’s OGC was incorporated in 1994 as an international consortium devoted to making it easier to share, access, process and apply location information to decision making. Our mission is two fold: To advance the development and use of international standards and supporting services that provide geospatial interoperability. Serve as the global forum for the collaboration of geospatial data / solution providers and users. Since our inception we have grown from 8 initial members to over 520 industry, government, academic, research and NGO members representing the Americas, Europe, Asia/Pacific, the Middle East and Africa. Our membership is diverse and well suited for addressing interoperability challenges, with strong representation from the user and industry communities, as well as active participation by research and academic organizations. All of these organizations work fluidly in the OGC process to define “pain points” in interoperability and to drive solutions forward ni key OGC programs.

The OGC standards process
We are a Standards organization, so this is our main work product The OGC standards process Copyright © 2016 Open Geospatial Consortium

What is an OGC Standard? A document, established by consensus and approved by the OGC Membership, that provides rules and guidelines, aimed at the optimum degree of interoperability in a given context. Community requirements Member requirements Market trends Technology trends Copyright © 2016 Open Geospatial Consortium

Five steps Identify requirements Form a Standards Working Group (SWG) Create the Standard Submit Standard for internal review and public comment OGC members vote to approve Standard Copyright © 2016 Open Geospatial Consortium

1. Identify requirements
Operational needs for data consistency or presentation OGC Sponsored Interoperability Experiments and Testbeds Defense Environment Commerce Science Etc. Data sharing and data services Commercial business drivers Domain Working Group Metadata Service interfaces Exchange encodings Processing services Copyright © 2016 Open Geospatial Consortium

1a. Requirements from alliance partnerships
Internet Engineering Task Force (IETF) Organization for the Advancement of Structured Information Standards (OASIS) National Emergency Number Association (NENA) International Organization for Standards (ISO) World Wide Web Consortium (W3C) World Meteorological Organization (WMO) IEEE Technical Committee 9 (Sensor Web) TM Forum Open Grid Forum (OGF) buildingSMART Alliance Web3D Consortium As you can see, we have relationships – often formal Memorandums – with numerous standards organizations. Some of the relationships, such as the IETF, focus primarily on standards coordination and the use of OGC standards in IETF standards. Other relationships also include a much stronger marketing aspect, such as with the Open Grid Forum in which we do joint workshops and GSDI on which OGC staff participate at multiple levels and we also provide portal support (for some $$). Copyright © 2016 Open Geospatial Consortium

1b. Other sources of requirements
Output from other OGC Standards activity Current merged efforts of OWS Context and GeoPackage Existing encoding or service that owner would like to submit to OGC for adoption KML, CDB Rigor added to older work LandXML >> InfraGML CDB image courtesy of David Graham, CAE, Inc. Copyright © 2016 Open Geospatial Consortium

2. Form a SWG Write a charter (clear and precise guidance from OGC) Find at least 3 charter members Demonstrate business case Request Technical Committee (TC) to allow SWG to form I said “SWG” not “swig” Copyright © 2016 Open Geospatial Consortium

2a. Community Standard We now have a new type of standard: Community Standard Developed outside OGC and brought to OGC for adoption Does not need to follow OGC template or be compliant with the Modular Spec (more about this later) Must be widely implemented A SWG is not required for a Community Standard: the document is proposed for adoption by members Copyright © 2016 Open Geospatial Consortium

3. Create the Standard Develop use cases Identify dependencies Work within OGC policy Comply with OGC Abstract Specification and OGC Modular Specification Invite experts Perform iterative internal and public reviews Use collaboration tools! Copyright © 2016 Open Geospatial Consortium

4. Submit Standard for review
OGC review OGC Architecture Board check for compliance with Abstract and Modular Specifications OGC Naming Authority for URIs OGC staff for adherence to policies and Standards template Public review Fully-advertised public review of 30 days of draft Standard Public comments must be reviewed and either incorporated or discarded with cause Copyright © 2016 Open Geospatial Consortium

5. Vote to approve TC votes to recommend for adoption by Planning Committee (PC) Standard must be presented to TC in a meeting TC must vote at that presentation to issue an electronic vote 45 day electronic vote with minimum thresholds for sufficiency and majority (2/3 majority) PC votes to adopt Standard If YES vote from TC, PC vote initiated 14 day vote via , simple majority Copyright © 2016 Open Geospatial Consortium

OGC Programs and Structure
Copyright © 2014 Open Geospatial Consortium

Communications and Outreach
Board of Directors and Executive Staff Interoperability Engineering Standards Program Communications & Outreach Program Regional Services Interoperability Program Compliance OGC Programs and Structure Communications and Outreach Copyright © 2016 Open Geospatial Consortium

Communications and Outreach goal
Work with OGC members and user communities around the world to encourage "take up" or implementation of OGC standards, as well as to encourage new membership and engagement in OGC programs and initiatives. Includes management of all OGC communications resources such as the website, portal, and lists. Copyright © 2016 Open Geospatial Consortium

Strategic partnerships
Developing and maintaining Strategic Partnerships is a key function of the OGC staff: World Meteorological Organization (WMO) Global Spatial Data Infrastructure Association (GSDI) OSGeo OGP OpenMI TM Forum buildingSMART DGIWG GEO IJIS USGIF Environmental Modeling and Software (iEMS) Copyright © 2016 Open Geospatial Consortium

Regional forums OGC forums provide for OGC Members to communicate on a country or regional level, recognizing local language, cultural, and policy requirements. Further, forums: Promote and support OGC membership Coordinate participation in the OGC Promote policies, co-operative business development initiatives and public/private partnerships that support the use of OGC standards. Existing forums: Asia Forum, Europe Forum, France Forum, ILAF (Iberian and Latin-American Forum), India Forum, Korea Forum, Nordic Forum, North American, and MENA (Middle East and Northern Africa), Australia-New Zealand, UK-Ireland Copyright © 2016 Open Geospatial Consortium

Interoperability Program
Board of Directors and Executive Staff Interoperability Engineering Standards Program Communications & Outreach Program Regional Services Interoperability Program Compliance OGC Programs and Structure Interoperability Program Copyright © 2016 Open Geospatial Consortium

OGC Interoperability Program
This is unique to a SDO! Standards Program OGC Network Plugfest Pilot Technology Maturation And Compliance Interoperability Experiment Specifications Implementations Demonstrations Testbed Types of Interoperability Program Initiatives Copyright © 2016 Open Geospatial Consortium

Tesbed 12 just completed its demonstration
Watch for Engineering Reports (ERs) coming out of the Testbed: these significantly influence revisions to and new standards Copyright © 2016 Open Geospatial Consortium

Compliance Testing OGC Programs and Structure
Board of Directors and Executive Staff Interoperability Engineering Standards Program Communications & Outreach Program Regional Services Interoperability Program Compliance OGC Programs and Structure Compliance Testing Copyright © 2016 Open Geospatial Consortium

Compliance Program goals
Provide robust standard compliance solutions for geospatial communities Provide a process whereby compliance for OGC specifications can be tested. Increase systems interoperability Reducing technology risks As of 7 June 2016, there are 851 Implementing and 203 Compliant products Copyright © 2016 Open Geospatial Consortium

Regional Services OGC Programs and Structure
Board of Directors and Executive Staff Interoperability Engineering Standards Program Communications & Outreach Program Regional Services Interoperability Program Compliance OGC Programs and Structure Regional Services Copyright © 2016 Open Geospatial Consortium

Your local contacts Ready to assist with membership questions Can put you in touch with other members and/or staff for expertise Facilitate regional forums Attend regional conferences Copyright © 2016 Open Geospatial Consortium

Standards Program OGC Programs and Structure
Board of Directors and Executive Staff Interoperability Engineering Standards Program Communications & Outreach Program Regional Services Interoperability Program Compliance OGC Programs and Structure Standards Program Copyright © 2016 Open Geospatial Consortium

The Standards development program…
is where and how the OGC standards are processed and adopted and contains four primary operating units: OGC Technical Committee (TC) OGC Architecture Board (OAB) OGC Naming Authority (OGC-NA) OGC Planning Committee (PC) CityGML Levels of Detail Copyright © 2016 Open Geospatial Consortium

Technical Committee meetings
Quarterly Meetings (N. America, Europe, Asia, Australasia) September 2016 Orlando, FL USA December 2016 Taichung, Taiwan March Delft, The Netherlands June St. John’s, NL Canada September 2017 Southampton, UK Members can send representatives Meeting fees waived depending on membership level Many sessions are virtual via web/teleconference If you are a voting member, consider sending a proxy if you cannot attend a meeting Assign to OGC member, Technical Committee Chair as desired Copyright © 2016 Open Geospatial Consortium

Domain Working Groups (DWGs)
Where Members discuss technical requirements, use cases, and issues related to the development and revision of OGC standards. The results of OGC interoperability projects are presented and discussed. Many members present on the use of OGC standards. Any Member or invited guest can attend any DWG session. Copyright © 2016 Open Geospatial Consortium

Standards Working Groups (SWGs)
Groups that work on a new (candidate) OGC standard or revision to an existing OGC standard Members and invited experts may participate Guided by the OGC Policies and Procedures OGC Intellectual Property policies in full effect Usually work from 6 months to 18 months per deliverable Copyright © 2016 Open Geospatial Consortium

OGC Architecture Board (OAB)
Work with the TC and the PC to insure architecture consistency of the Baseline and provide guidance to the OGC membership to insure strong life cycle management of the OGC standards baseline Reviews all OGC standards and revisions to standards prior to public comment. General technology discussions and guidance Issue resolution Nominated and Elected by the OGC Technical Committee Election is currently underway Copyright © 2016 Open Geospatial Consortium

OGC Naming Authority (OGC-NA)
The OGC-NA controls the assignment of OGC Names to resources of interest in geographic information infrastructures. Series of policy documents here Current policy is to use http uri’s and not urn’s. Part of any OGC standards development process is to submit list of proposed URIs to OGC-NA for review. There is an OGC registry and a resolver for assigned names. Copyright © 2016 Open Geospatial Consortium

The Planning Committee (PC)
The Planning Committee provides guidance and the management structure for the Technical Committee and the Interoperability Program. Members participate in OGC business planning and market focus activities Manages the consortium’s technology release process Approves special negotiated memberships and committee participation Must be a Principal or Strategic Member or a TC representative to the PC to participate in PC activities Two TC representative positions are currently available Copyright © 2016 Open Geospatial Consortium

OGC Position documents
OGC Standard Implementation Standard (IS): A document containing an OGC consensus approved technology dependent (e.g, http) specification for interfaces, encodings, and related specifications based on the Abstract Specification. Testable. Abstract Specification (AS): A document (or set of documents) containing an OGC (and in numerous cases ISO) consensus on a technology independent model that describes an application environment for interoperable geoprocessing and geospatial data and services products. Each document is referred to as a “topic.” OGC Best Practice A document containing discussion of best practices related to the use and/or implementation of an adopted OGC standard or related technology and for release to the public. Best Practices Papers are the official position of the OGC and thus represent an endorsement of the content of the paper. Copyright © 2016 Open Geospatial Consortium

Other OGC documents Engineering Report (ER) A document that reports on some technical activity in an Interoperability Program Initiative. An ER is by default not a publicly available document, but can be approved as a Public Engineering Report by member vote. An ER does not represent the official position of the OGC nor of the OGC Technical Committee. Discussion Paper A document containing discussion of some technology or standards work for release to the public. Discussion Papers are not the official position of the OGC and contain a statement to that effect. White Paper A publication released by the OGC to the Public that states a position on a social, political, technical or other subject, often including a high-level explanation of an architecture or framework of a solution. A White Paper often explains the results or conclusions of research. Copyright © 2016 Open Geospatial Consortium

Collaboration using GitHub
Many standards activities using GitHub for code, schema, and document management Example: Most are private repositories, more and more will be public Copyright © 2016 Open Geospatial Consortium

OGC Guidance Documents

The OGC Reference Model (ORM)
The OGC Reference Model (ORM) describes the OGC Standards Baseline focusing on relationships between the baseline documents. The OGC Standards Baseline (SB) consists of the approved OGC Abstract and Implementation Standards and Best Practice documents. Copyright © 2016 Open Geospatial Consortium

OGC Abstract Specification
The Abstract Specification provides the conceptual foundation for most OGC specification development activities Open interfaces and protocols are built and referenced against the Abstract Specification, thus enabling interoperability between different brands and different kinds of spatial processing systems The Abstract Specification provides a reference model for the development of OGC Implementation Specifications Copyright © 2016 Open Geospatial Consortium

OGC Modular Specification
Contains requirements for writing standards to be used for any document whose eventual purpose is the specification of requirements for software, services or data structures A set of testable constraints to which all OGC implementation standards must conform Copyright © 2016 Open Geospatial Consortium

TC Policies and Procedures (TC PnP)
This document provides descriptions of roles, responsibilities, standards development and submission procedures, and procedures related to revisions of existing OGC standards. The current version can be found here: A variety of FAQ and supporting documents can be found in a folder here: Copyright © 2016 Open Geospatial Consortium

OGC Collaboration and Communication assets

The life-blood of the OGC Every Working Group has an list. An list can be Members only or public. Public lists require WG Member approval. Any OGC Member in good standing can subscribe to any OGC TC list. Use the portal to subscribe as desired. Copyright © 2016 Open Geospatial Consortium

Two critical OGC lists Used for administrative, meeting, document review, calls for participation, and voting announcements Moderated Mostly OGC staff posts to this list For technical discussions Any member subscribed can post Copyright © 2016 Open Geospatial Consortium

OGC wikis Any OGC Working Group can request a wiki. Just need to let OGC staff know Wikis can be Members only or also publicly accessible. Need Member approval to have a wiki public. Copyright © 2016 Open Geospatial Consortium

Member Orientation 101st OGC Technical Committee Taichung, Taiwan

Similar presentations

Presentation on theme: "Member Orientation 101st OGC Technical Committee Taichung, Taiwan"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Member Orientation 101st OGC Technical Committee Taichung, Taiwan

Similar presentations

Presentation on theme: "Member Orientation 101st OGC Technical Committee Taichung, Taiwan"— Presentation transcript:

Similar presentations

About project

Feedback