Resource both Data and Container

[gibsonf1]

lws-protocol/lws10-core/container-representation.md

Line 26 in d8a4de3

- **`mediaType`**: The media type of the resource (e.g., `"text/plain"`, `"image/jpeg"`). MUST be present for DataResources.

How is the situation handled when a resource is both a Data resource and a Container?

[pchampin]

Repeating what I wrote in #126 (comment)

The spec currently states: "Resources in LWS are classified as either: Container [...] Data Resource" (emphasis is mine). So the situation you describe is not supposed to happen.

[elf-pavlik]

Again, this issue and #126 look like duplicates, plus there already are multiple existing issue about this topic.

[gibsonf1]

Repeating what I wrote in #126 (comment)

The spec currently states: "Resources in LWS are classified as either: Container [...] Data Resource" (emphasis is mine). So the situation you describe is not supposed to happen.

The spec needs to be corrected to not say either, this is my point as that would make no sense since a Container is a species of a data resource since they both are data resources. And a Container will have all the same kind of data about it as any data resource such as a file or person, etc, like labels, names, icon, comments, types, etc etc. So when a GET request is made on a Container, the return should include identical return to any data resource (given the accept) so app can populate that container approriately as it does with all data resources, as well as the container specifics per LWS spec to show the contents inside it- that is both should be had in one request.

[renyuneyun]

I remember there was a discussion in a LWS meeting on whether a Container can have "data" associated with it, just like a regular Resource. Unfortunately I can't find it now.

For my stance: I think it's useful to support Container to also have data, just like regular Resources; however, there does not appear to be a clean to support that -- especially if some fields conflict with each other (i.e. the Resource content has the same predicates as the Container's defined fields). Maybe content negotiation is a way out, but I'm not sure.