Hi Shawn, All of these need to be optional, IMO, I wouldn't want to require too much work from search-builders.
> These are really necessary: > <language /> > <region /> > The last should have predefined suggestions in wizards to make it more > compatible with filtering on values for the enabling/disabling > searches. That's a good one, what should they default to? > 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? > 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 > 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. > 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? > A special note to identify if there are any special accessory > requirements to use a search, such as software, components, > username/password, other: > <requirements /> If we can use this for diagnosing errors run-time, it seems like a good idea. Kim ------------------------------------------------------- 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
