ISSUE-60: The specification does not allow GETting empty containers
GETting empty containers
The specification does not allow GETting empty containers
- State:
- CLOSED
- Product:
- Linked Data Platform Spec
- Raised by:
- Raúl García Castro
- Opened on:
- 2013-03-22
- Description:
- The text in 5.3.1 does not allow getting an empty container since it says that a container representation MUST contain membership triples.
[[
5.3.1 The representation of a LDPC MUST contain a set of triples with a consistent subject and predicate whose objects indicate members of the container. The subject of the triples MAY be the container itself or MAY be another resource (as in the example). See also 5.2.3.
]]
I propose rewriting the text as follows in order to allow getting empty containers. I also propose replacing "consistent subject" by "single subject", to make the sentence easier to interpret.
[[
5.3.1 In the case of non-empty containers, the representation of a LDPC MUST contain a set of triples with a single subject and predicate whose objects indicate members of the container. The subject of the triples MAY be the container itself or MAY be another resource (as in the example). See also 5.2.3.
]]
- Related Actions Items:
- No related actions
- Related emails:
- Re: ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [Linked Data Platform core] (from richard@cyganiak.de on 2013-03-22)
- ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [Linked Data Platform core] (from sysbot+tracker@w3.org on 2013-03-22)
Related notes:
Resolution: Close Issue-60; with recommendation to editor to fix the spec to clarify intent (empty containers are allowed)
See http://www.w3.org/2012/ldp/meeting/2013-03-25#resolution_5
Display change log