[Requests] Comments about "OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard" and "

Andrea Aime andrea.aime at geo-solutions.it
Fri Aug 3 09:26:58 EDT 2018


*PART A*
1. Evaluator:  Andrea Aime
2. Submission: 17-003r0, OGC EO Dataset Metadata GeoJSON(-LD) Encoding
Standard

*PART B*

*Link category validation issue*
1. Requirement: /req/link
2. Implementation Specification Section number: 7.1.3
3. Criticality: Editorial
4. Comments/justifications for changes:
Example 5, 6, 7, 8 won't validate against the suggested schema due to the
"category" value used,
e.g. "http://www.opengis.net/spec/EOMPOM/1.1#CLOUD" vs the schema allowing
"CLOUD".
Either the example or the schema should be amended.

*Offering request and result*
1. Requirement: /req/operation
2. Implementation Specification Section number: 7.1.5
3. Criticality: Major
4. Comments/justifications for changes:
The request and response properties are defined as simple "objects",
leaving no way to the client
to interpret them (in particular, the request, should it try it issue it).
They should probably be better
specified, or, if there is a reason to keep them generic objects, the
reason should be clarified,
and it would be a good idea to set a target structure for requests using a
body with a mime type
(POST, PUT). The example seem to suggest "type" and "content" to be the
only mandatory properties.

*Examples*
1. Requirement:
2. Implementation Specification Section number: Annex F
3. Criticality: Editorial
4. Comments/justifications for changes:
Annex should contain, by title, examples, while at the moment only links to
schemas and vocabularies.
Full examples for a variety of real world cases would greatly increase the
readability and understandablity
of the spec, especially from the point of view of folks more interested in
the practical usage of the spec
(the spec is rich of snippets, what is missing is overall examples,
suggestions, one that describes
fully a SENTINEL1 product, one a SENTINEL2, and so on).

*Mapping for other sensor types*



*1. Requirement:2. Implementation Specification Section number: 3.
Criticality: Major4. Comments/justifications for changes: The
specifications seems to be concerned mostly about optical, SAR and derived
(processed)products, but does not seem to cover altimetric, atmospheric and
limb products.It also seem to "go away" from the notion of having the
separate classes, and describes attributeswithout mentioning the various
product classes.GeoJSON, even with a JSON schema reference, is extensible
and allows for extra attribute addition,but having some firm guidance in
the specification would help a lot in terms of interoperability.*
Also, it would be nice to see a section about custom extension to the base,
maybe including some
mission specific attribute, even just having a short chapter with an
example of a few extra attributes
from a real world case would benefit understanding (e.g., people coming
from a XML schema might
think the schema is fixed, or that the spec discourages extension by not
mentioning it).


-- 

Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it
------------------------------------------------------- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20180803/1c9f0085/attachment.html>


More information about the Requests mailing list