Intertween.*

Knowledge Objects: sources we can follow

A Knowledge Object gives a particular source an identity and describes its origins, context, responsibility and conditions of use. It may describe a document, an observation or a method that others can understand and build on.

Follow the bill and its evidence →

The file does not tell the whole story

A document contains information. Understanding its meaning also depends on where it comes from, which decisions it informed, who reviewed it and how it has been used. A Knowledge Object gives those relationships a place.

A guideline can be easy to open but difficult to use. What evidence supports it? Is this the right version? Does it apply in the same circumstances? Who is responsible for keeping it current? A Knowledge Object connects those details to the knowledge described in the guideline.

In Intertween’s model, the knowledge has its own identity. A PDF, a record in an organisational system and a restricted view can be different representations of the same object. Source material can remain with its custodian. The object’s description and references help us understand what we have found.

What needs to travel with knowledge?

Source and evidence
Where does the information come from, and what evidence can be examined?
Context and relationships
Which question, place or situation does it concern? What does it build on and connect to?
Conditions and responsibility
Who stewards the source? What may be shown and used, by whom and for which purpose?
Version, review and uncertainty
What has changed? Has the information been reviewed, challenged or superseded? What do we still not know?

The Knowledge Object describes a particular piece of knowledge. The relational metadata register describes how objects connect. A relationship can show the evidence behind an assessment or the method developed from it. Read about relationships and the register ↗

The same report, different needs

A Knowledge Object can be described differently for different recipients. This is a separate fictional example. It does not affect the parliamentary document chain.

FICTIONAL TEACHING EXAMPLE

One Knowledge Object, different views

Choose an example role and purpose. A different question can narrow the selection but grants no new rights. The controls only switch prepared views; they do not check real permissions.

Report KO-024 and connections shown in the selected example viewPublic guidelines. The graphic does not indicate whether other connections exist.KO-024Public guidelines

Public

KO-024 · Municipal report · the same identity in every view

Public summary

The municipality is examining how school transport decisions could become more consistent.

Only connections included in the selected example view are shown. The view does not reveal whether other protected connections exist.

In practice, the responsible organisation must assess access and use. Metadata may also need protection. A role or a selected purpose is not sufficient to grant access.

SOURCE EXAMPLE · PRESERVED MATERIAL

Seven connected documents

An inquiry leads to a bill and then to an act. Here the documents can be followed as Knowledge Objects, with references showing how they connect. The sources are open data from the Swedish Parliament.

Select a document to inspect its saved metadata and connections. The complete flow in the next chapter is available for bill 2021/22:225.

Select a step in the chain

Bill · 2021/22:225

You are inspecting the saved metadata example for 2021/22:225.

Inspect the document’s source, metadata and relationships

proposition

Public-sector data availability

identity
urn:se:itwn-id:ko:EPPDNDXGFB2TFRXCVN6S89GEYE
Status
beslutad
Issuer
Infrastrukturdepartementet
Created
2022-04-07
Local reference
H903225

Relations

härstammar från
använd i beslut

Note Cites SOU 2020:55 and diarienummer I2020/02346 in plain text. The chain is found by following the text’s own references.

The source stays. Its context remains traceable.
Compare metadata with source XML

Same document, two representations. XML retrieved 2026-09-26. The object is the previously saved example, not a new wrapper run. The original file is unchanged. The example code reads the equivalent JSON feed; XML shows the same source record.

Original metadata · H903225

Selected fields from /dokumentstatus/dokument. Select a field below to follow its mapping.

<dokument>
  <dok_id>H903225</dok_id>
  <titel>Den offentliga sektorns tillgängliggörande av data </titel>
  <organ>Infrastrukturdepartementet</organ>
  <datum>2022-04-07 00:00:00</datum>
  <doktyp>prop</doktyp>
  <status>Klar</status>
</dokument>
Show complete XML file

What does the wrapper do?

XML · dok_idH903225
Object · localRefH903225

The source identifier is preserved.

Added by the example: object identity, relationship labels and context. References can come from structured source fields or document-text searches; the relationship type is our mapping.

Ask the selected object

OBJECT VOICE · SCRIPTED EXAMPLE

Ask the object

Answers drawn from the selected object’s saved metadata and relationships. No AI or live verification is used.

Public-sector data availability

Recorded source information

Issuer: Infrastrukturdepartementet. Recorded document date: 2022-04-07. Local reference: H903225.

Inspect the source behind the answer

This example shows how an interface can explain the evidence. It sends no requests and records no new events.

DOCUMENT FLOW

From source to recipient

Your chain selection: 2021/22:225. The same bill follows all six stages. Your selected recipient view is retained as you move forwards and backwards.

Open the walkthrough: from source XML to a recipient view

H903225 · THE WHOLE DOCUMENT

Follow the complete feed through the flow

See exactly what is preserved, structured and passed on. Switch stages and recipient views while keeping the same source document.

Real source record · working demonstration projection · selected display rules are not Riksdagen’s conditions. All data is public on this teaching page; masking here is not access control.

Loading the complete feed and verifying the original file …

The same source, a changing understanding

A reference can persist while our assessment of it changes. New evidence can strengthen a connection. A challenge can reveal missing context. A correction can prompt a method’s reassessment.

We need to distinguish a source’s contents, assertions about it and what was recorded at different times. An object’s identity, a particular version and its representations are distinct; a matching identifier does not establish equivalence between representations.

TEACHING EXAMPLE · SIMULATED EVENTS

All objects, dates and events are fictional and entered in advance. No AI runs, no nodes exchange information and no permissions are enforced.

Observation recorded

A measurement is described in object EX-OBS-01. It concerns 10 January but is recorded on 12 January.

Assessment at the selected time: No connection to the method is yet described.

Original source

EX-OBS-01 · version 1

Observation: 10 January. Recorded: 12 January.

Later steps do not rewrite the original.

Described at the selected time

EX-OBS-01 · version 1

No later version is recorded.

A review flag does not automatically make the method wrong.

Show the complete prepared event list
  1. — Observation recorded

    A measurement is described in object EX-OBS-01. It concerns 10 January but is recorded on 12 January.

  2. — Connection proposed

    A reviewer proposes that the observation supports method EX-METOD-01. The reference and its asserting role are recorded in the scenario.

  3. — Context added

    Another reviewer notes that the measurement concerns a different location. The challenge becomes a separate contribution.

  4. — Source corrected

    The custodian describes a corrected measurement in version 2, valid from 19 January. The change is recorded on 20 January. Version 1 remains as earlier evidence in the example.

  5. — Method flagged for reassessment

    A reference from the method to version 1 makes the dependency visible. A responsible person needs to assess whether the method should change. The reviewer’s assignment has also ended; continued authority and visibility need separate review.

This example explains the model. Complete management of history and changing conditions across nodes remains to be developed.

Explore your own material ↗

The next person should be able to build on it

Consider a case officer who investigates a question and records an assessment. A colleague in another municipality finds it. With a Knowledge Object, the intention is that the colleague could also follow the sources, understand the local circumstances and see what needs to be assessed again.

The colleague’s correction or new experience can become a separate contribution linked to the source. Shared learning can grow while assessments remain local. The contribution, personal identity and authority to decide are separate questions. What may be shown can change over time.

This is a hypothetical use case. The examples show sources and relationships; full exchange between nodes and governance of rights over time remain to be built and tested.

DEEPER READING

Inspect the evidence or choose a new example

Explore evidence, changes and conditions in more depth. These teaching examples are separate and do not change the selected document or its flow.

Knowledge can remain useful as conditions change

A contribution is what someone adds: evidence, a correction or a method. Their identity, authority to act and any rights claims are separate questions. Tracing the origins of knowledge need not mean revealing every person behind it to everyone.

Consider a reviewer who contributes a correction and later leaves their role. The correction may remain relevant. Authority to make new changes ends with the mandate, while disclosure of personal information needs a separate decision. Withholding a name guarantees neither anonymity nor the termination of a valid rights claim.

This is a hypothetical case for the proposed architecture. The document flow above does not demonstrate automated lifecycle governance or enforcement of mandates and entitlements. Read the technical requirements ↗

Passage evidence and a separate permissions example

A separate walkthrough: two source-backed bill excerpts or a fictional water alert. This is not the next stage of the XML flow.

FOLLOW THE OBJECT

From document to Knowledge Object

See where the content lives, how a passage supports a relationship and what another node could discover. The object keeps its identity even when permitted views differ.

Source-backed excerpt · complete document at Riksdagen · no node runs here

H903225

Den offentliga sektorns tillgängliggörande av data

urn:se:itwn-id:ko:EPPDNDXGFB2TFRXCVN6S89GEYE

See the complete XML feed and all recipient views in the full flow above ↑

The complete bill is a representation held by Riksdagen. The older object file on this site contains metadata but no document body. Only a labelled excerpt from section 3 is shown here.

Representations

Complete document
data.riksdagen.se/dokument/H903225 ↗sourceRef · text/html · contentHash: null
Local excerpt
Two passages from section 3. An editorial selection, not the whole text.

3 Preparation of the matter · p. 14

Selected passage: Innovation genom information (SOU 2020:55)
Relation in the older manifest: härstammar från → SOU 2020:55
How it was found: document-text-pattern

The passage supports that the inquiry or consultation responses are mentioned. The relation name is a mapping in the earlier demonstrator, not a verbatim source claim. The text anchor belongs to the named source version; no byte hash has been computed.

The real source and earlier metadata record are separate from the illustrative representation. The synthetic record includes its entire fictional document. Its raw JSON is publicly downloadable for inspection: masking here illustrates protocol behaviour and does not protect real data. No button sends a request to an Intertween node.

See how a person and two agents receive different views ↗

Separate scenario: what happens when a shared method is corrected?

FOLLOW THE CHANGE

When a shared method changes

A fictional object is shared as a masked method. Then a section is corrected. Follow what the recipient, a dependent Knowledger and the event history need to show.

Scripted protocol scenario · no nodes or policy engines run · receipts are not signed

NODE A · LOCAL SOURCE

Source object @ 1

The second measurement was within the expected range. The cause of the first reading remains uncertain.

Representation
repr-complete-text-v1
Assertion
The repeat measurement was within range
State
asserted from source version 1

NODE B · RECIPIENT

Permitted view

No received view

KNOWLEDGER

Composed knowledge

Compare two possible immutable manifests. Choose how the member resolves; this does not modify the source object.

Manifest
intw:knowledger:fictional-town:review-methods:pinned
Member
sourceObject@1
Resolved member
sourceObject@1

Both variants currently resolve version 1.

What enters the history?

  1. observedsourceObject@1: source version 1 registered locally

Events are scripted. A real Relational Trace and impact handling for known recipients require implemented nodes, policy, exchange and evidence.

Earlier evidence: bill manifest, chain relationships and checks

The manifest, verbatim

This is what the bill looks like as a machine-readable JSON object, straight from the conformance harness output. This is the earlier metadata example, not the complete XML package in the document flow.

{
  "itwnId": "urn:se:itwn-id:ko:EPPDNDXGFB2TFRXCVN6S89GEYE",
  "objectType": "proposition",
  "title": "Den offentliga sektorns tillgängliggörande av data",
  "issuer": "Infrastrukturdepartementet",
  "responsibleAuthority": "Infrastrukturdepartementet",
  "created": "2022-04-07",
  "registered": "2022-04-07",
  "status": "beslutad",
  "version": "1",
  "localReferences": [
    { "organisation": "Sveriges riksdag", "identifier": "H903225",
      "role": "dok_id" },
    { "organisation": "Regeringskansliet", "identifier": "2021/22:225",
      "role": "propositionsnummer" }
  ],
  "contentHash": null,
  "accessPolicy": "offentlig",
  "retentionStatus": "bevaras",
  "relations": [
    { "type": "tillhör",
      "target": "urn:se:itwn-id:sp:FTN9X03NM64TJRCXX4K562WZHH" },
    { "type": "tillhör",
      "target": "urn:se:itwn-id:ar:DR8299AH44YWFQXBTGXYY3EAB1" },
    { "type": "härstammar från",
      "target": "urn:se:itwn-id:ko:NA0NT01S0HFVRQZRD3JWRBNBRD" },
    { "type": "använd i beslut",
      "target": "urn:se:itwn-id:ar:9RN3VB8VMH66CNMY2P3794CH2Z" }
  ],
  "validationStatus": "asserted-by-source",
  "source": "https://data.riksdagen.se/dokumentstatus/H903225",
  "note": "Hänvisar i klartext till SOU 2020:55 och diarienummer I2020/02346."
}

Validate the earlier metadata example →

All relations and how each one is known

Each relation states how it is known: from a structured field, from a pattern in the document text, or from an editorial decision by us.

Source assertionRelationHow it is known
bet. dokreferens [behandlar, prop]bygger påstructured-reference
bet. dokreferens [rskr]använd i beslutstructured-reference
prop. text: “SOU 2020:55”härstammar fråndocument-text-pattern
prop. text: “I2020/02346”använd i beslutdocument-text-pattern
SFS transitional clause: repeals 2010:566ersätterdocument-text-pattern
grouping under a samhällsprocesstillhörstructural
our decision, not a source claim

Riksdagen has no concept of a samhällsprocess. Grouping these objects under one is our own decision, and it is labelled as ours.

Checks of the earlier chain

MetricResult
Round-trip fidelityprecision 1.0, recall 1.0, f1 1.0 — 5 of 5 asserted relations reconstructed, 0 invented
Schema conformance105 objects, 0 missing required fields, 0 dangling edge targets, all identifiers unique
Ground truthRe-derived from the raw API independently of the mapper, so it cannot agree with itself
Relation vocabulary8 of 10 used; the two unused are named with the reason each is absent
Local identifier retention100% where the source publishes one, 0% where it does not

Where Swedish public sources publish a local identifier, it survives being wrapped. Where they do not, it is gone and cannot be recovered later.

Continue exploring

Continue from the example to the framework concepts, technical documentation or learning methods.