<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Right, so now we have arrived at the discussion of what it should look like technically.</blockquote><div> I meant that by "this", I have not seen the concern brought up about the ACL as an issue. I still stick by that, the current proposal is: * It is inconsistent with the rest. * It may be slower at times than getting all the dependencies in the same bunch (although it is true vice versa). * foobarX is an anti-pattern in OCS v1 in my opinion, and we should avoid using that unless it is really necessary. Unfortunately, that would leverage the argument for the posting as you have written. * this will require a slightly different management for the libraries (for instance attica) to introduce a separate logic for that. This should not lead the specification creation for sure, but considering our manpower, it is an additional factor either way. I have not mentioned that, but getting all the "required" and "requires by" data could also be done through queries. I believe, that would be the real purpose of the aforementioned dependencies, but what about adding queries (as well?) to get the "requires" and "required by" contents? My issue is that with your approach in certain cases, I would need to make a lot of queries to get all the necessary content data I am interested in. Having explicite queries and also embedded pointers would be a compromise (I can help with that, and work out in addition to this proposal, if accepted). Laszlo </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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><a href="http://www.KDE-Look.org/content/show.php?content=100" target="_blank">http://www.KDE-Look.org/content/show.php?content=100</a></detailpage> <requires1>100</requires1> </content> <div class="HOEnZb"><div class="h5"> -- ..Dan // Leinir.. <a href="http://leinir.dk/" target="_blank">http://leinir.dk/</a> Co- existence or no existence - Piet Hein </div></div></blockquote></div>