HTTP Example:POST /{BASE}/resource?uri=…
| API Example: ResourceWebService.postNewOrRemote({'uri': }); |
Creates new resource with given uri. If no uri is defined it creates a
local uri with random uuid - Output:
- javax.ws.rs.core.Response - HTTP response (body is a String message)
- Query parameters:
- uri - , the fully-qualified URI of the resource to create in the
triple store
- HTTP return codes:
- 201 - new resource created
- 302 - resource already exists
- 500 - Internal Error
- HTTP response headers:
- Location - the url of the new/found resource
|
HTTP Example:GET /{BASE}/resource?genid=…&format=…&uri=…
Accept: …
| API Example: ResourceWebService.getRemote({'genid': , 'format': , 'uri': , 'Accept': }); |
Returns a link to a remote resource (data or content) with the given uri
and an accepted return type - Output:
- javax.ws.rs.core.Response
- Query parameters:
- genid
- format - forces representation format (optional, normal content negotiation performed if empty)
- uri - the fully-qualified URI of the resource to create in the triple store
- Header parameters:
- Accept
- HTTP return codes:
- 303 - resource can be found in the requested format under Location
- 400 - bad request (maybe uri is not defined)
- 404 - resource cannot be found
- 406 - resource cannot be found in the given format
- 500 - Internal Error
- HTTP response headers:
- Location - the url of the resource in the requested format
- Content-Type - (for HTTP 406) a list of available types
(content and meta)
- HTTP request headers:
- Accept - accepted mimetypes; value must follow the pattern
(.+/.+(;rel=(content|meta))?,)+
|
HTTP Example:PUT /{BASE}/resource?uri=…
Content-Type: …
| API Example: ResourceWebService.putRemote({'uri': , 'Content-Type': }); |
Returns a Link where the given data (metadata or content) can be put to
the remote resource - Output:
- javax.ws.rs.core.Response - a link where the data can be put (depends on Content-Type)
- Query parameters:
- uri - , the fully-qualified URI of the resource to create in the
triple store
- Header parameters:
- Content-Type
- HTTP return codes:
- 303 - resource in given format can be put under Location
- 400 - bad request (e.g. uri is null)
- 404 - resource cannot be found
- 415 - Content-Type is not supported
- 500 - Internal Error
- HTTP response headers:
- Location - (for HTTP 303) the url where data can be put
- HTTP request headers:
- Content-Type - type of the body; value must follow the
pattern .+/.+(;rel=(content|meta))?
|
HTTP Example:DELETE /{BASE}/resource?uri=…
| API Example: ResourceWebService.deleteResourceRemote({'uri': }); |
Delete remote resource with given uri - Output:
- javax.ws.rs.core.Response - HTTP response (success or error)
- Query parameters:
- uri - , the fully-qualified URI of the resource to create in the
triple store
- HTTP return codes:
- 200 - resource deleted
- 400 - bad request (e.g, uri is null)
- 404 - resource not found
|