Adding where to new att.locatable to address #1769

[ebeshero]

I've moved @where to a new att.locatable and I'm hoping we can look at / improve my new explanation of it. I'm also hoping we can add some translations to other languages here.

[ebeshero]

Okay, we're really passing build tests now. Let's take a look and see if this is what we want to add to the Guidelines.

[peterstadler]

the bibliography shows a lot of whitespace changes. Is it somehow possible to reset these and only add the needed changes?

[peterstadler]

I think we'll need an example for resolving the where="#L" as all other targets of references ("#bellaf" and "#perf1") are provided.

[ebeshero]

@peterstadler @martindholmes @martinascholger @TEITechnicalCouncil Thanks for your help with this PR! I've made some changes as we discussed to expand the examples, so we now have some lists of stage movements for @where to point to. I've also made some revisions to the wording as suggested, and I restored the spacing I think as it was before in the BIB, and just added my new entry. How does this look?

[ebeshero]

Edited the above to separate this part out: If we decide this is okay to merge into dev, can I get some help with figuring out how to do something like a deprecation of the old way of doing things, like we discussed in our meeting? @sydb : I'm trying to remember how we do this.

[ebeshero]

Just an update on this branch--I think we resolved the requested changes now, but there's an outstanding issue (not on the reviews I think?) about how we talk to people about their use of the new datatype on @where which might invalidate existing values. I could use a little help with that, but I'll try something on it later today.

[ebeshero]

VF2F decision: We are thinking of better ways to handle the expression of stage movement, and think att.locatable is probably not the best approach to take now. Closing and not merging.