Addshore added a comment.
> Also, why should /statements get to have a shortcut but /items and
/properties don't?
For the decision to have a statements endpoint at the top level I'd defer to
the decision doc which currently says:
------
Entities + Statements
---------------------
**Decision: Statements would be exposed both within an entity and also at the
top level**
Considered options:
- For the statements with a GUID:
- Should we address those always through entities?
- longer path
- the entity id is already in the path and the prefix is redundant
- Or individually, through a /statements path?
Usefulness (end users) Vs. cost of ownership (devs)
Notes
-----
The current Action API allows you to get a statement with only the GUID
(without the entity id prefix) with no extra work
Not having a top level statement endpoint would mean that “extra work” would
be needed by the client in order to access a statement (splitting the statement
ID)
Taking this into account we can cover all of our existing APIs with REST APIs
only if we do have statements as a top level api module.
TASK DETAIL
https://phabricator.wikimedia.org/T264555
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Addshore
Cc: Lydia_Pintscher, Addshore, Pablo-WMDE, WMDE-leszek, Silvan_WMDE, Aklapper,
Akuckartz, darthmon_wmde, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden,
LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
