There is some early dump of documenting and standardising the tags at https://github.com/Quaddicted/quaddicted-data/wiki/Tags
The tags are meant to hold all information about a package that is not 100% technical, immutable and undebatable.
Random example:
"tags": [
"author=zbidou72",
"commandline=-game alk1.1",
"current_main_group_package=yes",
"dependency=alkaline1.1",
"depends=('alkaline>=1.10')",
"exceeds_quake_limits=yes",
"filename=nullbear2v12.zip",
"game=quake",
"game_mode=singleplayer",
"link=[Func_Msgboard thread](https://celephais.net/board/view_thread.php?id=62203)",
"link=[Slipseer page](https://www.slipseer.com/index.php?resources/null-bearing-redux.117/)",
"map_size=large",
"nonspecific_tag=alkaline",
"nonspecific_tag=explore",
"nonspecific_tag=makkon",
"nonspecific_tag=mg1",
"nonspecific_tag=ship",
"nonspecific_tag=warehouse",
"provides='nullbear2=1.2'",
"release_date=2022-09-30",
"release_group=nullbear2",
"source=included",
"startmap=nullbear2",
"theme=base",
"theme=industrial",
"theme=water",
"title=Null Bearing Redux v1.2",
"type=map",
"version=1.2",
"zipbasedir=alk1.1/"
],
The documentation will never be finished and is open for discusssion, so your input and collaboration would be highly appreciated.
Especially the handling of dependencies and “release groups” (other versions of a thing) is probably not perfect and could use your expertise.
You can form the database and website future this way! Want to catalog information about the number of monsters per map on hard mode? Invent a good tagging schema and add it. Want to document actual specific limits a map or mod requires? Invent a good tagging schema and add it.