proxies --> proxy

[azaroth42]

Tested in the playground and seems to work

[stain]

Thanks! Could you also fix the below..?

In context.json, a copy and paste error means there was no proxyIn statements in the playground.

    "proxyIn" : {
      "@id" : "http://www.openarchives.org/ore/terms/proxyFor", 

Could you also keep the old "proxies" and "ore:proxies" in (just) the contexts for backwards compatibility?

The new document version number should be 0.10 (or 1.0) as "proxy" is a new feature.

Remove "@container": "@set" for "proxy" in the contexts, as you don't want proxy to be generally framed as a list (we say "SHOULD be a JSON object")

"The resource referenced by proxyIn MUST be the Aggregation that the ResourceMap describes. " - this sentence is incompatible with the later talk about aggregating (someone elses's) proxy - could you modify the text to either SHOULD; or (more complicated to formulate, but more correct) to say that under "proxy", the "proxyFor" MUST blablaaola. I think this is now an important point to stress - this SHOULD match the @id of the JSON-wise owning Aggregation.

"An aggregation SHOULD NOT aggregate its own proxies" --> "An Aggregation .."