In the WBManifest prototype, we grouped items and properties together under equivEntities. This was pointed out by one tool builder as potentially confusing. We should determine whether it makes more sense to group them together or split them up.
Things we considered
- Extensibility to other entity types (besides items/properties): MediaInfo, Lexemes, and potentially EntitySchemas in the future
- How precisely would it help tool builders to have them split? Human consumption or machine readability?
Things discussed, but not relevant
- For sysadmins, slightly easier to check the manually entered equivalent entities if they are split apart into Ps and Qs (i.e. only PIDs are linked to other PIDs, so no properties are being mapped to an item on Wikidata)
- Splitting them apart also allows for validation of the input (the entity ID fits the expected pattern) to automatically reject incorrect input
Decision to Document
Include in the ADR for the final manifest format an explanation around why we decided to split or not split apart entity types.