<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Laws Foundation</title><link>https://openlawsfoundation.org/</link><description>Recent content on Open Laws Foundation</description><generator>Hugo</generator><language>en</language><atom:link href="https://openlawsfoundation.org/index.xml" rel="self" type="application/rss+xml"/><item><title>AKN4OLF: the profile</title><link>https://openlawsfoundation.org/spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://openlawsfoundation.org/spec/</guid><description>&lt;h2 id="the-core-principle"&gt;The core principle&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We normalize metadata, not content.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Legal &lt;em&gt;content&lt;/em&gt; is not normalizable across jurisdictions, and trying to do it is how
this kind of project dies. An Italian &lt;em&gt;comma&lt;/em&gt;, a U.S. &lt;em&gt;section&lt;/em&gt;, and a French &lt;em&gt;article&lt;/em&gt;
are not three names for the same object: they differ in granularity, hierarchy, and
citation rules. Force them into one schema and you either lose everything that makes
each jurisdiction useful (lowest common denominator) or build an unmaintainable monster
with a field for every national exception (highest common multiple).&lt;/p&gt;</description></item><item><title>Archive: the canonical corpus</title><link>https://openlawsfoundation.org/archive/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://openlawsfoundation.org/archive/</guid><description>&lt;h2 id="generated-not-curated"&gt;Generated, not curated&lt;/h2&gt;
&lt;p&gt;The archive is the project&amp;rsquo;s &lt;em&gt;output&lt;/em&gt;, not its source of truth. Every document in it came
out of the &lt;a href="https://openlawsfoundation.org/pipeline/"&gt;pipeline&lt;/a&gt;, built from an official source, validated against the
&lt;a href="https://openlawsfoundation.org/spec/#the-conformance-suite"&gt;conformance suite&lt;/a&gt;, and reproducible from that source.&lt;/p&gt;</description></item><item><title>Contributors</title><link>https://openlawsfoundation.org/contributors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://openlawsfoundation.org/contributors/</guid><description>&lt;p&gt;This page is generated, not hand-curated. Founders aside, everyone here earned their
place with commits to the foundation&amp;rsquo;s own repositories, and the list ignores nothing and
no one: if you have a merged contribution and you&amp;rsquo;re missing, it&amp;rsquo;s a bug, not a snub.&lt;/p&gt;</description></item><item><title>Diff: semantic and type-aware</title><link>https://openlawsfoundation.org/diff/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://openlawsfoundation.org/diff/</guid><description>&lt;h2 id="why-a-normal-diff-isnt-enough"&gt;Why a normal diff isn&amp;rsquo;t enough&lt;/h2&gt;
&lt;p&gt;Run &lt;code&gt;diff&lt;/code&gt; on two versions of an act and you get added and removed lines. A lawyer, a
journalist, or a downstream system does not care that line 412 moved. They care what kind
of change it was. Did the substantive text of an article change? Did the entry into force
shift? Or was it just a typo fix, a renumbering, a formatting cleanup?&lt;/p&gt;</description></item><item><title>Pipeline: adapters and ingest</title><link>https://openlawsfoundation.org/pipeline/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://openlawsfoundation.org/pipeline/</guid><description>&lt;h2 id="what-the-pipeline-does"&gt;What the pipeline does&lt;/h2&gt;
&lt;p&gt;We don&amp;rsquo;t invent a corpus. We build the machinery that lets anyone take their own
jurisdiction&amp;rsquo;s &lt;em&gt;already-published&lt;/em&gt; legal data and turn it into a common, verifiable,
interoperable form, then keep it that way as the law changes.&lt;/p&gt;</description></item><item><title>Principles</title><link>https://openlawsfoundation.org/principles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://openlawsfoundation.org/principles/</guid><description>&lt;h2 id="1-normalize-metadata-never-content"&gt;1. Normalize metadata, never content&lt;/h2&gt;
&lt;p&gt;This is the rule everything else follows from. Legal content does not normalize across
jurisdictions, and the projects that try to force it either collapse into a useless lowest
common denominator or balloon into an unmaintainable schema with a field for every national
exception.&lt;/p&gt;</description></item></channel></rss>