[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Proposal for the addition of properties to the SearchResultsPage object in Schema.org
Here are a couple of examples. They can be found at http://test.viaf.org/VIAFSearchResultsPage.html and http://test.viaf.org/GoogleSearchResultsPage.html Example 1: A SearchResultPage from a search for the name “dempsey” on viaf.org. (Most of the baloney and content has been removed to simplify the example.) The properties “description”, “numberOfItems”, “item” and “significantLink” are demonstrated. (“description” is a property of a Schema.org Thing and “significantLink” is a property of CreativeWork and are inherited properties of SearchResultsPage.) This example uses RDFa lite markup. <html xmlns="http://www.w3.org/1999/xhtml" xmlns:re="http://oclcsrw.google.code/redirect" lang="en" xml:lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>VIAF</title> <link href="" type="application/opensearchdescription+xml" title="VIAF Search" rel="search"> </head> <body> <h2>Virtual International Authority File</h2> <div xmlns="http://www.w3.org/1999/xhtml" vocab="http://schema.org" typeof="SearchResultsPage"> <h2 property="description"><span property="numberOfItems">573</span> headings found for <span class="searchState">dempsey<script language="_javascript_">updateSearchForms('local.names', 'all', 'dempsey', 'viaf')</script> </span> </h2> <table> <tbody> <tr property="item"> <td>1</td> <td> <a href="" property="significantLink">Harrison, Harry, 1925-2012 <br>Harrison, Harry <br>Harrison, Harry, 1925-.... <br> </a> </td> </tr> <tr property="item"> <td>2</td> <td> <a href="" property="significantLink">Campbell, Joseph, 1904-1987 <br>Campbell, Joseph <br>كامبل، جوزيف، 1904 م- <br>Campbell, Joseph D. (Joseph Dempsey) <br> </a> </td> </tr> </tbody> </table> </div> </body> </html> Example 2: A SearchResultsPage from a Google search for “dempsey”. (Again, significantly simplified.) The properties “numberOfItems”, “item” and “significantLink” are demonstrated. This example uses Microdata markup. <html itemscope="itemscope" itemtype="http://schema.org/SearchResultsPage"> <head> <title>dempsey - Google Search</title> </head> <body> <div id="cnt"> Search 5 personal results. <span itemprop=”numberOfItems”>8,200,000</span> other results. </div> <div id="search"> <h2 class="hd">Search Results</h2> <ol> <li itemprop="item"> <h3 class="r"> <a href="" itemprop="significantLink">Clint <em>Dempsey</em> - Wikipedia, the free encyclopedia</a> </h3> </li> <li itemprop="item"> <h3 class="r"> <a href="" itemprop="significantLink">Jack <em>Dempsey</em> - Wikipedia, the free encyclopedia</a> </h3> </li> <li itemprop="item"> <h3> <a href="" itemprop="significantLink">Patrick <em>Dempsey</em> - IMDb</a> </h3> </li> </ol> </div> </body> </html> From: LeVan,Ralph I’m trying to start a conversation about adding properties to the SearchResultsPage in Schema.org. Currently, there are no properties for that object. My proposal is below. Opinions are solicited. If the conversation becomes extensive, I’ll start of a list for it. Ralph SearchResultsPage Properties: a proposal The OASIS Search Web Services Technical Committee has developed an abstract protocol definition of a search-and-retrieve operation (http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part1-apd/searchRetrieve-v1.0-cs01-part1-apd.html). The abstract response elements described in that document make good candidates for properties in the Schema.org SearchResultsPage object. Benefits: The SRU search protocol supports content negotiation, but the SRU protocol does not specify how HTML responses should be formed. A suitably decorated SearchResultsPage would be a completely satisfactory solution. NISO had at one time a Metasearch Initiative (http://www.niso.org/workrooms/mi). Its purpose was to propose a lightweight mechanism that would allow content providers a way to expose their content interoperably with federated search providers. A suitably decorated SearchResultsPage would have been a much better solution than the one that was ultimately proposed. The OpenSearch protocol describes how to return three search result properties in <meta> tags in an HTML response (http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML). This proposal extends the list of properties and makes them properties of the SearchResultsPage object. Model: A search result is modeled as a stream of items, not all of which can always be returned in a single response. A mechanism is assumed that will allow a client to retrieve all of the items through a sequence of responses. Some content providers model their response as a sequence of items and others as a sequence of pages (the abstract protocol definition calls them groups). Response elements are provided to support both models. For some search environments, a search is an expensive operation and search results are cached by name. A response element is provided to return a search result name. Proposal: Add these properties to the SearchResultsPage 1: numberOfItems: Integer: The number of items matched by the query. 2: numberOfGroups: Integer: The number of result groups in the result set. 3: resultSetId: Text: The identifier for the result set created by the query. 4: item: Text: An individual response item (one of possibly many). 5: nextPosition: Integer: The next position within the result set following the final returned item. (This would be used in a subsequent request to retrieve more items.) 6: nextGroup: Integer: The next result group following the group returned. 7: diagnostics: Text: Error messages and/or diagnostics. 8: echoedRequest: Text: The server may echo the request back to the client. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]