Change Details

We need to decide on what HTML to attach our Wikidata bridge app. **This may have larger implications for the Wikidata technical strategy.** Two options: #### 1. Add needed extra data to a wrapping element around the link ``` <span data-bridge-edit-flow="overwrite" > <a href="https://www.wikidata.org/Q123?uselang=en#P456">🖊</a> </span> ``` **Pros:** * We are using a `data`-attribute which is intended for exactly that purpose -- holding data **Cons:** * Wikidata knows nothing about the people that arrive via these links, we cannot make use of that information later #### 2. Add needed extra data to the query string of the link ``` <a href="https://www.wikidata.org/Q123?uselang=en&bridge-edit-flow=overwrite#P456">🖊</a> ``` **Pros:** * all the info is available in the link to Wikidata and could in the future be used there, for example for an edit wizard **Cons:** * Wikidata gets query parameters that it doesn't understand * might be harder to select for * link target for editing multiple statements, possibly with different properties or even entities, is not obvious * space in the URL is limited What is our strategy regarding easier human editing on wikidata.org and might that strategy have implications for how we proceed here?

We need to decide on what HTML to attach our Wikidata bridge app. **This may have larger implications for the Wikidata technical strategy.** Two options: #### 1. Add needed extra data to a wrapping element around the link ``` <span data-bridge-edit-flow="overwrite" > <a href="https://www.wikidata.org/Q123?uselang=en#P456">🖊</a> </span> ``` **Pros:** * We are using a `data`-attribute which is intended for exactly that purpose -- holding data **Cons:** * Wikidata knows nothing about the people that arrive via these links, we cannot make use of that information later #### 2. Add needed extra data to the query string of the link ``` <a href="https://www.wikidata.org/Q123?uselang=en&bridge-edit-flow=overwrite#P456">🖊</a> ``` **Pros:** * double implementation, and resulting [documentation] complexity, (relevant data partially on the link, partially in data attributes //or// completely in data attributes) is avoided * the bridge app enhances only elements that natively already exhibit click behavior * source for "user error", what happens if multiple links are present inside an area marked-up with data attributes, is avoided * all the info is available in the link to Wikidata and could in the future be used there, for example for an edit wizard **Cons:** * Wikidata gets query parameters that it doesn't understand * might be harder to select for * link target for editing multiple statements, possibly with different properties or even entities, is not obvious * space in the URL is limited What is our strategy regarding easier human editing on wikidata.org and might that strategy have implications for how we proceed here?

We need to decide on what HTML to attach our Wikidata bridge app. **This may have larger implications for the Wikidata technical strategy.** Two options: #### 1. Add needed extra data to a wrapping element around the link ``` <span data-bridge-edit-flow="overwrite" > <a href="https://www.wikidata.org/Q123?uselang=en#P456">🖊</a> </span> ``` **Pros:** * We are using a `data`-attribute which is intended for exactly that purpose -- holding data **Cons:** * Wikidata knows nothing about the people that arrive via these links, we cannot make use of that information later #### 2. Add needed extra data to the query string of the link ``` <a href="https://www.wikidata.org/Q123?uselang=en&bridge-edit-flow=overwrite#P456">🖊</a> ``` **Pros:** * all the info is available in the link to Wikidata and could in the future be used theredouble implementation, and resulting [documentation] complexity, (relevant data partially on the link, partially in data attributes //or// completely in data attributes) is avoided * the bridge app enhances only elements that natively already exhibit click behavior * source for "user error", what happens if multiple links are present inside an area marked-up with data attributes, for example for an edit wizardis avoided * all the info is available in the link to Wikidata and could in the future be used there, for example for an edit wizard **Cons:** * Wikidata gets query parameters that it doesn't understand * might be harder to select for * link target for editing multiple statements, possibly with different properties or even entities, is not obvious * space in the URL is limited What is our strategy regarding easier human editing on wikidata.org and might that strategy have implications for how we proceed here?