Hi Glen, > I've noticed a couple of things. I'm afraid I'm also new to the list so > apologies if you've already discussed them. > > 3. Terminology > > EM-URI 'The Atom Edit Media URI' > Edit-URI 'The Atom Media Edit URI' > > I'm afraid the first sentences for the two definitions got me confused > for a while. Maybe edit-url could be defined as Atom Metadata Edit URI > or something to differentiate them.
Ah yes, good point - my mistake; I've clarified this in my copy of the doc, which will make its way online soon. > I think I might be asking the same question as Alistair for the > following two: > 6.6.2. Adding New Metadata to a Resource > > Is this replacing the metadata (atom-entry document) or adding to it? If > replacing should it be a PUT operation? Actually, this is unclear, thanks for picking that up. I'll have a look at it again, and perhaps define PUT and POST or defer to one or the other. I'll have to go and have a bit of a read of what the Atom spec says about this before putting anything down. > 6.6.3. Adding New Metadata and Packages or Files to a Resource with > Multipart > > Same question here, is this replacing the metadata or adding to it? > Should the section title be Updating Metadata and adding packages or > files to a resource with multipart? ok, will cover both this and the above. > 9.1 & 9.2. Suppress Metadata Updates > > I'm afraid I've missed this discussion about this but isn't the decision > on what to do with the metadata the responsibility of the server > implementation? What would be the use case for the client saying not to > use the metadata on a new deposit and if the server had no other data to > work with can they ignore the request? I don't think there's any presumption that the client can tell the server what to do (or maybe this should be more clearly articulated). Just like In-Progress, this is a hint to the server as to what the purpose of the deposit is, and what the client might be about to do. For example, imagine issuing Suppress-Metadata when uploading a spreadsheet of data to an item for which it is supporting information, not the primary file (which might be the research paper for which the spreadsheet is supporting data). In this case, you would not want the server to attempt to extract metadata from the spreadsheet and overwrite existing metadata in the item (it might replace the title, for example). You declare Suppress-Metadata to hint to the server that it should just take the file and not do any more with it. This might turn out to be unnecessarily complex in implementation - what do you think? Dave T - you were the origin of this particular idea, can you expand on it a little more? Cheers, Richard ------------------------------------------------------------------------------ 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
