[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Review comments for OLSC Resource Preview 3.0
Example 5: Requesting the Compact Resource
GET /bugs/324/screenshot?compact HTTP/1.1
Host: example.com
Accept: application/json
Does this guarantee a JSON
response?
What other media types MUST
or MAY be supported by the server?
If "application/rdf+xml"
is permitted, how does this differ from the XML response format that says
it should be be processed as RDF/XML?
5.1.3 Discovering Compact Resources Using the HTTP
Prefer Header
Clients can request a Compact resource by making an HTTP
GET request to the target resource's URI using the return=representation
preference of the HTTP Prefer request header [RFC7240]
and include parameter
[LDP]
value http://open-services.net/ns/core#PreferCompact.
Servers supporting resource preview must support this method of discovery
for resources with RDF or JSON representations.
Does Accept=application/json
guarantee a JSON response?
Should "must" be
"MUST"?
What other media types MUST
or MAY be supported by the server?
6.5 Displaying a small preview
6.6 Displaying a large preview
Is there a way that a client
can request small vs large preview?
Or is the expected behaviour
that servers return both small and large preview data in the same response
and the client can choose which to display?
Should a client preserve
the ordering of data in the response (for JSON)?
If so, what about Turtle where ordering may not be preserved?
7.5 Compact Resources
7.5.1 Servers MUST support the application/json
[RFC4627]
and text/turtle
[turtle]
media types for the Compact resource.
Shouldn't this also include
application/x-oslc-compact+xml?
A. Resource Constraints
A.1 Resource: Compact
B. JSON Representation Format
The table in A.1 shows the
RDF predicate prefixed name. However, the JSON format in B seems to use
an unqualified name, and I could not see anything that said the JSON property
names should match them, or reference some other table where they are defined.
Would it be clearer to have the JSON section simply reference the table
in A.1 with some statement about the JSON property name? Currently the
data seems duplicated between the two, with the danger they might get out
of sync with each other.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]