Re: Search requirements

I think so, from a semantic perspective, if not an implementation
perspective.
There is a resource (or should be) which contains content. Search that
content.

Whether any given system implements that for external resources, or for
different media types, is another question.

Rob

On Tue, Apr 28, 2015 at 2:01 PM, Denenberg, Ray <rden@loc.gov> wrote:

> Rob – when searching the content of the body ….
>
> The body can be (1) a resource, (2) a simple textual body, or (3) an
> embedded textual body.
>
> Would the requirements for searching body content apply in all three cases?
>
>
>
> Ray
>
>
>
> *From:* Robert Sanderson [mailto:azaroth42@gmail.com]
> *Sent:* Sunday, April 26, 2015 3:00 PM
> *To:* Web Annotation
> *Subject:* Search requirements
>
>
>
>
>
> To make progress on the search part of protocol, some proposed types of
> search that should be supported:
>
>
>
> Search by:
>
>
>
> * exact target URI
>
> * ... where the target URI might be in the hasSource of a SpecificResource
>
> * ... ignoring fragments
>
>
>
> * exact body URI
>
> * ... where the body URI might be in hasSource of a SpecificResource
>
> * ... or in foaf:page / skos:exactMatch of a SemanticTag
>
> * ... ignoring fragments
>
> * class of body (Tag, SemTag, Text, ...)
>
> * exact body content
>
> * keyword(s) in body content
>
> * phrase in body content
>
> * language of body content
>
> * format of body content
>
>
>
> * annotator URI
>
> * annotation's date
>
> * motivation
>
>
>
> Ordered By:
>
>
>
> * Date created/modified
>
> * Position in target resource (e.g. first annotations first)
>
> * Relevance to the query
>
>
>
>
>
> Am I missing anything?
>
>
>
> --
>
> Rob Sanderson
>
> Information Standards Advocate
>
> Digital Library Systems and Services
>
> Stanford, CA 94305
>



-- 
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305