- Number of implementation reports
- 16
- ✔
- Passed
- ✗
- Failed
- ?
- Cannot tell
- ⌙
- Inapplicable
- ○
- Untested
- PR
- Accepts
POST requests. [source] - PC
- Responds to
POST requests with Content-Type: application/ld+json with status code 201 Created or 202 Accepted . [source] - PL
- Returns a
Location header in response to successful POST requests. [source] - PLP
- Succeeds when the content type includes a
profile parameter. [source] - GR
- Returns JSON-LD on
GET requests. [source] - GLC
- Lists notification URIs with
ldp:contains . [source] - GNJL
- Notifications are available as JSON-LD. [source]
- GNRS
- When requested with no
Accept header or */* , notifications are still returned as RDF. [source] - OR
- Accepts
OPTIONS requests. [source] - OAP
- Advertises acceptable content types with
Accept-Post in response to OPTIONS request. [source] - OAPCJL
Accept-Post includes application/ld+json . [source]- PRCU
- Fails to process notifications if implementation-specific constraints are not met. [source]
- GNL
- Restricts list of notification URIs (eg. according to access control). [source]
- GLCR
- Inbox has type
ldp:Container . [source] - GLCB
- Advertises constraints with
ldp:constrainedBy . [source]
|