# Tags as metadata for releases

**URL:** <https://discuss.quaddicted.com/t/tags-as-metadata-for-releases/8135>\
**Category:** Quaddicted.com\
**Created:** [August 24, 2025, 12:39pm UTC](https://discuss.quaddicted.com/t/tags-as-metadata-for-releases/8135 "2025-08-24T12:39:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Spirit](https://discuss.quaddicted.com/user_avatar/discuss.quaddicted.com/spirit/32/6_2.png) [@Spirit](https://discuss.quaddicted.com/u/Spirit)\
**Post date:** [August 24, 2025, 12:39pm UTC](https://discuss.quaddicted.com/t/tags-as-metadata-for-releases/8135/1 "2025-08-24T12:39:45Z")

</div>

There is some early dump of documenting and standardising the tags at [https://github.com/Quaddicted/quaddicted-data/wiki/Tags](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:

```json
    "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.

---

<div class="post-metadata">

**Author:** ![Spirit](https://discuss.quaddicted.com/user_avatar/discuss.quaddicted.com/spirit/32/6_2.png) [@Spirit](https://discuss.quaddicted.com/u/Spirit)\
**Post date:** [September 22, 2025, 7:45pm UTC](https://discuss.quaddicted.com/t/tags-as-metadata-for-releases/8135/2 "2025-09-22T19:45:11Z")

</div>

I hacked together some validation code for some tags and added it as a CI action to the [https://github.com/Quaddicted/quaddicted-data](https://github.com/Quaddicted/quaddicted-data) repository so new changes or additions will be scanned by it.

Currently it fails already because while coding I had two assumptions which go against existing tags of some packages:

- [https://github.com/Quaddicted/quaddicted-data/issues/59](https://github.com/Quaddicted/quaddicted-data/issues/59) for allowed characters in `commandline` tags
- [https://github.com/Quaddicted/quaddicted-data/issues/60](https://github.com/Quaddicted/quaddicted-data/issues/60) for allowed characters in `theme` tags

Your input would be highly appreciated!