Skip to content
Public Framework

Layers

v1.0 · in consultation

Information (INF)

Layer INF of Public Framework Modelling Language 1.0 answers the question “With what information?”. This page describes the layer's concepts, how they relate, and its 17 element types.

Describes specification v1.0

What the layer describes

The INF layer answers the question “With what information?”. It describes information, its meaning and its governance, independently of the software that processes it. The logical data store (DataStore) used by software belongs to APP, and installed storage (StorageResource) belongs to RUN.

Concepts and how they relate

An information entity (InformationEntity) is a concept with its own meaning, independent of its representation in software. A dataset (Dataset) is an identifiable collection of related data. A distribution (Distribution) is the form in which the dataset is provided; it realises the dataset through the “realises” relationship (realisation).

A processing activity (ProcessingActivity) uses or transforms information for a declared purpose. As an element of INF, it links where needed to its legal basis through the “has legal basis” relationship (legalBasis). The target is a legal resource (LegalResource) or a legal provision (LegalProvision).

The other layers use information through the “accesses” relationship (access). Its source is a structure, a behaviour or a service, for example a procedure (Procedure) or a software system (SoftwareSystem). The target is information or a store, for example a dataset or a base registry (BaseRegistry), the authoritative source of information.

Element types

The layer has 17 element types, in these families: access (1), information (11), store (1), intent (4). Each type's own fields are listed under its definition; the fields common to every element are described under the core concepts.

  • InformationEntityInformation entity · information family

    A meaningful information concept independent of its software representation.

    Key attributes: coreVocabularyMappingstewardversionstatuslifecycleStatesourceReferencebusinessMeaningcimMappingmappingRationalesensitivity
  • DataStandardData standard · information family

    An agreed specification for describing or exchanging data.

    Key attributes: formatversionpublisher
  • CodeListCode list · information family

    A controlled set of codes and their meanings.

    Key attributes: authorityversion
  • DatasetDataset · information family

    An identifiable collection of related data.

    Key attributes: accessRightslicenceupdateFrequencyversionstatuslifecycleStatesourceReferencepurposerecordGranularitydataCategorytimeResolutiontimezonevaliditySemanticspublicationCadenceupdateModecorrectionPolicymaximumAgelateArrivalPolicyclassificationpermittedPurposeretentionvalidFromvalidToregionscarrieshasRepresentationderivesFrom
  • DistributionDistribution · information family

    An accessible representation or delivery form of a dataset.

    Key attributes: formataccessUrlmediaType
  • BaseRegistryBase registry · store family

    An authoritative register used as a trusted source of information.

    Key attributes: registerKindaccessConditions
  • QualityRuleQuality rule · intent family

    A condition used to assess information quality.

    Key attributes: dimensionthreshold
  • ProcessingActivityProcessing activity · information family

    An activity that uses or transforms information for a stated purpose.

    Key attributes: purposelawfulBasisretentionPerioddatasets
  • DataProductData product · information family

    Information packaged and managed for defined consumers and uses.

    Key attributes: versionstatuslifecycleStatesourceReferencepurposetargetAudiencesupportContactpackages
  • DataRepresentationData representation · information family

    A particular structured representation of information.

    Key attributes: versionstatuslifecycleStatesourceReferenceaudiencenamingPatterndatasetconformsTo
  • DataSchemaData schema · information family

    A specification of the structure and constraints of represented data.

    Key attributes: versionstatuslifecycleStatesourceReferenceschemaLanguageschemaReferencedescribes
  • FormatProfileFormat profile · information family

    A profile describing the conventions of a data format.

    Key attributes: versionstatuslifecycleStatesourceReferencestandardBasiscontentSummaryformatmediaTypefileExtensionencodingpackagingcompressionschemaDialectcsvDelimitercsvQuotenullMarkerdecimalConventiondateConventionxmlNamespacexmlRootElementsheetNamescolumnMappingformulaPolicylogicalTypesschemaReferencecsvHeaderRowsheaderPositionusesSchemaincludes
  • InformationDomainInformation domain · information family

    A subject-oriented grouping of related information concepts.

    Key attributes: versionstatuslifecycleStatesourceReferencepurposegroups
  • QualityGateQuality gate · intent family

    A point where information is checked against defined quality conditions.

    Key attributes: versionstatuslifecycleStatesourceReferencepositionfallbackguardsapplies
  • ValidationRuleValidation rule · intent family

    A specific check applied to information or its representation.

    Key attributes: versionstatuslifecycleStatesourceReferenceexpressionlanguageseverityqocdcReferencevalidatesrealises
  • ValidationRuleSetValidation rule set · intent family

    A named collection of related information-validation rules.

    Key attributes: versionstatuslifecycleStatesourceReferenceincludes
  • DataInterfaceData interface · access family

    An interface defining information exchanged across a boundary.

    Key attributes: regionhorizonProfiledirectioncontractboundary1boundary2

In the “Family support benefit” example

Figure 4.4 (page 28) shows the INF layer in the example. The procedure “Assess benefit application”, from ORG, accesses the dataset “Benefit case records”. The dataset contains personal data, and access to it is restricted.

The layer's other links are fields and are not shown in the figure. The dataset carries the information entity “Benefit application facts”. It has the data representation (DataRepresentation) “Benefit case JSON representation”, which conforms to the format profile (FormatProfile) “Benefit case JSON profile”. The processing activity “Benefit case assessment” processes the dataset to determine eligibility.

Was this page helpful?