-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think it would be most useful to adopt an existing category hierarchy, and if possible either supply or refer to a web page that defines each and gives some examples. One question: how will the syntax for nested/sub-categories look? Will it be:
<category>database/browser</category> or is it even useful to get into such sub-classifications? (personally, I think it is, and the tool could aggregate all general and subcategory matches when viewed directly...) One thing I am a little concerned with is getting this design figured out as soon as is humanly possible, particularly if we intend to provide this for 2.0-final, since -beta-1 will have to be feature-complete, and it none too far away... - -j Jason van Zyl wrote: | Hi, | | I wanted to broach the topic of augmenting the POM to allow a project to | categorize itself for the purposes of creating a meaningful index of | projects like can be found at http://java-source.net/. | | Putting aside for the moment what the actual categories would be would | something like: | | <categories> | <category>database</category> | <category>visualization</category> | <categories> | | Where a project could specify any number of categories. | | Or should we attempt to create/borrow an existing category hierarchy and | try to use that? This is something that I think would be good for 2.0 | final as creating an index of contained within a repository I think | would be highly useful. | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFC1pmCK3h2CZwO/4URAnE0AJ0YvDwsxCa5fW/2M4v5rjEV+LAqsACfWs9J +ym/sIJ+uJMYQmBpfKTwgHc= =o1fc -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
