Skip to content

LOF-ODP-005: Legal Time and Versions

Identifier LOF-ODP-005
IRI https://w3id.org/lof/odp-005.owl
Repository https://github.com/legal-ontologies-foundry/lof-odp-005
Status draft
Version 0.1.0
Depends on LOF-ODP-001, LOF-ODP-002, LOF-ODP-003, LOF-ODP-004
Drafted by David R. Koepsell
For review by William Mandrick, Barry Smith

Draft for review

First draft, prepared for discussion by the founding coordinators. Open questions are listed at the end.

Intent

ODP-001 to 004 say what legal content is and how a position comes to exist, but not when. A legal question is almost always a question at a time: was the Directive or the Regulation the law on 15 March 2017; did the controller notify within seventy-two hours; which text was in force when the contract was signed. This pattern gives legal content its periods, records the acts that change it, distinguishes the consolidated texts people actually read from the law they consolidate, and gives positions the periods within which they must be discharged.

Three distinctions carry most of the weight.

  • In force is not applies. The General Data Protection Regulation entered into force on 24 May 2016 and applied from 25 May 2018. Retroactive content applies to a period before it is in force. Repealed content goes on governing facts that occurred while it applied.
  • Content is succeeded, not changed. An amending act establishes content of its own, which succeeds the amended content in whole or in part. The amended content is unchanged; what changes is which content is in force.
  • A consolidation is not, by default, law. EU consolidated texts have no legal force. A United States Code title enacted as positive law does.

Competency questions

  1. What legal content was in force at a given time?
  2. What legal content applies to a given occurrence, and what was in force but did not apply to it?
  3. What amended or repealed this content, in what act, and when did its force end?
  4. Which consolidated version states the law during a given period, and what content does it combine?
  5. Which positions were not discharged within the period they were due within, computed from what occurrence, and what positions does the end of that period trigger?

All five are answered by SPARQL (src/sparql/).

Solution

Diagram

flowchart BT
  n0["amending act"]
  n1["repeal"]
  n2["consolidated version"]
  n3["compliance period"]
  n4("legal act")
  n0 -->|is a| n4
  n1 -->|is a| n4
  n5("generically dependent continuant")
  n2 -->|is a| n5
  n6("temporal region")
  n3 -->|is a| n6
  n7("legal content")
  n4 -. amends .-> n7
  n4 -. repeals .-> n7
  n7 -. succeeds .-> n7
  n7 -. in force during .-> n6
  n7 -. applies during .-> n6
  n2 -. consolidates .-> n7
  n2 -. states the law during .-> n6
  n8("first-order legal position")
  n8 -. due within .-> n6
  n9("occurrent")
  n6 -. computed from .-> n9
  classDef ext stroke-dasharray: 4 3,opacity:0.8
  class n4,n5,n6,n7,n8,n9 ext

Solid boxes are this pattern's classes; dashed boxes are classes from BFO or other patterns. Solid arrows mean is a; dotted arrows are relations, from domain to range. Drawn automatically from the tables below, so it always matches them.

Classes

Label IRI BFO parent Definition
amending act ODP005_0001000 legal act (defined) A legal act that establishes legal content succeeding some legal content established earlier, or that ends, suspends, or alters the force or scope of such content.
repeal ODP005_0001001 legal act (defined) A legal act that establishes that some legal content established earlier ceases to be in force.
consolidated version ODP005_0001002 generically dependent continuant A generically dependent continuant that combines some legal content with the content succeeding it in part, as they stand during some temporal region.
compliance period ODP005_0001003 temporal region (defined) A temporal region within which some first-order legal position is to be discharged.

Relations

Label IRI Domain Range Definition
amends ODP005_0001100 legal act legal content The act establishes content succeeding the content, or ends, suspends, or alters its force or scope.
repeals ODP005_0001101 legal act legal content Subproperty of amends: the act establishes that the content ceases to be in force.
succeeds ODP005_0001108 legal content legal content The first replaces the second, in whole or in part, from the time the first is in force.
in force during ODP005_0001102 legal content temporal region The maximal region throughout which the content is part of the law in force.
applies during ODP005_0001103 legal content temporal region The maximal region during which the content directly governs what occurs. Asserted only of directly applicable content.
consolidates ODP005_0001104 consolidated version legal content The version combines the content (base or succeeding).
states the law during ODP005_0001105 consolidated version temporal region The version's own region, during which it correctly combines the content in force.
due within ODP005_0001106 first-order legal position temporal region The position is to be discharged within the region.
computed from ODP005_0001107 temporal region occurrent According to legal content, the region is computed from the occurrent (it need not begin there).

Data property

Label IRI Domain Range
has date-time value ODP005_0001200 temporal instant xsd:dateTimeStamp (functional)

A region's bounds are its BFO instants, related by has first instant (BFO_0000222) and has last instant (BFO_0000224); the date and time sit on the instant. xsd:dateTimeStamp is in the OWL 2 datatype map and requires a time zone; xsd:date, xsd:duration and the xsd:g* types are not in the map.

Conventions. Regions are closed and recorded to the second, so the GDPR's Directive predecessor is in force until 23:59:59 on 24 May 2018 and the GDPR applies from 00:00:00 on 25 May. Where the law gives a date and no time, the time zone is a stated convention, not a rule of the source: for EU acts the example uses midnight Brussels time. Values are compared in SPARQL after casting to xsd:dateTime.

Axioms (Manchester syntax)

amending act         EquivalentTo  legal act and (amends some legal content)
repeal               EquivalentTo  legal act and (repeals some legal content)
repeals              SubPropertyOf amends
has date-time value  Domain temporal instant, Range xsd:dateTimeStamp, Functional
consolidated version SubClassOf    generically dependent continuant
    and (consolidates some legal content)
    and (states the law during some temporal region)
compliance period    EquivalentTo  temporal region
    and (inverse (due within) some first-order legal position)

Grounding rationale (LOF-P-004)

  • Periods are temporal regions, not processes. Being in force is not something that happens; it is a standing condition that holds through a region of time. The pattern therefore relates content to BFO temporal regions instead of reifying a "force" entity. Entry into force is the first instant of such a region, a BFO temporal instant.
  • Calendar values on instants, not regions. BFO already relates a region to its first and last instants. Putting the date-time on the instant keeps one value per entity, makes an instant reusable as the bound of several regions (the last instant of a compliance period is also what triggers the power to fine), and matches OWL-Time, where time:inXSDDateTimeStamp sits on time:Instant.
  • Amendment as succession of content. Legal content is a generically dependent continuant (ODP-001). Treating amendment as the establishment of new content that succeeds the old, rather than as a change in old content, keeps every version citable as it stood and avoids ascribing change to an abstract pattern.
  • Consolidated version as generically dependent continuant. A consolidation is information content about the law. It is not declared disjoint from legal content, so that an enacted consolidation can be asserted to be both (LOF-P-010). It has its own period, because it stops stating the law at the next amendment while the base content stays in force.
  • Compliance period as a defined temporal region. No new primitive: a region is a compliance period by being the period some position is due within.

Example

The GDPR, the Directive it repealed, and the United Kingdom Act that transposed the Directive, with real dates; and a hypothetical controller that notifies one breach late and one in time. Excerpt:

ex:gdprEnactment a odp1:0001003 ;            # enactment
    odp1:0001100 ex:gdpr ;                   # establishes
    odp5:0001101 ex:directive9546 .          # repeals (Art. 94(1)), with effect from 25 May 2018
ex:dpa1998Enactment a odp1:0001003 ;
    odp1:0001100 ex:dpa1998 ;
    odp1:0001102 ex:directive9546 .          # performed under: transposition

ex:gdpr odp5:0001102 ex:gdprInForce ;        # in force during (Art. 99(1))
        odp5:0001103 ex:gdprApplies ;        # applies during (Art. 99(2))
        odp5:0001108 ex:directive9546 .      # succeeds
ex:directive9546 odp5:0001102 ex:directiveInForce .   # in force, never applying to private processing
ex:dpa1998 odp5:0001102 ex:dpaInForce ; odp5:0001103 ex:dpaInForce .

ex:gdprApplies obo:BFO_0000222 ex:t20180525 .          # has first instant
ex:t20180525 odp5:0001200 "2018-05-24T22:00:00Z"^^xsd:dateTimeStamp .   # 25 May 2018, 00:00 Brussels

ex:window1 odp5:0001107 ex:awareness1 ;      # computed from (aware at 08:40)
    obo:BFO_0000222 ex:window1Start ;        # 09:00: Reg. 1182/71 Art. 3 excludes the starting hour
    obo:BFO_0000224 ex:window1End .          # 5 March 2026, 08:59:59 UTC
ex:notifyDuty1 a odp3:0001002 ;              # duty (Art. 33(1))
    odp5:0001106 ex:window1 ;                # due within
    odp4:0001106 ex:window1 .                # undischarged during
ex:finePower1 a odp3:0001005 ;               # power (Art. 83(4)(a))
    odp4:0001102 ex:window1End .             # triggered by the end of the period

Inferred by HermiT, under both ODP-003 options: the adoption of the GDPR is a repeal and so an amending act; both seventy-two-hour windows are compliance periods.

Question Answer from the example
In force on 15 March 2017 Directive 95/46/EC, the Data Protection Act 1998, and the GDPR
Applies to processing in March 2017 the Data Protection Act 1998; the Directive and the GDPR are in force but do not apply to it
Repealed, succeeded, force ended Directive 95/46/EC, by the adoption of the GDPR, succeeded by the GDPR, end of 24 May 2018
Consolidation text 02016R0679-20160504 combines the GDPR and states the law from 24 May 2016
Overdue Acme's duty to notify breach 1, due by 5 March 2026 08:59:59 UTC, computed from its awareness of the breach; the end of the period triggers the authority's power to fine

Two points the example makes explicit. Article 33(1) requires notification "without undue delay and, where feasible, not later than 72 hours"; the compliance period records the fixed limit, and whether a later notification with reasons was lawful is for the rule layer. And the fine of Article 83 is a sanction, not a remedy in the ODP-004 sense of making good the failure, so the power is linked by what triggers it, not by remedies (open question 5).

The example also contains a period that ends before it begins, which the shapes report as a violation. The full example is src/examples/gdpr-timeline.ttl.

This pattern ELI Akoma Ntoso OWL-Time LOMO (Legal Ontology for Modelling Obligations)
amends, repeals eli:amends, eli:repeals (between legal resources), close match active and passive modifications, close match none none
succeeds none textual modifications (substitution, insertion), related none none
in force during eli:first_date_entry_in_force, eli:date_no_longer_in_force, close match forceMod (entryIntoForce, endOfEnactment, postponementOfEntryIntoForce), close match interval, via its instants none
applies during eli:date_applicability, close match efficacyMod, related interval lomo:TemporalSpecification with function validity, related
consolidated version eli:consolidates, eli:LegalExpression versions, close match FRBRExpression with a version date, close match none none
due within, computed from none none none lomo:TemporalSpecification with function deadline, lomo:trigger, related
has date-time value dates as xsd:date dates in FRBRdate time:inXSDDateTimeStamp, exact lomo:instant (non-OWL-2 datatypes), related

The mappings are also published as SSSOM in src/mappings/odp-005-standards.sssom.tsv.

ELI and Akoma Ntoso record these facts about documents and their expressions. This pattern records them about legal content, so that a period of force can be related to the positions grounded in that content and to the chain of ODP-004.

Consequences and limitations

  • Instance level only. The pattern records that a particular period was computed from a particular occurrence. The rule "seventy-two hours after becoming aware" is type-level and belongs to a rule layer, as in ODP-004.
  • No interval reasoning in OWL. OWL cannot compare date-time values within class definitions, so "in force at t" and "overdue" are answered by SPARQL, and period well-formedness by SHACL. The pattern deliberately does not import OWL-Time's interval algebra, which would add Allen relations the queries do not need.
  • Suspension and revival are represented as several in force during regions for the same content; the gap between them is the suspension.
  • No discharge relation. The pattern says a position is due within a period and, with ODP-004, that it went undischarged during it. It does not link a position to the process that discharged it (open question 3).
  • Repeal is not the only end of force. A sunset clause, implied repeal, desuetude, or annulment ends force with no repealing act; the pattern records them by the last instant of the region in force alone, so CQ3 sees only repeals made by acts.
  • One time line. The pattern records the periods as now understood. When a court annuls content ex tunc, the content was in force as people then believed and is treated as never in force afterwards. Recording both requires a second, transaction-time dimension (open question 6).
  • Jurisdiction. Nothing in the pattern assumes the European Union. It has been checked against the forms below, all of which it can express (LOF-P-010):
Form How it is expressed
Delayed application (GDPR) in force during and applies during with different first instants
Retroactivity applies during a region that begins before the in force during region
Sunset clause an in force during region whose last instant is set by the enacting content
Repeal with saving provision in force during ends; applies during continues for facts before the repeal
Suspension, revival two in force during regions
Directive and transposition the directive in force during only; the transposing content applies during, its enactment performed under the directive (ODP-001)
Positive-law codification (US Code) a consolidated version asserted also to be legal content established by an enactment
Annulment by a court the last instant of the region in force, with no repealing act

Open questions for the founding coordinators

  1. Amendment target. Amends relates an act to the content it amends, following ODP-001, and succeeds relates the texts. Should amended by (content to act) also be provided, or is the inverse enough?
  2. Limitation periods and other periods for second-order positions. A limitation period, or a time to appeal, is a period within which a power may be exercised, not one within which a position must be discharged. Due within does not cover it. Should there be a parallel exercisable within for powers, here or in ODP-004?
  3. Discharge. Should a relation from a position to the process that discharged it (discharged by) be added here, in ODP-004, or in a compliance pattern of its own?
  4. Versions of positions. When content is succeeded, are the positions it grounds ended and replaced, or do they persist? Under ODP-003 Option A they are replaced; under Option B they may persist. The pattern takes no position, and the example does not depend on it.
  5. Sanctions. A fine is not a remedy in the ODP-004 sense. Should ODP-004 distinguish sanctions (powers whose exercise penalizes the failure) from remedies (positions that make it good), with sanctioning positions linked to the failure they penalize?
  6. Bitemporality. Annulment ex tunc (and the Akoma Ntoso treatment of unconstitutionality) needs a record of what was believed in force at a time as well as what is now held to have been in force. Should the Foundry add a transaction-time layer, or leave it to the data store?
  7. Instants as triggers. The end of a compliance period triggers the power to fine. ODP-004 triggered by has the range occurrent, and a BFO instant is a temporal region, an occurrent, so this is valid; should ODP-004 say so explicitly?
  • LOF-ODP-001 supplies legal act, legal content, enactment, and performed under; amending acts and repeals are legal acts.
  • LOF-ODP-002 is imported with the other base patterns. The pattern uses none of its terms directly, but content that confers a role (an office with a fixed term) is given its periods like any other.
  • LOF-ODP-003 supplies first-order legal position, the domain of due within.
  • LOF-ODP-004 supplies triggered by and undischarged during; entry into force and the end of a compliance period are typical triggers.
  • LOF-ODP-006 uses these periods for the scope in time of a derogation; lex posterior compares enactments (ODP-001).

Discussion