Andy Mabbett wrote:
Now, would someone with IE7 kindly check out the "opensearch.xml" file
referenced from:
http://www.westmidlandbirdclub.com/new.htm
IE stuff:
IE7 doesn't support OpenSearch (usefully). M$'s current paranoia has
broken it - you aren't permitted to access this terrible security hole
unless you mark the site as trusted.
Using OpenSearch for the first time with a site is too long-winded to
be useful. You have to add the sie provider, then submit the search. No
one-click searching, which is ridiculous.
You don't even see that a site supports OpenSearch unless you know
where to look.
IE doesn't see any connection between OpenSearch and the current page.
You have to pick a search provider from a list, you aren't
automatically defaulted to one because you're already on the relevant
page.
Site stuff:
Your shortname of "WMBC" is possibly too short to be meaningful in a
list of providers. Remember that IE is enforcing a two-step "register,
then search" approach here, so anyone who uses OpenSearch even casually
is likely to collect a long list of search providers.
The results are in HTML, not anything aggregateable. This kills most of
the interesting uses of OpenSearch.
Your <tagsshould probably include "birdwatching" and as many related
terms you can squeeze in there.
General stuff.
OpenSearch isn't about replacing a site's search box. Certainly not in
the short term, as usability-wise it's substantially les usable than
that.
What OpenSearch is really for is for syndicating searches across
multiple related search providers, typically per-site searches for
related sites. To make this work we need <tags(sic) in the search
metadata to indicate "related" search providers, and we need search
results to be returned in a format that's not just easily parseable,
but that is _identically_ parseable (i.e. a standard format like Atom)
without needing to write site-specific parsers.
OpenSearch isn't well designed (IMHO). In particular the <tagselement
is almost unusable. This really did need extensible scope for _much_
smarter annotation, particularly structured annotation and the ability
to use shared vocabularies (e.g. TGN for your geographical location).
As it is, the OpenSearch "trivial lost of keywords" is barely useful
here, and we've lost the possibility of auto-aggregation by
auto-discovery of relevant search providers.
I've spent most of the last decade faffing about with metadata - to
have Amazon produce a protocol so trivial and restricted this late in
the game was a little galling. We _know_ how to do it better, and we
even know how to do it in a simplicity-compatible manner. Shame they
didn't pay attention.