Issue/Requirements for being a server

Currently required (by Alan's demo):

Needs to run apache and PURLZ 1.4
- to explore federation, I'm trying out Release 1.6.3 Dan Connolly 16:59, 26 April 2010 (UTC)
[In Apache] Need mod_proxy, mod_proxy_http
Need to run mysql [because purlz needs it?]
Fixed IP address

We want to enumerate these.

Federation Architecture Review

The 3rd goal from the 5 March architecture PURL service operators will remain in control of their DNS registrations and operation. was dropped and replaced by the authorities will be "outsourced" to a dynamic DNS service that will resolve to proxies for all authorities of the PURLs in the federation.
- this conflicts with requirements from the resolution within an enterprise use case.
"Caching proxies are inserted between the client and federation members."
- hmm... who runs the proxies? i.e. who bears the setup and operational burden?
For example a partial PURL can be defined for the pattern "http://*.purl.sn.org/*" and use the regex http://(.*).purl.sn.org/([^/]*)/(.*) with the template http://$1.sn.org/$2/pages/$3.html to map http://term.purl.sn.org/dom/item to http://term.sn.org/dom/pages/item.html
- close to "On the other matter of suffixes dispatch, we are assured that that can happen." but Partial PURLs can also match path fragments ending with a '/'. doesn't seem to work for the case of Dispatch off suffix http://uniprot.sharedname.org/P01221 and http://uniprot.sharedname.org/P01221.xml have different targets.

what other requirements/desiderata did we discuss in the 5 March meeting? it's a little hard to tell from the notes.

Editorial:

... not a design criterion seems odd; did you mean "not a design requirement"?
attached diagram? I can't find it. oh... I see it now. Why not link to it at 1st mention too?
why the in-your-face URLs? e.g. for wikipedia on SRV records