Closed Malvoz closed 4 years ago
Yes, this is the intention. It has been on my To-do for a while to go through & find the missing cross-links. So thank you for the reference list! I will try to get to these this week.
Edit: Updated to reflect changes in: https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/commit/0071b30625a29455ea3e4105aefce4e3eff5e755, https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/commit/ae59ecb6e8a85acbf21489916079a5afa2d398ae.
Additionally, most issues about use cases and capabilities point to the corresponding section in the spec (e.g. "This issue is for discussion of <link>") - I've found that many of these links aren't working anymore (some of these don't link to the spec at all, in some cases because there is no such section yet):
These examples link back to relevant sections of the spec, I've found that they have broken links (in some cases because no such section exist in the spec yet):
@AmeliaBR I've updated the lists above to reflect the changes made in https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/commit/0071b30625a29455ea3e4105aefce4e3eff5e755. And regarding the (new) examples that link back to use cases, many of the links are broken because they don't include some determiners while the id
s for the use case sections do. For example:
The show-vector-data-overlay-map.html example links to #use-case-show-vector-data-overlay-map
while the id for that section is use-case-show-a-vector-data-overlay-on-a-map
. Would you rather change the id
s in the spec, or the links from the examples in these cases?
Thanks for the updates @Malvoz. Yes, I'm still working on going through the rest of the links; that commit was just the first batch. But… it looks like I messed up in a few cases, by not including the use-case-
prefix on the link back to the spec from the example page. I'll review that.
I've also been simplifying the IDs as I go (to make it less likely that these little discrepancies will slip through), so for your example, probably both of those will end up changed!
Once I've done a full pass, I'll run the whole thing through a link checker & make sure we get this all tidied up.
OK, I think I've fixed the broken links and filled in the missing discussion issues for all the use-case sections (as of https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/commit/ae59ecb6e8a85acbf21489916079a5afa2d398ae).
Ran the main document through the W3C link checker, so at least I am sure that the links out of the report are OK. (Well, except for links to GitHub, since the link checker is blocked by robots.txt! But it's more likely that those are valid links but to the wrong issue rather than dead links, anyway!)
I still need to do another pass for editorial/content clean-up and standardizing the examples, so I'll double check the back-references (from the example files to the report) at that time.
Next step: missing issues for the capabilities section. Also: avoid breaking things again as we fill in additional sections!
Thanks, I've updated all the lists! :)
I resorted to removing things in the checklists that have been finished instead of checking the boxes, for an easier overview of what needs TBD.
The list has been updated per changes in https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/pull/124.
These use cases and capabilities are currently not linking to a corresponding github issue (perhaps because no such issue exist yet):
@AmeliaBR
I'd like to open issues for all the cases where there is none yet, and also cross reference them from the spec afterwards. Is that okay with you?
I'm not permitted to label issues - so I could add a follow-up comment on which labels for you to set to save you time, then I'd delete those comments at any time you've set the corresponding label(s).
Hi @Malvoz, If you want to go ahead and make the rest of the missing discussion pages, I would be grateful. I haven't had nearly as much time & energy for this project as I'd like this past month, and your contributions are definitely appreciated.
I've granted you Triage permissions for the repo, so you should be able to add any labels as required. But if you're not sure about any of the details, just ping me in a comment.
Seconding the gratitude, @Malvoz! I have been meaning to go through these but I'm dealing with a bad case of RSI at the moment and repetitive clicking actions like making issues en-masse are difficult. Your assistance here would be much appreciated!
@AmeliaBR "Take my energy ༼ つ ◕_◕ ༽つ" 😄
Thanks for allowing me to do this!
And thank you @nchan0154 for the kind words, too!
Whoosh!
I admit, I had one moment of panic when I saw the 30+ notification emails. Then I realized what they all were & “Hooray!”
Thanks again. It is very great to have those links ready before the big TPAC meeting, when we'll be trying to get new people looking at the report & starting discussions.
@AmeliaBR, @prushforth, @nchan0154, @NickFitz When you find that you have some time... (although this shouldn't take very long)
I think it's important (particularly for newcomers) that the issues for discussion properly link to their respective section in the report. Since refactoring some time ago, quite a few of the URLs have changed for certain sections of the report, thus they'll need to be updated - in some cases there is no link at all.
But this is all done below, so as issue owners you'll just have to edit your initial comment in each of those issues and copy & paste to include at the top:
@Malvoz I've just done mine, including editing the title for a couple of them to match the section they refer to where the wording of that's changed.
Thanks for your work on this!
@NickFitz
Thanks!
I had actually missed updating the link for #74
, I've updated it now, could you redo that one?
@Malvoz No problem, done :-)
Done, thank you @Malvoz!
Thank you Robert, you are a great collaborator! Done.
I did @ameliabr's too, cause she's either busy or asleep. I hope that's not bad github etiquette? I was on a roll in an airport lounge...
Thanks Peter!
Regarding issue https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/issues/21 - I had missed to include "Use Case:" in its title, it should rather be: "Use case: Access additional information about a point on the map".
And in https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/issues/9 you can remove the outdated reference:
Relevant section: https://maps4html.github.io/HTML-Map-Element-UseCases-Requirements/#google-maps-embeds-and-google-maps-platform-api
now that you've added the new reference.
Again, thanks, for doing both yours and Amelia's. This is great! Safe travels! 😄
Thanks Peter & Robert!
When I came up with this idea of using GitHub issues for section-by-section discussion, I did not think about all the extra work of keeping them in sync as the document gets re-written and re-organized!
The example pages have been revamped some time ago, and will need more work but I no longer consider them (or them not linking properly to the spec) "broken", closing this. Thanks for all your help! :)
In the hope of potentially saving you guys some time, I've been going through the spec for use cases and capabilities that do not link to an issue for discussion, and I've also tried to find the corresponding issue in any case there is one but it just hasn't been linked to from the spec.
Edit: Things TBD as listed below have been updated to reflect changes in: https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/commit/0071b30625a29455ea3e4105aefce4e3eff5e755, https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/commit/ae59ecb6e8a85acbf21489916079a5afa2d398ae, https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/pull/121/commits/6826d37de02e51d5e1b92089696e01846f5fa7d8, https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/pull/124, https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/pull/162.
These examples have broken links to corresponding use cases in the spec:
These issues aren't properly linking to their corresponding section in the spec, e.g.:
is missing, or have a broken link:
Items in https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/issues/110#issuecomment-529998014
These use cases and capabilities are currently not linking to a corresponding github issue (perhaps because no such issue exist yet):