Shouldn't http://registry.webpipes.org/blocks.json include URLs to each respective block?

[elimisteve]

Reading about what each block does, its name, and its inputs and outputs is interesting... but not particularly useful if I don't know each block's URL that I can send the requisite inputs to.

Is this deliberate? Should each block definition/description (probably incorrect terminology) include a url field, as below?

  {
    "name": "Send Email",
    "description": "WebPipe block for sending emails.",
    "url": "http://registry.webpipes.org/blocks/send-email.json",
    "inputs": [
        ...
    ]
  }

[elimisteve]

Nevermind (kinda); looks like this was already added to the spec, but above description instead of just below: https://github.com/webpipes/spec/blob/master/SPEC.markdown#block-definition-format

Has the registry just not been updated to correspond to v0.2?

[matthewhudson]

@elimisteve There was some back-and-forth about the virtue of including URLs in Block Definitions. We initially considered URLs to be a registry problem. IMHO, it makes most sense to simply include the URL in the Block Definition.

I'll update registry.webpipes.org accordingly.