W3C home > Mailing lists > Public > public-schemaorg@w3.org > May 2016

SearchAction vs FindAction, and OpenSearch totalResults equivalent

From: Tim Strehle <tim@strehle.de>
Date: Tue, 17 May 2016 11:58:52 +0200
Message-Id: <DB5BE699-8C3E-466E-A663-3F29857E8129@strehle.de>
To: public-schemaorg@w3.org
Hi,

I’m a schema.org newbie struggling with describing image searches and search results. I.e. there should be several endpoints to which one can send a query (and pagination info like search result page size and number), and get back a list of matching ImageObject items, along with some result metadata (number of total results, page size and number).

For some background, see my “RDF and schema.org for DAM interoperability” blog post:

 https://www.strehle.de/tim/weblog/archives/2015/05/08/1762

I think I understand how to use input properties (as described in http://schema.org/docs/actions.html ) to describe the required and optional query (search form) fields.

But how would I best return search results? Should I use https://schema.org/SearchAction or https://schema.org/FindAction (both with CompletedActionStatus)? What’s the difference?

Would I return an array of ImageObject items directly within the result property? 

If so, where would I put result metadata like the total number of results?

And is it true that there’s no schema.org equivalent for the OpenSearch elements “totalResults”, “startIndex” and “itemsPerPage”? See:

 http://www.opensearch.org/Specifications/OpenSearch/1.1/Draft_5#Elements

For pagination, I guess I could somehow link to potential “next page” and “previous page” actions. Where would I put them in my search results?

Sorry for so many questions in one post. Any input is appreciated :)

Thanks,
Tim Strehle
Received on Friday, 20 May 2016 16:04:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:25 UTC