Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think this bit is particularly relevant,

> Any effort spent describing what methods to use on what URIs of interest should be entirely defined within the scope of the processing rules for a media type (and, in most cases, already defined by existing media types).

What are the "processing rules" for JSON? Do they depend on the application? Do we have a standard?

My first thought is something like this,

    { "resources":
      { "foo":
        { href:   'http://example.com/foo',
          method: 'get'
        },
        "bar":
        { href:   'http://example.com/bar',
          method: 'post'
        },
        "baz":
        { href:   'http://example.com/baz',
          method: 'put'
        },
      }
    }


Yes, to be useful for REST json really needs either a type for hyperlinks or a naming convention. Arguably then it is an extension of json and needs a new mime type...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: