| Lucas_Werkmeister_WMDE added a comment. Herald added a subscriber: PokestarFan. |
This will definitely require a breaking change to the API output format, but I’m not sure what the new output will look like. We need some way to address a snak, regardless of where it appears:
- as the main snak of a statement (currently: entity ID / property ID / statement ID; suggested: that plus "mainsnak")
- as a qualifier of a statement (suggested: entity ID / property ID / statement ID / "qualifiers" / property ID / hash)
- as part of a reference of a statement (suggested: entity ID / property ID / statement ID / "references" / hash / property ID / index)
The reference snaks are the weirdest part, because apparently they don’t even have hashes – only the full reference (which can contain several snaks) has a hash.
The schema suggested above is similar to the JSON format, but mainly differs from it in that it uses the statement ID or snak hash as keys into objects instead of using lists. Is that a good idea, or should we change that and get even closer to the JSON format?
TASK DETAIL
EMAIL PREFERENCES
To: Lucas_Werkmeister_WMDE
Cc: PokestarFan, Lydia_Pintscher, Lucas_Werkmeister_WMDE, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331
Cc: PokestarFan, Lydia_Pintscher, Lucas_Werkmeister_WMDE, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
