Volunteered Geographic Information (VGI) Workshopsosi.geonorge.no › kurs › september2018 ›...

®

Meeting Sponsors

Member Orientation

106th OGC Technical CommitteeOrléans, FranceAthina Trakas19 March 2018

Copyright © 2018 Open Geospatial Consortium

OGC®

THIS WEEK


OGC®

What is the Technical Committee (TC) ?

• Where the formal standards development consensus discussion and approval process occurs.

• Comprised of Domain Working Groups (DWGs, pronounced “dwigs”) and Standards Working Groups (SWGs, pronounced “swigs”)

• Work is guided by the TC Policies and Procedures


OGC®

How do I participate ?

• Attend meetings and have conversations!• Learn something new• Share something new• Compare notes

http://ogcmeet.org


http://ogcmeet.org/

OGC®

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 as well as updated on OGCmeet.org


OGC®

OGC OVERVIEW


OGC®

Commercial

GovernmentNGO

Research

University

The Open Geospatial Consortium

Europe

N. America

Asia / Pacific

Middle EastAfrica

S. America

Not-for-profit, international voluntary consensus standards organization; leading development of geospatial standards

• Founded in 1994.

• 515+ 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®

Programs

• Innovation Program (IP) - a global, innovative,hands-on rapid prototyping and testing programdesigned to unite users and industry in acceleratinginterface development and validation, and thedelivery of interoperability to the market

• Standards Program – Consensus standardsprocess similar to other Industry consortia (WorldWide Web Consortium, OMA etc.).

• Communications and Outreach Program–education and training, encourage take up of OGCspecifications, business development,communications programs

• Compliance Program - allows organizationsthat implement an OGC standard to test theirimplementations with the mandatory elements ofthat standard

Rapid InterfaceDevelopment

StandardsSetting

MarketAdoption

Testing &Certification

OGC®

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


OGC®

Five steps

1. Identify requirements2. Form a Standards Working Group (SWG)3. Create the Standard4. Submit Standard for internal review and public comment5. OGC members vote to approve Standard


OGC®

• Metadata• Service interfaces• Exchange encodings• Processing services

Data sharing and data services

Sponsored Interoperability Experiments and Testbeds

• Defense• Environment• Commerce• Science• Etc.

1. Identify requirements

Operational needs for data consistency or presentation

Domain Working Group

®

Commercial business drivers


OGC®

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


OGC®

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.


OGC®

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”


OGC®

2a. Community Standard

• We also have a 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


OGC®

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!


OGC®

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


OGC®

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 e-mail, simple majority


OGC®

STANDARDS PROGRAMOGC Programs and Structure

Board of Directors and Executive Staff

Communications & Outreach Program

RegionalServices

InteroperabilityEngineering

Standards Program

InteroperabilityProgram

Compliance


OGC®

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


OGC®

Technical Committee meetings

• Quarterly Meetings (N. America, Europe, Asia, Australasia)– December 2016 Taichung, Taiwan– March 2017 Delft, The Netherlands– June 2017 St. John’s, NL Canada– September 2017 Southampton, UK– December 2017 Palmerston North, New Zealand

• 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


OGC®

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.


OGC®

http://www.opengeospatial.org/projects/groups/wg



OGC®

Joining a DWG

• Get basic information– Public summary: http://www.opengeospatial.org/projects/groups/wg– OGC member-only details:

https://portal.opengeospatial.org/?m=projects&tab=3

• Just show up and participate• Join the DWG mailing list




OGC®

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


OGC®

http://www.opengeospatial.org/projects/groups/swg


http://www.opengeospatial.org/projects/groups/swg

OGC®

Joining a SWG

• Get basic information– Public summary: http://www.opengeospatial.org/projects/groups/swg– OGC member-only details:


• Sign the Observer Agreement




OGC®

Every DWG and SWG has a portal page

Go to https://portal.opengeospatial.org/?m=projects&tab=3and select the WG of interest



OGC®

OGC Architecture Board (OAB)

• Work with the TC and the PC to ensure architectural consistency of the Baseline and provide guidance to the OGC membership to ensure effective life cycle management

– 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


OGC®

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– http://www.opengeospatial.org/ogc/policies/directives#urn

• Current policy is to use uniform resource identifiers - urs - and not uniform resource names – urns.

• 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.


http://www.opengeospatial.org/ogc/policies/directives#urn

OGC®

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


OGC®

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


OGC®

Submitting 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:http://portal.opengeospatial.org/index.php?m=public&orderby=default&tab=2


http://portal.opengeospatial.org/index.php?m=public&orderby=default&tab=2

OGC®

OGC DOCUMENTS


OGC®

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.”

– Community standard (CS): A document developed external to the OGC and endorsed by the OGC membership as part of the OGC Standards Baseline.

• 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.


OGC®

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.


OGC®

Change Request (CR)

• Can be submitted by anyone – Member or non-Members• Use the public Change Request Submission application

– http://ogc.standardstracker.org/


http://ogc.standardstracker.org/

OGC®

Guide to the OGC

• Guide to the Open Geospatial Consortium (OGC), 2016

– https://portal.opengeospatial.org/files/?artifact_id=68511


https://portal.opengeospatial.org/files/?artifact_id=68511

OGC®

The OGC Reference Model (ORM)

• The OGC Reference Model (ORM) describes the OGCStandards Baseline focusing on relationships between the documents. The OGC Standards Baseline (SB) consists of the approved OGC Abstract and Implementation Standards and Best Practice documents.

• http://www.opengeospatial.org/standards/orm


http://www.opengeospatial.org/standards/orm

OGC®

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, 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

• http://www.opengeospatial.org/standards/as


http://www.opengeospatial.org/standards/as

OGC®

OGC Modular Specification

• Standard to be used for writing any document whose eventual purpose is the specification of requirements for software, services or data structures

• A set of testable constraints to which all OGCimplementation standards must conform

• https://portal.opengeospatial.org/files/?artifact_id=34762


https://portal.opengeospatial.org/files/?artifact_id=34762

OGC®

TC Policies and Procedures (TC PnP)

• 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:

http://docs.opengeospatial.org/pol/05-020r25/05-020r25.html

• A variety of FAQ and supporting documents can be found in a folder here:https://portal.opengeospatial.org/modules/files/details.php?m=files&artifact_id=22851


http://docs.opengeospatial.org/pol/05-020r25/05-020r25.html

https://portal.opengeospatial.org/modules/files/details.php?m=files&artifact_id=22851

OGC®

VOTING


OGC®

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….


OGC®

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


OGC®

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


OGC®

Votes in a TC Plenary

• A number of votes will occur in a TC Plenary

• The next slide has a table of voting types and who can vote

• Don’t worry – the TC Chair keeps track of the rules in TC Plenary votes!


OGC®

Table of votes that can occur in a TC Plenary

Vote Type Who canVote

White Paper, Discussion Paper, or Engineering Report

Any member

Approval of Domain WG Charter

Any member

Election of TC reps to the PC

Any member

Best Practices Paper TC Voting Member Only

Vote Type Who canVote

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



OGC®

Where do I learn more?

• This presentation

• Meeting key informationhttp://ogcmeet.org/

• Other meeting informationhttps://portal.opengeospatial.org/?m=public&orderby=default&tab=4


http://ogcmeet.org/

https://portal.opengeospatial.org/?m=public&orderby=default&tab=4

OGC®

INNOVATION PROGRAMOGC Programs and Structure



RegionalServices


Standards Program

InnovationProgram

Compliance


OGC®

OGC Innovation Program

Interoperability Experiment

Plugfest

OGC Network

Pilot

SpecificationsImplementationsDemonstrations

Types of Interoperability Program Initiatives

Testbed

StandardsProgram

This is unique to a SDO!


OGC®

Testbed 12

• Watch for Engineering Reports (ERs) coming out of the Testbed: – Significantly influence revisions to existing standards and potential

new standards– Can include best practices, user guides, others– Testbed 12 - 50 reports– Testbed 13 - Underway– Testbed 14 – In planning (Sponsor’s meeting this week)


OGC®

COMPLIANCE TESTINGOGC Programs and Structure



RegionalServices


Standards Program


Compliance


OGC®

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 March 2017, there are 908 Implementing and 236 Compliant products– http://www.opengeospatial.org/resource/products/stats


http://www.opengeospatial.org/resource/products/stats

OGC®

How does it work?


OGC®

COMMUNICATIONS AND OUTREACH

OGC Programs and Structure


OGC®

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 e-mail lists.


OGC®

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)– ISO– OGP– OpenMI– IHO– buildingSMART– DGIWG– GEO– IJIS– USGIF– UN-GGIM plus more


OGC®

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.– http://www.opengeospatial.org/ogc/regions

• 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, China, Canada


http://www.opengeospatial.org/ogc/regions

OGC®

REGIONAL SERVICESOGC Programs and Structure



RegionalServices


Standards Program


Compliance


OGC®

Regional 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• Support IP, Compliance, Outreach , Membership

opportunities• OGC Staff

– Europe, Central Asia, Africa – Athina Trakas– Americas and Asia/Pacific – Trevor Taylor– India – M.K. Munshi/ Trevor Taylor– Australia and Oceania – Denise McKenzie


OGC®

COLLABORATION AND COMMUNICATION TOOLS


OGC®

OGC member portal

• The Portal is designed to assist OGC Staff and Members in the management and conduct of all aspects of OGC related activities. http://portal.opengeospatial.org


http://portal.opengeospatial.org/

OGC®

E-mail

• The life-blood of the OGC

• Every Working Group has an e-mail list.

• An e-mail 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 e-mail list.

• Use the portal to subscribe as desired.


OGC®

Two critical OGC lists

[email protected]– Used for administrative, meeting, document review, calls for

participation, and voting announcements– Moderated– Mostly OGC staff posts to this email list

[email protected]– For technical discussions– Any member subscribed can post– Moderated


mailto:[email protected]


OGC®

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.


OGC®

Collaboration using GitHub

• Many standards activities using GitHub for code, schema, and document management

• Example: https://github.com/opengeospatial/CityGML-3.0

• Most are private repositories, more and more will be public


https://github.com/opengeospatial/CityGML-3.0

OGC®

Questions ?

• Points of Contact;– Standards Program – Scott Simmons

[email protected]– Innovation and Compliance Programs – Luis Bermudez,

[email protected]– Communications and Outreach – Denise McKenzie,

[email protected]

Staff Listing:

http://www.opengeospatial.org/ogc/organization/staff





Volunteered Geographic Information (VGI) Workshopsosi.geonorge.no › kurs › september2018 ›...

Documents

Transcript of Volunteered Geographic Information (VGI) Workshopsosi.geonorge.no › kurs › september2018 ›...