OK, I'll keep thinking about it and see if anyone else has something
to say. It's not a big deal to add the attribution - we respect the
TOS, that's why I asked. It just didn't look right for content that
was perhaps first located through Google, but not actually obtained
from there to bear the mention "clipped from Google". Also, since the
embeds are served live from the content owners and as such subject to
change, Google might not want us to claim that content was copied from
its index that might not actually be there.
Yes, Google results for Twitter not only reach back further (good for
offbeat or past-date subjects) but are generally more relevant. There
is no mystery to getting Twitter results from Google - it's just
another website: setSiteRestriction("twitter.com") works for me.
To your last point, if a lack of explicit permission implied
prohibition, that would mean that a licensor had anticipated all the
good ideas before any licensee. Google releases the APIs in order to
stimulate developers and I am sure they are regularly surprised by
what developers come up with. The terms of service need occasionally
to be revised to reflect unforseen cases that the licensor wishes to
disallow.
On Jun 24, 4:15 pm, Jeremy Geerdes <[email protected]> wrote:
> If you are comfortable with that interpretation, I guess that's up to you. I,
> however, would be extremely leery of it.
>
> Also, if I'm understanding correctly, you're getting Twitter results via
> Google because Google returns older results than the Twitter API will return.
> Since Twitter results are not available through the Search API, I can only
> assume that you're hacking something together using undocumented (i.e.,
> non-public) APIs and/or screen scraping, both of which would be against
> Google's existing TOS by default because, according to my admittedly limited
> understanding of legalese, if you do not have explicit permission to do
> something, you have an implicit prohibition.
>
> Jeremy R. Geerdes
> Effective website design & development
> Des Moines, IA
>
> For more information or a project quote:http://jgeerdes.home.mchsi.com
> [email protected]
>
> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan
> Church!
>
> On Jun 24, 2010, at 3:09 AM, Ken wrote:
>
> > Thanks Jeremy. We are not storing any part of the search results. We
> > are forwarding a fragment of the item (say, the youtube video id
> > extracted from the URL of the item), forwarding it to another service,
> > and then storing some of what is returned from that service. Sometimes
> > data that we store might look the same as data returned by Google, but
> > not always. For example, Google often truncates the title but we will
> > always store the full title.
>
> > We also use clipping to display Twitter statuses for a search query
> > (Google results include older tweets not available through the Twitter
> > API). We "clip" the status id from the URL and retrieve the full
> > metadata from the Twitter API. Our user can then reply and it is her
> > reply that is stored on our system.
>
> > So clipping does not necessarily involve storing. Clipping by means of
> > setOnKeepHandler can also be used to further manipulate data returned
> > by Google. My conclusion is that the manipulations mentioned above are
> > not covered by the TOS.
>
> > Of course any comments are welcome!
>
> > On Jun 24, 12:44 am, Jeremy Geerdes <[email protected]> wrote:
> >> I am not a legal expert in any way, so if you have any doubts whatsoever
> >> about what I'm about to say, you should by all means consult someone who
> >> is. That said, if you are storing any part of the search results for later
> >> display, the TOS explicitly require that you also display the "clipped
> >> from Google on [date]" text. I see no exceptions to that rule.
>
> >> Jeremy R. Geerdes
> >> Effective website design & development
> >> Des Moines, IA
>
> >> For more information or a project quote:http://jgeerdes.home.mchsi.com
> >> [email protected]
>
> >> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan
> >> Church!
>
> >> On Jun 23, 2010, at 1:46 PM, Ken wrote:
>
> >>> I have set up a Custom Search Engine to return links to embeddable
> >>> content (videos, Scribd docs, etc) that our users can add to their
> >>> blogs. Previously, we used a multitude of APIs to find this content,
> >>> but a Google CSE is much simpler.
>
> >>> I use the setOnKeepHandler to grab the url of the item and send it to
> >>> the API of the content provider in order to retrieve all we need to
> >>> embed the content.
>
> >>> My question is, is this use of setOnKeepHandler considered 'clipping'?
> >>> The embed that ends up on the user's blog page has not been clipped
> >>> from Google. It bears only a passing resemblance to the search result
> >>> returned by Google, and contains additional information returned by
> >>> the provider. Therefore I wonder if it is really logical, appropriate
> >>> or necessary to add the "clipped from Google" attribution to each
> >>> embed on a user's blog page...
>
> >>> Thanks for clarifying this!
>
> >>> --
> >>> You received this message because you are subscribed to the Google Groups
> >>> "Google AJAX APIs" group.
> >>> To post to this group, send email to
> >>> [email protected].
> >>> To unsubscribe from this group, send email to
> >>> [email protected].
> >>> For more options, visit this group
> >>> athttp://groups.google.com/group/google-ajax-search-api?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google AJAX APIs" group.
> > To post to this group, send email to
> > [email protected].
> > To unsubscribe from this group, send email to
> > [email protected].
> > For more options, visit this group
> > athttp://groups.google.com/group/google-ajax-search-api?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google AJAX APIs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en.
