-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idea: checksums or digital signatures for statute text #124
Comments
Hi @dogweather, We actually have an api endpoint for getting a list of updates to a specific law sub document (looks like this is missing from our documentation though). Does this help? |
hmm, yeah that's an interesting problem. The text diff sounds like a reasonable solution, we actually do something similar internally to check bill text accuracy. Let me know how it goes. That website looks amazing btw, well done! |
Thanks, I really appreciate it. |
I'm kicking around ideas for enabling the end user to verify a website's text against the official API content. E.g., I pull from the API to create this page:
https://newyork.public.law/laws/n.y._insurance_law_section_3217-d
Now, how can I help site visitors verify that the text is unchanged and up to date? Currently I do two things:
https://newyork.public.law/laws/information-about-updates
I'd like to take this further
Somehow - maybe a browser plugin - that'd check the text after loading the page. My current best idea is to reduce the two texts to a normalized whitespace and then do a diff. It'd reflect the result to the user, and on demand show how it arrived at that result.
Now, if the API included e.g. a SHA checksum or public key-based signature, that could enable more scenarios.
The text was updated successfully, but these errors were encountered: