> > This would aid in tracking individual histories: > > <history> > > [...] > > We have this information in the CVS, and there no use littering the XML > with it... Is there?
Agreed. A lot of histories won't be maintained accurately if the burden is on the search writer. Let CVS tell us the history. I tend not to trust developer-maintained history records anyway -- I would always go to CVS. There is a way to have CVS automatically incorporate the history into its files by using keywords ($Log$, $Revision$, etc.) I've used both the full $Log$ and $Revision$ and we always end up getting rid of $Log$ in favor of $Revision$, because it takes up too much space with info readily available in CVS. > > These would be useful to developers playing with the view-port or > > wanting to use graphics later on: > > <icon /> > > <logo /> > > Yup, as long as they're optional +1 > > A link for more information (unlike <link /> which, IMO, should point > > to something approximating a web-based interface for the resource > > itself): > > <about /> > > What extra information would this provide, that <description/> and > <link/> doesn't? > To me, it seems redundant. +1 for redundant. > > If a generator is used (like the DQSD Search Wizard, a > > search-builder-search, or a webpage (I'm working on one)): > > <generator /> > > This might be interesting. It's "cleaner" than the existing > <created_by/>, so I propose we replace <created_by/> with <generator />. > Of course, the DQSD wizard would have to be updated, but I can do that > if we reach consensus. > There's no logic based on <created_by/>, is there? Nope. <generator /> sounds more professional anyway ;) Glenn ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
