From 91def1fe684d76efbd9949a87a3020a386ea4559 Mon Sep 17 00:00:00 2001 From: Joost van Ulden Date: Wed, 22 May 2019 14:33:41 -0700 Subject: [PATCH 1/7] Update scorecard layout Updated the layout of the scorecards and minor edits to improve readability. --- roadmap/non-webby-ogc-standards.md | 164 ++++++++++++++++------------- 1 file changed, 90 insertions(+), 74 deletions(-) diff --git a/roadmap/non-webby-ogc-standards.md b/roadmap/non-webby-ogc-standards.md index 2e6d818c..15dca969 100644 --- a/roadmap/non-webby-ogc-standards.md +++ b/roadmap/non-webby-ogc-standards.md @@ -6,131 +6,147 @@ The following is a list of OGC standards which are well-deployed in the geospati Criteria we use for a standard to be considered *Webby*: -- *`WWW-aligned:` The standard fully supports and follows the [fundamental concepts of current web architecture][1]*. This includes the use of URIs for identification; interaction using HTTP(S), content negotiation, and linking to other resources, including to secondary resources; and formats with agreed syntax and semantics. A representation of a resource is sent together with metadata, identifying the content-type. -- *`Accessible:` The standard is easy and simple enough for non-experts in geospatial data and geospatial information systems to understand and use*. Complexity in geospatial standards often stems from the fact that they cover a wide range of use cases, many of which are not required by non-experts. -- *`Web-oriented:` The standard is web-developer-friendly*, i.e. meets the expectations of many Web developers, for example by using encodings that are common on the Web, using HTTP verbs, etc. Note that this is a different criteria from the previous one; for example, it's about developers preferring encodings such as JSON to XML/GML. Note: what's 'developer-friendly' can be a trend sensitive thing. +- __WWW-aligned:__ The standard fully supports and follows the [fundamental concepts of current web architecture][1]*. This includes the use of URIs for identification; interaction using HTTP(S), content negotiation, and linking to other resources, including to secondary resources; and formats with agreed syntax and semantics. A representation of a resource is sent together with metadata, identifying the content-type. +- __Accessible:__ The standard is easy and simple enough for non-experts in geospatial data and geospatial information systems to understand and use*. Complexity in geospatial standards often stems from the fact that they cover a wide range of use cases, many of which are not required by non-experts. +- __Web-oriented:__ The standard is web-developer-friendly*, i.e. meets the expectations of many Web developers, for example by using encodings that are common on the Web, using HTTP verbs, etc. Note that this is a different criteria from the previous one; for example, it's about developers preferring encodings such as JSON to XML/GML. Note: what's 'developer-friendly' can be a trend sensitive thing. ## Web Map Service (WMS) -| `Scorecard` | | | +| __Scorecard__ | | | | ------------------------- |:------------:|:------------------------------------------------------------------------| -| `Criteria` | `Rating` | `Rational`| +| *__Criteria__* | *__Rating__* | *__Rational__* | | WWW-aligned | Yes | The fundemental concepts are adhered to. One could argue that a more RESTful approach would be a necessary step towards modernization of the standard. | | Accessible | No | Many of the required parameters assume a priori knowledge about OGC standards and geospatial concepts such as CRS, BBOX, Layers, Version, Service, etc. | | Web-oriented | No | WMS allows the use of parameterized URLs, but returns XML messages. No support for JSON.| ## Web Map Tile Service (WMTS) -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Web Map Tile Service (WMTS)| ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Web Coverage Service (WCS) -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Web Coverage Service (WCS)| ? | no | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | No | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Web Coverage Processing Service -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Web Coverage Processing Service| ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Catalogue Service (CSW) -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Catalogue Service (CSW) | no | ? | no | +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | No | Catalogue services cannot be crawled by web indexers. | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | -Rationale: Using http only as a transport protocol, sending XML messages back and forth. Catalogue services cannot be crawled by web indexers. ## Web Map Context -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Web Map Context | ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Web Processing Service -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Web Processing Service | ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Web Service Common -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Web Service Common | ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Sensor Observation Service -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Sensor Observation Service| ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using HTTP only as a transport protocol, sending XML messages back and forth. | ## Sensor Planning Service -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Sensor Planning Service | ? | ? | no | - -Rationale: Using http only as a transport protocol, sending XML messages back and forth. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | ? | | +| Accessible | ? | | +| Web-oriented | No | Using http only as a transport protocol, sending XML messages back and forth. | ## Observations and Measurements (O&M) GML encoding -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| O&M GML encoding | n.a. | ? | no | - -Rationale: The encoding is not web-developer-friendly. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | N/A | | +| Accessible | ? | | +| Web-oriented | No | The encoding is not web-developer-friendly. | -Note: The concepts of the standard have for a large part been incorporated in SSN. +> Note: The concepts of the standard have for a large part been incorporated in SSN. ## Timeseries (Profile of Observations and Measurements and the XML Encoding) -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Timeseries | n.a. | no | no | - -Rationale: The XML encoding is too complex and verbose - not lightweight enough to conduct, for example, enhanced (near) real-time operations involving moving objects, via the Web. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | N/A | | +| Accessible | No | The XML encoding is too complex and verbose. | +| Web-oriented | No | Not lightweight enough to conduct, for example, enhanced (near) real-time operations involving moving objects, via the Web. | ## Moving Features -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| Moving Features | n.a. | no | no | - -Rationale: The XML encoding is too complex and verbose - not lightweight enough to conduct, for example, enhanced (near) real-time operations involving moving objects, via the Web. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | N/A | | +| Accessible | No | The XML encoding is too complex and verbose. | +| Web-oriented | No | Not lightweight enough to conduct, for example, enhanced (near) real-time operations involving moving objects, via the Web. | ## IndoorGML -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| IndoorGML | n.a. | no | no | - -Rationale: Too complex and the GML encoding is not web-developer friendly. A JSON encoding might be created from the conceptual model, but people have indicated it may currently be too complicated for that. This standard is potentially relevant for mobile web applications, though. +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | N/A | | +| Accessible | No | Too complex and the GML encoding is not web-developer friendly. | +| Web-oriented | No | A JSON encoding might be created from the conceptual model, but people have indicated it may currently be too complicated for that. This standard is potentially relevant for mobile web applications, though. | ## CityGML -| `Scorecard` | webarch | simple | dev-friendly | -| ------------ |:------------:|:------------:|:------------:| -| CityGML | n.a. | no | no | -Rationale: The GML encoding is not web-developer friendly. There is a v0.9 JSON encoding (CityJSON). +| __Scorecard__ | | | +| ------------------------- |:------------:|:------------------------------------------------------------------------| +| *__Criteria__* | *__Rating__* | *__Rational__* | +| WWW-aligned | N/A | | +| Accessible | No | The GML encoding is not web-developer friendly. | +| Web-oriented | No | There is a v0.9 JSON encoding (CityJSON). | [1]: https://www.w3.org/TR/webarch/ [2]: https://w3c.github.io/web-roadmaps/sdw/ From f863820272001693fa25a14748a4ca9c3cb20a52 Mon Sep 17 00:00:00 2001 From: Linda van den Brink Date: Mon, 3 Jun 2019 08:27:58 +0200 Subject: [PATCH 2/7] Update f2f-4.html Added MapML update to agenda --- meetings/f2f-4.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meetings/f2f-4.html b/meetings/f2f-4.html index 177a3a4f..2823b260 100644 --- a/meetings/f2f-4.html +++ b/meetings/f2f-4.html @@ -223,6 +223,8 @@

Tuesday, June 25 (09:00 - 17:30)

From 8a11c8da65ce142920d1eac989ebf8036503ebe4 Mon Sep 17 00:00:00 2001 From: Tom Kralidis Date: Mon, 3 Jun 2019 06:34:43 -0400 Subject: [PATCH 3/7] fix typo on my last name --- meetings/f2f-4.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meetings/f2f-4.html b/meetings/f2f-4.html index 2823b260..0e44ea00 100644 --- a/meetings/f2f-4.html +++ b/meetings/f2f-4.html @@ -223,7 +223,7 @@

Tuesday, June 25 (09:00 - 17:30)

  • 09:00: Introduction + recap Monday + agenda Tuesday (chairs)
  • 09:30: ...
    • -
  • 17:00: Update on the Maps for HTML / MapML community activity part 1 (Tom Kradalis)
    • +
  • 17:00: Update on the Maps for HTML / MapML community activity part 1 (Tom Kralidis)
  • 17:00: Update on the Maps for HTML / MapML community activity part 2 (Amelia Bellamy-Royds)
From 9423a1be868af31b8c989c75f59885c6321fb7e3 Mon Sep 17 00:00:00 2001 From: Linda van den Brink Date: Tue, 4 Jun 2019 09:13:36 +0200 Subject: [PATCH 4/7] Update f2f-4.html Update agenda --- meetings/f2f-4.html | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/meetings/f2f-4.html b/meetings/f2f-4.html index 0e44ea00..069fa327 100644 --- a/meetings/f2f-4.html +++ b/meetings/f2f-4.html @@ -218,11 +218,16 @@

Monday, June 24 (09:00 - 17:30)

  • 09:00: Start - get meeting tech working, pick scribe, etc. (chairs)
  • 09:30: ...
    • +
  • 12:00: Lunch
    • +
  • 13:00: ...

Tuesday, June 25 (09:00 - 17:30)

  • 09:00: Introduction + recap Monday + agenda Tuesday (chairs)
    • -
  • 09:30: ...
    • +
  • 09:30: Update on WebVMT (Rob Smith)
    • +
  • 10:00: ...
    • +
  • 12:00: Lunch
    • +
  • 13:00: ...
  • 17:00: Update on the Maps for HTML / MapML community activity part 1 (Tom Kralidis)
  • 17:00: Update on the Maps for HTML / MapML community activity part 2 (Amelia Bellamy-Royds)
From 33c68e75b5a3806a3699d4068b66b8b5cf1a374b Mon Sep 17 00:00:00 2001 From: Linda van den Brink Date: Tue, 4 Jun 2019 09:15:08 +0200 Subject: [PATCH 5/7] Update f2f-4.html Correction --- meetings/f2f-4.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meetings/f2f-4.html b/meetings/f2f-4.html index 069fa327..6e1cebf9 100644 --- a/meetings/f2f-4.html +++ b/meetings/f2f-4.html @@ -229,7 +229,7 @@

Tuesday, June 25 (09:00 - 17:30)

  • 12:00: Lunch
  • 13:00: ...
  • 17:00: Update on the Maps for HTML / MapML community activity part 1 (Tom Kralidis)
    • -
  • 17:00: Update on the Maps for HTML / MapML community activity part 2 (Amelia Bellamy-Royds)
    • +
  • 17:15: Update on the Maps for HTML / MapML community activity part 2 (Amelia Bellamy-Royds)
    • From 7c8d9533359b6cce6cbe379b5bf6a9160109b566 Mon Sep 17 00:00:00 2001 From: Linda van den Brink Date: Wed, 5 Jun 2019 14:27:04 +0200 Subject: [PATCH 6/7] Update f2f-4.html --- meetings/f2f-4.html | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-) diff --git a/meetings/f2f-4.html b/meetings/f2f-4.html index 6e1cebf9..742f1019 100644 --- a/meetings/f2f-4.html +++ b/meetings/f2f-4.html @@ -214,22 +214,30 @@

    Remote attendance

    Agenda (draft)

    (All times are in Central European Summer Time / UTC+02:00)

    -

    Monday, June 24 (09:00 - 17:30)

    + +

    Monday, June 24 (13:00 - 18:00)

      -
    • 09:00: Start - get meeting tech working, pick scribe, etc. (chairs)
      • -
    • 09:30: ...
    • 12:00: Lunch
      • -
    • 13:00: ...
      • +
    • 13:00: Start - get meeting tech working, pick scribe, etc. (chairs)
      • +
    • 13:15: Spatial data on the Web BP implementation reports (Michael Gordon)
      • +
    • 14:15: OGC API hackathon report (Michael Gordon)
      • +
    • ...
    -

    Tuesday, June 25 (09:00 - 17:30)

    +

    Tuesday, June 25 (13:00 - 18:00)

      -
    • 09:00: Introduction + recap Monday + agenda Tuesday (chairs)
      • -
    • 09:30: Update on WebVMT (Rob Smith)
      • -
    • 10:00: ...
    • 12:00: Lunch
      • -
    • 13:00: ...
      • +
    • 13:00: Introduction + recap Monday + agenda Tuesday (chairs)
      • +
    • 13:15: Update on WebVMT (Rob Smith)
      • +
    • 13:45: ...
    • 17:00: Update on the Maps for HTML / MapML community activity part 1 (Tom Kralidis)
    • 17:15: Update on the Maps for HTML / MapML community activity part 2 (Amelia Bellamy-Royds)
      • +
    • 17:30: Summary, conclusions and next steps for SDWIG (chairs)
      • +
    • 18:00: Meeting closed
    From 54a68aacf27e91dce05326ec5043af13aaa82f9b Mon Sep 17 00:00:00 2001 From: Linda van den Brink Date: Wed, 5 Jun 2019 15:25:24 +0200 Subject: [PATCH 7/7] draft agenda update --- meetings/f2f-4.html | 24 ++++++++++++++++++------ 1 file changed, 18 insertions(+), 6 deletions(-) diff --git a/meetings/f2f-4.html b/meetings/f2f-4.html index 742f1019..0bed730e 100644 --- a/meetings/f2f-4.html +++ b/meetings/f2f-4.html @@ -222,25 +222,37 @@

    Agenda (draft)

    -->

    Monday, June 24 (13:00 - 18:00)

      -
    • 12:00: Lunch
    • 13:00: Start - get meeting tech working, pick scribe, etc. (chairs)
    • 13:15: Spatial data on the Web BP implementation reports (Michael Gordon)
    • 14:15: OGC API hackathon report (Michael Gordon)
      • -
    • ...
      • +
    • 14:30: Break
      • +
    • 14:45: Strategy funnel review (chairs)
      • +
    • 15:30: Spatial ontology / GeoSPARQL: update on work starting in OGC GeoSemantics DWG (Linda van den Brink / Joseph Abhayaratna)
      • +
    • 15:45: CRS content negotiation (Joseph Abhayaratna)
      • +
    • 16:15: Break
      • +
    • 16:30: Statistical data on the Web (Bill Roberts)
      • +
    • 17:30: Spatial data on the web Roadmap (Linda van den Brink)
      • +
    • 18:00: Meeting closed

    Tuesday, June 25 (13:00 - 18:00)

      -
    • 12:00: Lunch
    • 13:00: Introduction + recap Monday + agenda Tuesday (chairs)
      • -
    • 13:15: Update on WebVMT (Rob Smith)
      • -
    • 13:45: ...
      • +
    • 13:15: Video search with location - update on WebVMT (Rob Smith)
      • +
    • 13:45: OWL Time issues and amendments (Chris Little?)
      • +
    • 14:15: SSN issues, amendments and extensions part 1 (Simon Cox?)
      • +
    • 14:30: Break
      • +
    • 14:45: SSN issues, amendments and extensions part 2 (Simon Cox?)
      • +
    • 15:00: Extra time for discussions that were parked earlier
      • +
    • 16:00: Future (direction) of SDWIG after 2019 - discussion part 1 led by chairs
      • +
    • 16:15: Break
      • +
    • 16:30: Future (direction) of SDWIG after 2019 - discussion part 2 led by chairs
    • 17:00: Update on the Maps for HTML / MapML community activity part 1 (Tom Kralidis)
    • 17:15: Update on the Maps for HTML / MapML community activity part 2 (Amelia Bellamy-Royds)
    • 17:30: Summary, conclusions and next steps for SDWIG (chairs)
    • 18:00: Meeting closed
    - +