Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Provide a physicalLocation on a stack frame #69
Labels
Comments
michaelcfanning
changed the title
ghost
self-assigned this
|
Closed in c443e9a. |
ghost
mentioned this issue
michaelcfanning
added a commit
that referenced
this issue
Oct 28, 2022
michaelcfanning
added a commit
that referenced
this issue
Nov 9, 2022
Minutes for SARIF TC meeting #69, 2022/10/27.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently break out uri, uriBaseId, etc. on a stack frame instead of putting a physicalLocation on it. I think the reason is that we didn't see value in providing all the information in a physicalLocation (a region doesn't exactly make sense for a stack frame).
I think it might be preferable to simply have the physicalLocation object, though, with the caveat that its region data is not likely to cover a multi-line span.
The text was updated successfully, but these errors were encountered: