Query about results rendering and startIndex

[DeWitt Clinton]

[+opensearch list, -several email addresses that I believe are out of
service]

That's a good question.

If memory serves, I think we came to the conclusion that the subset of
elements that do exist are sufficient to provide a two-way mapping between
index-based and page-based search results. And that if we included
startPage as well then an inconsistent state could be reached.

We could add it now, of course, though we'd have to document that it should
be treated mutually exclusively with startIndex.

Thoughts?

-DeWitt

Dear all,
I have a question related to Draft 5 of the Open Search specification
located at
http://www.opensearch.org/Specifications/OpenSearch/1.1/Draft_5
Section 'Elements'
*'The "startIndex" element *
*The index of the first search result in the current set of search
results.'*
We note that you can express a result set in terms of startIndex but since
our OpenSearch API will allow navigation by page only we would like to use
a startPage element in the results instead. Is the lack of provision for
this in the document by accident or design?
we would like to say the following,
<feed ...>
...
<opensearch:totalResults>100</opensearch:totalResults>
<opensearch:startPage>1</opensearch:startPage>
<opensearch:itemsPerPage>10</opensearch:itemsPerPage>
...
<entry>
...
</entry>
</feed>
Cheers,
--
Vangent, A General Dynamics Company | NASA | ECS Evolution Development Programhttp://earthdata.nasa.gov/echo
Note: I am not a government employee and have no legal authority to obligate any federal, state, or local government to perform any action of payment.