"All we need to do" is to decide on an xml tag that identifies the reporting schedule and have podlings put it into the document. Then write an xslt transform that extracts the schedule information from each <project>.xml file.
For example, <section id="Reporting"> <title>Reporting Schedule</title> <p>some information here about the reporting schedule</p> </section>I don't know quite enough about how to specify or transform the schedule data, but at least we can put it somewhere that already exists and is maintained.
Craig On Jun 20, 2007, at 10:07 AM, robert burrell donkin wrote:
On 6/19/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:On 6/19/07, Justin Erenkrantz <[EMAIL PROTECTED]> wrote: > On 6/19/07, robert burrell donkin <[EMAIL PROTECTED] > wrote: > > 1. should the information be public? Yes. > > 2. should the information be machine readable? > Not at the expense of making it hard for humans to maintain it. If > you can't make sense of the format in 10 seconds or less, then it's > unlikely to get much attention. -- justinthey don't get much attention now even though they are in loosely structuredformats :-/ +1 (though not saying rdf is incomprehensible, haven't looked at itmuch yet, thought the premise warrants support on its own :-)cost of maintenance is a more complex issue than just formatthis information needs to be available in several different formats for different purposes. free text is the easiest format to understand but is not necessarily the easiest to maintain. if the price of unstructured text is maintaining multiple documents then this may be most costly than using astructured format. - robert
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
