webpipes/spec

Issues

• JSON Schema for the Specification

  #11 opened 12 years ago by matthewhudson
  1

• Renew webpipes.org or change docs to use new domain

  #18 opened 8 years ago by elimisteve
  1

• Define baseline Trigger behavior

  #17 opened 11 years ago by matthewhudson
  0

• Success/Error handling: Status Codes

  #14 opened 12 years ago by matthewhudson
  1

• CLIENTSPEC

  #13 opened 12 years ago by matthewhudson
  1

• No OPTIONS?

  #12 opened 12 years ago by tlrobinson
  1

• Align with JSON-RPC?

  #4 opened 12 years ago by tlrobinson
  19

• What if a block doesn't have any output?

  #7 opened 12 years ago by matthewhudson
  4

• How do * inputs (and outputs?) work?

  #8 opened 12 years ago by tlrobinson
  0

• How to handle error messaging?

  #6 opened 12 years ago by matthewhudson
  1

• Should block definition have a "url" property?

  #5 opened 12 years ago by tlrobinson
  1

• Use JSON Schema in block definitions?

  #2 opened 12 years ago by tlrobinson
  5

• Request/inputs and response/outputs formats

  #3 opened 12 years ago by tlrobinson
  1

• Proposal for POST requests on /block-endpoint

  #1 opened 12 years ago by jpf
  5