[Ocs] Proposal for new field in CONTENT module

[Laszlo Papp]

>
> * URL Argument: fullrequires - Defaults to false. Set to true, this will
> cause
> the listing to include full content items for any requiredby and requires
> fields in the items. If the content item required has already been listed
> at a
> higher level in the same returned data, it will not be shown again.--
>

I had the impression you would be against the original idea of mine for
having the whole children and parents contents embedded, but I actually
feel this cooler. I agree with getting back to this way. :-)

This reminds that, children and parents could just well do the tricks by
using the "details" tag for the content elements. There are examples for
full, downloads, fan, details, check, summary, basic, id, balance.

This way, the specification would be more flexible. It would be possible to
use any details type allowed for content, not just "everything or id".
Whether it is called children/parents or requires/requiredby, it is not a
big deal. However, I would encourage the consistency here, so my preference
is childrend/parents. This way, we would also address my aforementioned
issues (i.e. consistency, performance, foobarX, no additional specification
implementation logics).

We could perhaps introduce the "details" tag for the parents/children as
well to avoid the bytes that way for all the entries.

I am now about to put up the examples that I can post just to see how this
would look like. :-)

Laszlo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/ocs/attachments/20120818/4cc6fad1/attachment.html>