[Ocs] Proposal for new field in CONTENT module

[Dan Leinir Turthra Jensen]

On Friday 17 August 2012 12:57:58 Laszlo Papp wrote:
> >   That would make sense for one direction, however we need the information
> > in both directions.
> 
> You would need a separate entry for the other direction with the
> "requires-way" as well which is also a similar situation to that you have
> described below. I do not personally call this an issue.

  Right, so now we have arrived at the discussion of what it should look like
technically. Proposal time. The examples in the proposal below contain a bi-
directional dependency, to show how this would look, taking into account the
feedback from Laszlo.

(note: the lists beginning at 1 being established by precedent in the spec,
also discussed as needed fixing in 2.0)

--------------------------------------
Addition to content/add, content/edit:

* POST Arguments: requiresX - X is any number from 1 and upwards, and when set it must be set to the ID of another content item.

--------------------------------------
Addition to content/get:

Example amended as follows:

   <downloadrepository2>repo</downloadrepository2>
   <requires1>12</requires1>
   <requiredby1>1420</requiredby1>
  </content>

--------------------------------------
Addition to content/list:

* URL Arguments: requires - The ID of a content item which the returned items should require

Example amended as follows:
    <detailpage>http://www.KDE-Look.org/content/show.php?content=100</detailpage>
    <requires1>100</requires1>
  </content>


-- 
..Dan // Leinir..
http://leinir.dk/

                          Co-
                            existence
                          or no
                            existence

                          - Piet Hein