I thought about it, but decided against pre-processing: The repo is meant to be an archive, and the XML spec can be looked up. If I were to introduce a new structure by pre-processing the files, I think that might be a plus for reading, but not for archiving. Whoever has a concrete use case (the "Digebu" website above looks great!), can write their own pre-processor for that use case.
I just want to archive the "official" XML files since the "official" website does not provide an archive. For that reason, I also don't change the XML files: The spec is available and everyone can build their own transform (to JSON, XML, whatever) based on their particular needs.
Some time ago, someone from the digital service of Germany reached out and asked about my use case. Maybe there will be an official version of a "Git law" repo someday...
Thanks! I tried, but I have not yet found a way to make such guides unobtrusive. I will try out your suggestion. It is very motivating to see that people care about my little side project so much that they post a comment. So, thank you, made my day!
It is basically a timer for your breathing exercises, as the idea is that you inhale and exhale slowly, hold your breath in between, each step lasting 4 seconds.
I tried to make it as simple as possible, and to make it usable with old devices as well.
Parsing the legal acts with the tools you mention looks very interesting! Currently, I simply collect the published XML files whose structure is optimized for laying out the text and not so much for representing a structure of sections and subsections.
I built this tool for my girl friend. A small nimble website to help you focus on breathing deep, like really deep:
Inhale for four seconds, hold your breath for four seconds, exhale for four seconds, hold your breath for four seconds, and repeat...
Very simple. And yet, taking deep breaths helps you focus on your body and calms your mind. Try it out.
The website is very minimal on purpose – no tracking, no accounts, no newsletter banners, no tracking. Nevertheless, if you miss a feature, please leave a comment.
> “Git for everything“ would be a multi-billion dollar startup easily.
Worked on a “Git for Word” project [1], which is currently on hold.
The diff part was manageable, though not trivial to get diffs that make sense for prose/regular text.
The hard parts are UX/UI (making Git concepts transparent to “normal” users) and merging. Yet without automatic merging, branching is not very convenient.
Would love to collaborate on this in the future again. Reach out if you are working in this space, happy to share.
This looks great! I share your sentiment: I looked into the XML files for the published German legal texts[1], and they seem to be made for display purposes only.
Many available options seem to be based on manual annotation and, therefore, cover a limited range of all legal texts. Especially with regard to regulatory topics, those research sites usually fall short.
I wish this was available for legal texts, making it easy to jump from one law to the referenced next legal provision. Many legal provisions, especially in very regulated areas, make use of “functions” “imported” from other, totally different laws.
Sorry for being off-topic, but if anyone knows a resource for that, I am super interested!