Re: [uf-discuss] OpenSearch

2006-08-30 Thread Stephen Paul Weber

Currently I use an hAtom+XOXO mix for search results on my pages, but
I have found that hAtom works sufficently for most -- I just wasn't
sure if this was a 'proper' use of it... but I figure it probably is
since you can have RSS for search too...
  -- Singpolyma

On 8/30/06, David Janes [EMAIL PROTECTED] wrote:

This looks very possible. In particular,

(1) according the article, Yahoo only returns its results in HTML, so
we know HTML is good
(2) one could add an extra field to the OpenSearch XML (a description
file about how your results are returned) indicating that the file is
hAtom
(3) parties not understanding hAtom can just display HTML
(4) parties wating to understand hAtom can do it themselves or use a webservice

When I was at MashupCamp in January (Feb?) there was a guy from
A9/OpenSearch very interested in mashup type applications and
developer feedback so there's a door open for us.

I'll also note that his WordPress integration problem will probably go
away if we did this, as an independent XML-feed result will not have
to be returned;

Regards, etc...
David
http://blogmatrix.blogmatrix.com

On 8/30/06, Scott Reynen [EMAIL PROTECTED] wrote:
 On Aug 29, 2006, at 10:23 PM, Ted Drake wrote:

  It's slightly off topic, but I thought I'd share my latest post
  about how we
  added the OpenSearch protocol to the Yahoo! Tech site. This open
  protocol
  lets you define how your web site's search engine works and then
  activates
  the personal search box in IE7 and Firefox 2. It also helps the
  aggregating
  search engines, such as A9.
 
  http://www.last-child.com/add-opensearch-to-your-web-site/
 
  Sorry if it is too off-topic.

 I'm not sure this is off-topic at all.  I think OpenSearch solves a
 problem by extending RSS that microformats could solve by extending
 HTML, possibly hAtom specifically.  The problem is identifying search
 results for reuse in aggregation, reformatting, etc.  The use cases
 are obvious as there are plenty of applications that already reuse
 this type of data and could benefit from a standard format for
 already published search results (A9, OS X Sherlock, etc.), there's
 certainly no shortage of search results on the web to use as real-
 world examples from the general web searches to very narrow-focus
 searches, and between hAtom and OpenSearch, I suspect most of the
 work is already done.  hSearch?
 `
 Peace,
 Scott
 ___
 microformats-discuss mailing list
 microformats-discuss@microformats.org
 http://microformats.org/mailman/listinfo/microformats-discuss

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss




--
- Stephen Paul Weber, Amateur Writer
http://www.awriterz.org

MSN/GTalk/Jabber: [EMAIL PROTECTED]
ICQ/AIM: 103332966
NSA: [EMAIL PROTECTED]
BLOG: http://singpolyma-tech.blogspot.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] OpenSearch

2006-08-30 Thread Edward Summers

On Aug 30, 2006, at 9:36 AM, David Janes wrote:

The reason I think that (2) is needed is:

(a) profiles are not manditory, so we can't depend on their presence
(b) the search-results consumer, knowing that there is hAtom search
results, may want not to read the URL at all (prefering a proxy to do
it)
(c) there is and will continue to be pages that have HTML but not  
hAtom


So are you proposing an extension to OpenSearch to support hAtom; or  
that a MIME type is established for hAtom?


//Ed
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] OpenSearch

2006-08-30 Thread Edward Summers

On Aug 30, 2006, at 9:52 AM, David Janes wrote:

I'm not sure how to be clearer: my first message in this thread
suggests in point (2) add a single-field extension to OpenSearch XML;
my second message says adding a MIME type is not the solution [1].


OK, so an extension to OpenSearch since OpenSearch currently uses  
MIME types to distinguish the type of a response. IMHO this is  
undesirable since it essentially makes opensearch treat microformats  
(hAtom) as a special case.


But maybe I've got something wrong here with my understanding of  
OpenSearch. I just pinged people over on opensearch-discuss [1] to  
take a look at this thread so maybe more light is available.


//Ed

[1] http://opensearch.org/pipermail/discuss/2006-August/57.html
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] OpenSearch

2006-08-30 Thread Scott Reynen

On Aug 29, 2006, at 11:28 PM, David Janes wrote:


(2) one could add an extra field to the OpenSearch XML (a description
file about how your results are returned) indicating that the file is
hAtom


There are two problems here, and I think we should avoid approaching  
both at once.  Just as a blog description was tabled until after  
hAtom, I think a search results description should be tabled until  
after there are microformat search results to be described.  How  
exactly is Yahoo indicating which HTML is search results?  That's not  
part of the OpenSearch standard as I'm reading it, and I don't see  
anything equivalent to OpenSearch's RSS and Atom syntaxes in Yahoo's  
HTML.


Peace,
Scott

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] OpenSearch

2006-08-30 Thread Edward Summers

more light:

  http://wiki.unto.net/OpenSearch_and_microformats

//Ed
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


RE: [uf-discuss] OpenSearch

2006-08-30 Thread Ted Drake
I'm not sure if I understand the theory behind the twiki of OpenSearch and
Microformats.

Are you suggesting I modify the opensearch.xml file to include microformat
values, so that when A9 and other search engines gather the content, they
can insert the microformat into their results?

A9 does not support HTML search pages at this time. I tried to register our
OpenSearch with them and the response was that they only accept RSS and atom
at this time.

I haven't looked at hAtom yet. If I can add some microformatting to our
search results, I'd be happy to try it.

This is a sample product result from the search result page. Where would the
OpenSearch/hAtom microformats be added?


div class=product id=prod8
div class=prodTitle
h4a href=/pr/apple-ipod-shuffle-512mb-mp3-player/1991675140 Apple iPod
shuffle 512MB MP3 Player/a/h4
div class=ytcompareProductCheck
label class=compareLabel for=a1991675140Select this product to be
compared with others/labelinput class=ytcompProdCheckBox name=id
id=a1991675140 value=1991675140 type=checkbox
/div
/div
div class=ytImgThumbContainera
href=/pr/apple-ipod-shuffle-512mb-mp3-player/1991675140 
class=ytprodThumbLinkimg class=prodThumb
src=http://f3c.yahoofs.com/shopping/mcid2_17104/simg_t_tcatalog_l_t19916751
401105478782jpg85?rm_Dy10zfXDq alt=/a/div
div class=ytRatingsContainer
ul class=ytratingsul
li class=overall stars8
span title=Yahoo! Users gave this product  4.19 out of 5 stars for overall
quality4.19/5 /spanb class=ytuserRatings559img
src=/images/userratings.jpg alt=this product has user ratings/b
/li
li class=ytSpecInstalled Memory: 512 MB/li
li class=ytSpecAudio Format: AAC, AIFF, MP3, WAV/li
li class=ytSpecSystem Compatibility: Mac, PC/li
/ul/div
divul class=priceInfo
li class=ytPrice
span class=priceLow$66.49/span - span class=priceHigh$74.05/span
  in 6 stores/li
li class=pricebuttona href=/pp/1991675140
class=ytbtncomppricesCompare Prices/a/li
/ul
/div

Thanks for your help, I'd love to extend the OpenSearch and Microformatting
as much as possible.

Ted


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Edward
Summers
Sent: Wednesday, August 30, 2006 7:22 AM
To: Microformats Discuss
Subject: Re: [uf-discuss] OpenSearch

more light:

   http://wiki.unto.net/OpenSearch_and_microformats

//Ed
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] OpenSearch

2006-08-30 Thread Scott Reynen

On Aug 30, 2006, at 10:43 AM, Ted Drake wrote:

This is a sample product result from the search result page. Where  
would the

OpenSearch/hAtom microformats be added?


For the results section, you'd just be adding hAtom to the results,  
which someone more involved with hAtom would probably explain better  
than I.  But to make an HTML version of OpenSearch, you'd also need  
to identify that those hAtom entries are search results part of a  
larger set.  A quick one-to-one mapping of OpenSearch to HTML looks  
something like this:


pResults span class=start-index21/span to 30 of span  
class=total-results423/span, span class=per-page10/ 
span per page./p

input type=text class=search-terms value=New York History /

That's taken from the example here:

http://opensearch.a9.com/spec/1.1/response/#rss

That's a slightly different format of information that can be  
inferred, but is not explicitly published on Yahoo! Tech.  For  
example, I can see there are ten results per page, but that's not  
stated anywhere.  And I can assume that page one starts at an index  
of 1, and page 2 at an index of 11, but that's also not published  
currently.  The total results and search terms are already published,  
so they would just need class names to match the OpenSearch  
properties.  And the difference between Yahoo's HTML and the  
OpenSearch properties (e.g. page vs. index, stated per-page vs.  
unstated) would need to be worked out through collecting more  
examples and seeing which is more representative of the implied  
schema for search results across the web.


Peace,
Scott

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


[uf-discuss] OpenSearch

2006-08-29 Thread Ted Drake
Hi All
It's slightly off topic, but I thought I'd share my latest post about how we
added the OpenSearch protocol to the Yahoo! Tech site. This open protocol
lets you define how your web site's search engine works and then activates
the personal search box in IE7 and Firefox 2. It also helps the aggregating
search engines, such as A9.

http://www.last-child.com/add-opensearch-to-your-web-site/

Sorry if it is too off-topic.

Ted Drake
Yahoo! Tech
 


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] OpenSearch

2006-08-29 Thread David Janes

This looks very possible. In particular,

(1) according the article, Yahoo only returns its results in HTML, so
we know HTML is good
(2) one could add an extra field to the OpenSearch XML (a description
file about how your results are returned) indicating that the file is
hAtom
(3) parties not understanding hAtom can just display HTML
(4) parties wating to understand hAtom can do it themselves or use a webservice

When I was at MashupCamp in January (Feb?) there was a guy from
A9/OpenSearch very interested in mashup type applications and
developer feedback so there's a door open for us.

I'll also note that his WordPress integration problem will probably go
away if we did this, as an independent XML-feed result will not have
to be returned;

Regards, etc...
David
http://blogmatrix.blogmatrix.com

On 8/30/06, Scott Reynen [EMAIL PROTECTED] wrote:

On Aug 29, 2006, at 10:23 PM, Ted Drake wrote:

 It's slightly off topic, but I thought I'd share my latest post
 about how we
 added the OpenSearch protocol to the Yahoo! Tech site. This open
 protocol
 lets you define how your web site's search engine works and then
 activates
 the personal search box in IE7 and Firefox 2. It also helps the
 aggregating
 search engines, such as A9.

 http://www.last-child.com/add-opensearch-to-your-web-site/

 Sorry if it is too off-topic.

I'm not sure this is off-topic at all.  I think OpenSearch solves a
problem by extending RSS that microformats could solve by extending
HTML, possibly hAtom specifically.  The problem is identifying search
results for reuse in aggregation, reformatting, etc.  The use cases
are obvious as there are plenty of applications that already reuse
this type of data and could benefit from a standard format for
already published search results (A9, OS X Sherlock, etc.), there's
certainly no shortage of search results on the web to use as real-
world examples from the general web searches to very narrow-focus
searches, and between hAtom and OpenSearch, I suspect most of the
work is already done.  hSearch?
`
Peace,
Scott
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss