Hi Ian, I think that a large part of what SWORD adds to AtomPub is how you talk about packaging. We're definitely not going to go down the route of specifying package formats or support levels outside of AtomPub's basic definitions. What I'd be particularly interested to know is whether you think that SWORD currently provides you with enough tools to talk /about/ packaging?
We have, for example, had a couple of mentions of the desire to ONLY use mime-types, which we know is insufficient for describing packages - what is the mime type of a DSpace METS package? And I have also verified that the registration process for mime-types is not strictly trivial. Do the extra features for providing Package information during deposit, Accept-Package headers for retrieval, and sword:packaging elements in the service documents and atom entries provide you with a framework which will work for your requirements? Cheers, Richard On 18/02/11 14:28, Ian Stuart wrote: > On 18/02/11 12:52, David Tarrant wrote: >> >> On 18 Feb 2011, at 12:49, Ian Stuart wrote: >> >>> SWORD is a transport mechanism... we all understand that - but sword can >>> either be a bling truck >>> (http://farm1.static.flickr.com/120/307424194_ccb7df1246.jpg) or a >>> container >>> (http://www.shipping-container-modification.com/images/standard_large.jpg) >> >> and both are really expensive!!! > The Shipping container is an un-patented design.... open access, if you > like ;-) > >> I think that, if you want to upload a package, don't expect to be able >> to edit parts of the package. >> >> I feel if you want to edit using packages, then you delete the previous >> version and upload a whole new package. >> Supporting more features than that is going to be very hard in the >> packaging scenario. > The question still comes down to.... at some point, the client and the > server need to exchange "metadata" and "files" - how is this negotiated > and how is the data transferred? > > Even in your video, you are transferring a small set of metadata items > from client to server. In your example, you control both ends of the > link, so you know the fields to transfer. What happens when the objects > get more complex, and you don't control both ends? > > Copying binary files is (relatively) easy.... copying sets of metadata > from one system to another requires "packaging" > > "Packaging" is the area I'm interested in. > > ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Sword-app-techadvisorypanel mailing list Sword-app-techadvisorypanel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sword-app-techadvisorypanel
