- From: Erik Wilde <dret@berkeley.edu>
- Date: Tue, 04 Jun 2013 22:21:52 -0700
- To: public-ldp@w3.org
- CC: Wes Turner <wes.turner@gmail.com>
hello wes. On 2013-06-04 01:24 , Wes Turner wrote: > https://github.com/madrobby/downtime is a "Standardized JSON API to > indicate downtime for apps and services". it seems to take the concept of "standardized" rather lightly. > Possible Use Case: Through which URLs could/would/should downtime JSON > integrate with Problem JSON? in the current model, it might simply become a problemType URI, and if people actually think the model is useful, they can reuse it (and using that URI would become a pattern shared across various services that want to communicate downtime information in their problem reports). the current problem draft has no registry, so there are no "standardized types" other than the HTTP status codes, but if a URI becomes widely used across services, it would become a de-facto standard. http://tools.ietf.org/html/draft-nottingham-http-problem-04#section-4 cheers, dret.
Received on Wednesday, 5 June 2013 05:22:18 UTC