[Esip-discovery] RFC ready for internal review by Nov. 9
Lynnes, Christopher S. (GSFC-6102)
christopher.s.lynnes at nasa.gov
Wed Oct 10 17:10:09 EDT 2012
On Oct 10, 2012, at 3:39 PM, Pedro Gonçalves wrote:
> in section 7.2.7 you propose to use the namespace to convey the version of esip conventions being used
> but it seems that this XML namespace (esipdiscovery) is not actually used on the query and response XML elements
> and it is not easy to XPATH the namespaces list and get the version number
> wouldn't it be better to follow ATOM conventions and use the category element instead?
> for example at feed level you could use
> <category scheme="http://commons.esipfed.org/discovery/version" term="1.2" label="Version 1.2 of the ESIP Discovery Conventions"/>
> this is much easier to xpath and to quickly obtain the ESIP Discovery version
I actually started by trying to fit the version into the OpenSearch Description Document, and then tried to do the Atom feed response in a similar manner. The OSDD is actually where the version is most important for the OpenSearch case, because it's likely that the client has parsed that first before issuing any queries to get the Atom feed response. The main use for version in the Atom feed response is actually for the data casting folks (where there is not necessarily a search preceding acquisition of the Atom feed document.)
On the parsing aspect, I don't think it is necessary to extract the end part of the path to get the version, 1.2. I think you can consider the whole string to be "the version". In which case, the xpath is once again pretty easy. This may also be useful in distinguishing between, say, an OGC-compliant OpenSearch "version" and an ESIP-compliant OpenSearch "version".
Datacasting guys, what do you think? Pedro's suggestion would be closer to what Atom does, but then will be a very different formulation from the one found in the OSDD for OpenSearch...
> On Oct 10, 2012, at 4:09 PM, Lynnes, Christopher S. (GSFC-6102) wrote:
>> OK, think I am maxed out for now until i get some feedback on the ESIP Discovery RFC for the NASA Standards and Processes Group. It would be nice to submit this just before the ESDSWG Meeting, say Nov. 9.
>> Please look for:
>> o clarity
>> o understandability
>> o accuracy
>> If you can suggest (or even supply) more pictures for it, that would be good.
>> Here is the link: https://docs.google.com/document/d/1ymt5vsP2jw2YMVnc2B8uEI0BKTHcT4jSNVQzruLIFPA/edit
>> Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185
>> Esip-discovery mailing list
>> Esip-discovery at lists.esipfed.org
Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185
More information about the Esip-discovery