| daniel edited the task description. (Show Details) |
EDIT DETAILS
* 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="" style="padding: 0 2px; color: #333333; background: rgba(251, 175, 175, .7);">``` interface.
* Apply conten* "URLs don't negotiation to the established page URLs using the ```/wiki/``` path ed to be pretty"
* The ``/wiki/`` path really points to a UI for interacting with the pageWhile URLs do not have to be pretty, they should be stable, especially when they are to be used as stable unique identifiers. Remocing all application specific information from the URL provides more stability by adding a layer of abstraction.
== Open Questions and Concerns ==
* We could apply content negotiation to the established page URLs using the `/wiki/` path. Such URLs are already in use for referring to Wikipedia pages in RDF (e.g. Using it to refer to the page content can be confusingby DBpedia and also by Wikidata). On the other hand, the `/wiki/` path is really a UI entry point, such URLs are already in use for referring to Wikipedia pages in RDFand it seems like a good idea to keep the UI separate from the data identifiers.
* "URLs don't need to be pretty"The proposed URL scheme does not have room for slot names. We will not be able to refer to slots other than the main slot. Possible solution: https://commons.wikimedia.org/data/main/Avignon_City_Wall.map. This is looking more and more thike the REST API URLs.
* While URLs do* The porposed schemes are not have to be pretty,stable against page renames. they shWe could be stable,use page IDs instead of the title. especially when they are to be used as stable unique identifiers.That makes the URLs a lot less intuitive, Remocing all application specific information from the URL provides more stability by adding a layer of abstraction.
and requires database access in order to construct them.
== Resources ==
...
* The ```/data/```` 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="" style="padding: 0 2px; color: #333333; background: rgba(251, 175, 175, .7);">``` interface.
...
* The REST API offers fairly clean URLs, but they still expose details about the web application and API version. Even the fact that they expose the fact that this is an API is too specific in a context where URLs are used as identifiers.* Apply conten* "URLs don't negotiation to the established page URLs using the ```/wiki/``` path ed to be pretty"
* The ``/wiki/`` path really points to a UI for interacting with the pageWhile URLs do not have to be pretty, they should be stable, especially when they are to be used as stable unique identifiers. Remocing all application specific information from the URL provides more stability by adding a layer of abstraction.
== Open Questions and Concerns ==
* We could apply content negotiation to the established page URLs using the `/wiki/` path. Such URLs are already in use for referring to Wikipedia pages in RDF (e.g. Using it to refer to the page content can be confusingby DBpedia and also by Wikidata). On the other hand, the `/wiki/` path is really a UI entry point, such URLs are already in use for referring to Wikipedia pages in RDFand it seems like a good idea to keep the UI separate from the data identifiers.
* "URLs don't need to be pretty"The proposed URL scheme does not have room for slot names. We will not be able to refer to slots other than the main slot. Possible solution: https://commons.wikimedia.org/data/main/Avignon_City_Wall.map. This is looking more and more thike the REST API URLs.
* While URLs do* The porposed schemes are not have to be pretty,stable against page renames. they shWe could be stable,use page IDs instead of the title. especially when they are to be used as stable unique identifiers.That makes the URLs a lot less intuitive, Remocing all application specific information from the URL provides more stability by adding a layer of abstraction.
and requires database access in order to construct them.
== Resources ==
...
TASK DETAIL
EMAIL PREFERENCES
To: daniel
Cc: MZMcBride, Rybesh, Dzahn, GWicke, tstarling, Aklapper, Jonas, Smalyshev, mkroetzsch, Lydia_Pintscher, daniel, QZanden, Salgo60, D3r1ck01, Izno, suriyaa, Eevans, mobrovac, Hardikj, Wikidata-bugs, aude, jayvdb, Southparkfan, fbstj, RobLa-WMF, santhosh, Mbch331, Jay8g, Ltrlg, Glaisher, bd808, Krenair, Legoktm
Cc: MZMcBride, Rybesh, Dzahn, GWicke, tstarling, Aklapper, Jonas, Smalyshev, mkroetzsch, Lydia_Pintscher, daniel, QZanden, Salgo60, D3r1ck01, Izno, suriyaa, Eevans, mobrovac, Hardikj, Wikidata-bugs, aude, jayvdb, Southparkfan, fbstj, RobLa-WMF, santhosh, Mbch331, Jay8g, Ltrlg, Glaisher, bd808, Krenair, Legoktm
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
