<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 09 Aug 2007, at 1:58 PM, Dries Buytaert wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Is there a reason why we can't use PHPdoc for this?<SPAN class="Apple-converted-space"> </SPAN>(I'm not really keen on having to execute random PHP code on api.drupal.org.)</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>I'm not really sure that we'd need to execute it. We only document core on api, and schema.module makes the existing data structure</DIV><DIV>self documenting (as far as I understand).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This same information would be available to all contrib modules, for anybody who installs the schema module, similar to how you can</DIV><DIV>get api documentation by installing the api module.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>It would even theoretically be possible to have the schema module produce an image (which can then be cached) or svg file</DIV><DIV> (which would be trés cool) from the information it has (ie: foreign keys and the like).</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>