Skip to content

Current priority: reduce the number of unknown properties #194

@ScriptRaccoon

Description

@ScriptRaccoon

This issue is partially a duplicate of other issues (or more like a parent), but I want to make it more visible that this should have a priority right now (when it comes to additions to the data). Do not add new properties and do not add new categories before we have decided most (or at least some) of the unknown properties of the categories which look doable. Exceptions: new properties that help to decide the given ones and where all categories will be decided directly (those that create no new unknowns).

In particular, decide all properties of (at least):

category done
CMon
FinOrd
FinGrp
B
FS
Rel
Set_f
Cat
Man
BG_f
walking_fork
walking_pair
walking_span
BG_c

The following are currently open:

All these look doable. A PR can tackle one property or one category at a time.

Related:

PRs working on this issue:

Development of the number of unknown (category, property)-pairs:

151 --> 145 --> 139 --> 136 --> 133 --> 125 --> 118 --> 116 --> 115 (--> 117) --> 116 --> 114 --> 108 ---> 97

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions