Yes, the cemetery categorization was my initial example for this suggestion, but it could apply to many other templates as well. I have suggested the tagging of elements to make life easier on WBE developers in the past, but I think it's on the back burner until the site redesign happens.
The cemetery situation that I am referring to is one where the burial location on Find a Grave is actually incorrect (the manager has guessed the location might be in a certain cemetery, but documentation from other family members states that they were buried on their private homestead, and I don't control the Find a Grave profile).
Admittedly, sameas=no is not the ideal solution to this edge case. If the parameter were called "ignore" instead of "sameas" then it would be clearer, as the main intent of the sameas parameter, as stated in the documentation, is that it "helps define the correct memorial page for usage in WikiTree+ hints."
When developing WBE, we only have access to the rendered HTML on the profile you're currently viewing (unless we make a separate API call and force the user to be logged in). It doesn't pass along any of the metadata from those template parameters so that they can be consumed.
So, for example, if somebody makes a feature for WBE to highlight the FamilySearch and Find a Grave links for the person in a toolbar at the side or top, it can't detect whether that Find a Grave link was entered as a plain URL in the bio, whether it was generated by the {FindAGrave} template, or whether the sameas parameter was set. So in the example you used, where one profile uses the Find a Grave memorial of a family member as a source, or links directly to the Find a Grave memorial for a relative who doesn't currently have a profile on WikiTree, WBE might show the wrong link to the user.
This, of course, still would depend on editors using templates instead of direct links to external sites.
So, the request is to have that data in any HTML elements rendered by a template, and in addition, for the structural elements on the page to be more clearly tagged so that features like Readability Options don't require code like this to detect the various components of the profile page.
This could include many items, such as:
- linked people, spaces, categories, etc.
- bio sections like Biography, Sources, DNA, etc.
- various icons, buttons, navigation
- source list items generated by <ref>
- and many others queried here