Public comments are a very important part of the OGF document approval process. Through public comments, documents are given scrutiny by people with a wide range of expertise and interests. Ideally, a OGF document will be self-contained, relying only on the other documents and standards it cites to be clear and useful. Public comments of any type are welcomed, from small editorial comments to broader comments about the scope or merit of the proposed document. The simple act of reading a document and providing a public comment that you read it and found it suitable for publication is very useful, and provides valuable feedback to the document authors.
Thank you for making public comments on this document!
Comments for Document: SAGA API Extension: Information Service Navigator API
|Author(s):||S. Fisher, A. Wilson|
|Public Comment End:||6 Aug, 2011|
- reads like a copy & paste from the SD API (see page 3)
- the underlying data model for both API is GLUE
- the entity data looks pretty much the same as a service description
=> What I am trying to say here is that there is a lot of overlap.
Wouldn't it be better to combine both APIs into a single package. At
the end of the day I am just traversing the data of a single
- It would be beneficial to describe which query and filter strings
from the SD package can be used. The SD declares different filters I
could not find in the ISN package (e.g. authz_filter).
My main point of feedback:
I'm not convinced that SD (a service) and ISN should map one-to-one.
From an application perspective, it would maybe make more sense to have a
kind of aggregate information service instead of multiple ones.
Of course, this could be AND, and not XOR.
Note that I welcome this effort in general.