Laws.Africa Developer Guide
  • Laws.Africa Developer Guide
  • Get Started
    • Introduction
    • Quick start
    • Works and expressions
    • Webhooks
    • Changelog
  • Tutorial
    • About the tutorial
    • Module 1: Build a legislation reader
      • Introductory concepts
      • Create a basic Django app
      • Create database models
      • Fetching the data
      • Work listing page
      • Expression detail page
      • Styling with Law Widgets
      • Adding interactivity
      • Staying up to date
    • Module 2: Enrichments and interactivity
      • Basic enrichments
      • Advanced enrichments
      • Advanced interactivity
    • Module 3: Text extraction for search and analysis
      • Why extracting text is important
      • Basics of text extraction
      • Advanced text extraction
      • Extracting text for analysis and machine learning
  • Content API Reference
    • About the Content API
    • Authentication
    • Pagination
    • Places
    • All work expressions
    • Single work expression
      • Commencements
      • Embedded images
      • Publication document
      • Table of Contents
      • Timeline
    • Taxonomy topics
    • Enrichment datasets
  • AI API Reference
    • About the AI API
    • Authentication
    • Knowledge Bases
  • How-to Guides
    • How to use the Table of Contents API
    • How to download images
Powered by GitBook
On this page
  • In this section
  • Works and expressions
  1. Tutorial
  2. Module 1: Build a legislation reader

Introductory concepts

Some key details before we build our legislation app.

PreviousModule 1: Build a legislation readerNextCreate a basic Django app

Last updated 1 year ago

In this section

  • Works and Expressions

  • FRBR URIs

Works and expressions

A work is a piece of legislation.

It does include all the metadata concerning publication and other lifecycle events (commencements, amendments, and repeals).

It does not include the text and other content, because there can be more than one version of the content (depending on the language and date).

An expression is the content of a work, in a given language and at a given date.

A work can have multiple expressions. Most of the metadata on an expression is inherited from its work.

One key difference between a work and an expression is that an expression can have a different title from the work's, according to its language and date.

The language and date belong to the expression only.

FRBR URI essentials

An FRBR URI uniquely identifies a work and an expression.

The FRBR URI is created using some core metadata of the work and expression.

Work-level FRBR URI example:

/akn/za/act/1996/93

Because an expression inherits these core pieces of metadata from its work, an expression-level FRBR URI is the parent URI, plus the language and the date of the expression.

Expression-level FRBR URI examples:

/akn/za/act/1996/93/eng@1996-11-22

/akn/za/act/1996/93/eng@2000-08-01

In the above example, the expressions are the English-language versions, from 22 November 1996 onwards, and from 1 August 2000 onwards, of a South African national Act, 93 of 1996. The work is Act 93 of 1996, which can and does have multiple expressions.

While the work's title is the National Road Traffic Act, the expressions may have different titles. This is more common in the case of different language versions, although some pieces of legislation are renamed over time. In those cases, the older expressions will have the old title, and the work and the newer expressions will have the new one.

Read more about the terminology used by Laws.Africa in our .

Terminology Guide