On 2003-04-30, Nicola Ken Barozzi wrote:
> No comments?
> Nicola Ken Barozzi wrote:
> > Again I want to tackle the status.xml file thing.
> > So in the end, I would propose that we don't pursue a single status.xml
> > anymore, but make them into:
> > authors.xml (as but with added homepage links)
> > changes.xml (without authors section)
> > todo.xml (without authors section)
> > compat.xml (compatibility-breaks)
> > issues.xml (the issue-vote part, remove it ATM because DOA)
> > news.xml (the project headline news)
> > that will reside or in the main dir or in a 'project' or 'status' dir (I
> > vote for 'status' dir).
> > Also, we replace the status.xml file with a STATUS.TXT file that is all
> > text-based, ans that refers to the above xml descriptors for the
> > structured data, keeping only unstructured extra info about the project.
Your ideas sound fine to me.
> > --- news ---
> > Then we have to make a news.xml file.
> > I look at all the RSS feeds, but I don't like them to be source formats.
> > I could propose this news DTD, loosly based on RSS 0.91:
> > shbat fix
> > Any suggestions?
A "date" attribute on
- . Perhaps a "timespan" attribute on
How would we deal archives of news? I mean we do not want just
one big news.xml forever growing. Perhaps a directory approach
... news/ with say separate monthly news files. A directory generator
could build a table of contents.