Go to file
2023-11-04 00:19:12 +01:00
data test with more laws 2023-11-04 00:12:14 +01:00
src add docs 2023-11-04 00:19:12 +01:00
.gitignore empty rust project 2023-11-03 13:45:25 +01:00
.gitlab-ci.yml add ci 2023-11-03 22:41:22 +01:00
Cargo.lock Start paring ris law overview 2023-11-03 22:40:19 +01:00
Cargo.toml Start paring ris law overview 2023-11-03 22:40:19 +01:00
README.md add next step 2023-11-04 00:06:42 +01:00

RISolve

History

Goals

  • I want to have the text of the law.
  • I want to see the structure (proper headers) of the law.
  • I want to be able to make comments (e.g. Erschöpfung) on certain parts
  • I want to see since when this paragraph is in use.
  • Lawtext should be updateable

Technical

  • I don't want to restrict myself with a parser combinators but code it myself using recursive descent parser.
  • Be strict in what I process. Fail if anything unexpected happens. The user should handle this case. It's fine if one decides to ignore the new/unexpected field, but it should be done deliberately.

Progress / Functions

  • Parse structure of law into struct using Deserilize trait, pot. multiple requests (if > 100 paragraphs)
  • Parse risdok using own RD parser, again strict: fail if anything not expected happens, not sure (yet) if I want to operate on strings, or first parse using off-the-shelve XML reader (prob. 2nd option)

Next step

  • Fetch all pages of law overview (mostly copy from law)

Naming

  • Law ("Gesetz"): e.g. UHG, TEG, ABGB
  • Section ("Paragraph")
  • Subsection ("Absatz")
  • Item ("Ziffer")
  • Heading-{1,2,3,...}