Re: [sword-app-tech] Opinion seeking for sword implementation

[Jim D. <oj...@ca...>]

Hi Friederike,

2009/7/23 Stuart Lewis <s....@au...>:
> 1) No advice is given, you are free to implement this how you want. I'm
> not a HTTP guru, but I wonder if there may be problems caused by using
> query parameters (?collection=escidoc:133823) in a POST? Could you use
> URL rewriting (or another similar method) to have URLs such as
> /sword-app/deposit/collection/escidoc:133823 ?

Yes, but encoding the ":" ...

> 2) When a client performs a deposit, they SHOULD be sending an
> X-Packaging header to tell you what the packaging format is. If they
> don't, or if it contains an unacceptable value, you MUST return a 415
> Unsupported Media Type, SHOULD return a SWORD error document with the
> Error URI of http://purl.org/net/sword/error/ErrorContent

I'd imagine you'd have a packaging type for each metadata type here
(zip+bib, zip+xmlschema etc). This should be a URI. The original
intention was to have a second document that enumerated the types, but
that probably wouldn't be sufficiently dynamic - a registry is a
better solution. In the meantime, please propose a scheme of URIs
you'd like to use and describe what the packaging / manifest
arrangement is in each case. With some discussion we should be able to
form a consensus if other people are doing similar things.

Best regards,
jim