<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Brian,<div><br><div><div><div>On Sep 12, 2014, at 12:59 PM, Brian Major wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On Thu, Sep 11, 2014 at 10:39 AM, Matthew Graham<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:mjg@cacr.caltech.edu" target="_blank">mjg@cacr.caltech.edu</a>></span><span class="Apple-converted-space"> </span>wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">Hi,<br><br>Mike Fitzpatrick and I were reviewing the VOSpace spec last week specifically for capability stuff and realized that there are a couple of elements missing that we would like to see included in VOSpace 2.1:<br><br>(1) At the moment you get all-or-none with the capabilities on a node whereas there should be a way to specify which capabilities you would like on a node so we would like to propose two additional methods to work a specific node: attachCapability and detachCapability.<br></blockquote><div><br></div><div>I'm probably not correctly understanding these proposed methods: are you suggesting that clients should have the ability to modify the capabilities of a node? Couldn't the desired capabilities be set by creating a new node? I think it would be tricky to accept capability modification actions when there is potentially data already associated with the node...</div><div> </div></span></blockquote><br></div></div></div><div>The spec specifically says that you cannot use node creation to set the capabilities on a given node so there is actually no way to do this. You either get all the capabilities that a server offers on all nodes or none - the user has no control over this.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Cheers,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Matthew</div></body></html>