where's namespace spec?

[Chuck Kollars]

The doc (and everyplace else on the web) says

The XML Namespaces URI for the XML data formats described in this
specification is:

http://a9.com/-/spec/opensearch/1.1/

But when I try to visit there with my browser, all I get is 404. (Even just
http://a9.com/- returns "not found".)

[DeWitt Clinton]

Technically the namespace is just an arbitrary (if rather evocative)
string, but I agree it would be nice if it referred people to somewhere
useful.

I believe that URL used to serve a page with a link to the opensearch docs,
but the a9.com servers have gone through several iterations since then, so
I'm not entirely surprised it 404's.

If anyone reading this group still has the ability to make changes to a9.com,
it might be nice to put something up that points to opensearch.org.

-DeWitt

Post by Chuck Kollars
The doc (and everyplace else on the web) says
The XML Namespaces URI for the XML data formats described in this
http://a9.com/-/spec/opensearch/1.1/
But when I try to visit there with my browser, all I get is 404. (Even
just http://a9.com/- returns "not found".)
--
You received this message because you are subscribed to the Google Groups
"OpenSearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/opensearch.
For more options, visit https://groups.google.com/groups/opt_out.

[Ed Summers]

Is it worth considering changing the namespace to something else? Perhaps
it could be anchored at opensearch.org?

[DeWitt Clinton]

I'm not sure. It makes some sense, but it's effectively a full version
bump, forking the spec away from any existing clients. Which is maybe
overdue, but still it's pretty high cost for marginal benefit. If we ever
did a "2.0" or a proper IETF RFC, then definitely we'd want to fix it.

Also, the domain name and DNS for both opensearch.org and a9.com are owned
and run by Amazon, so it's effectively the same thing. Worse actually, as
opensearch.org points to a MediaWiki instance that I still personally
maintain (in terms of paying for it, I spend very little time actually
working on it), and still hope to transition off of someday in favor of a
purely static site that cheaper and easier to host.

So, I suppose I think keeping the existing namespace problem is better, and
certainly easier on me, than coming up with a new set of ones. : )

-DeWitt

Post by Ed Summers
Is it worth considering changing the namespace to something else? Perhaps
it could be anchored at opensearch.org?
--
You received this message because you are subscribed to the Google Groups
"OpenSearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/opensearch.
For more options, visit https://groups.google.com/groups/opt_out.