Huh... if nobody tells me when I write "RDF" instead of "RFC", I'll start to think that nobody reads my mails ;)
Sorry about that...
Am 13.04.2017 um 20:57 schrieb Daniel Kinzler:
This is a final call for comments on https://phabricator.wikimedia.org/T161527, "Canonical data URLs for machine readable page content".
This RFC was discussed in a public RFC meeting on the wikimedia-office channel on April 12. It was agreed that the RDF be put on Final Call: if no new pertinent concerns are raised by April 26th, the RFC will be approved for implementation. Meeting log: https://tools.wmflabs.org/meetbot/wikimedia-office/2017/wikimedia-office.2017-04-12-21.07.html
The RFC has been discussed before, and proöposed for final call, but some new concerns where indeed raised, which were then addressed in the above discussion. Log of the original meeting: https://tools.wmflabs.org/meetbot/wikimedia-office/2017/wikimedia-office.2017-03-29-21.01.log.html
The RDF proposes:
- Use URLs of the form
https://commons.wikimedia.org/data/main/Data:Avignon_City_Wall.map to identify and retrieve machine readable page content. "main" refers to the main slot, see T107595.
The /data/<slot> path is rewritten to a special page, Special:PageData
Special Special:PageData will redirect (with status 303) to an appropriate
(and typically cacheable) URL for retrieving the page data. For now, this will use the action=raw interface.
- Special:PageData may apply content negotiation based on the Accept header sent
by the client. In the first iteration, it will only check if any accept header sent by the client is compatible with the content model of the requested page.
- The 303 redirects are not cecheable for now, because they depend on the Accept
header; complex normalization would be needed to allow the cache to vary on the Accept header without causing massive cache fragementation.
Please see the phabricator ticket for a summary of the concerns raised and addressed.