Skip to content

UC-01: Titleblock-Based Drawing Search

Methodology: LOT (Linked Open Terms) · Use Case ID: UC-01 · Version: 0.21 (draft) — see §9 Version History


1. Use Case

Field Content
ID UC-01
Title Titleblock-Based Drawing Search
Statement As an engineer, I want to search and filter drawings based on the information in the titleblock.
Primary Actor Engineer
Goal Retrieve a set of drawing sheets matching one or more titleblock metadata criteria, individually or in combination.

Terminology note: Throughout this ORSD, the user-facing term "drawing" refers to a metadata:DrawingSheet — the top-level, titleblock-bearing, searchable unit in the existing ontology. A sheet contains one or more Layouts, each of which carries its content type (Plan / Section / Detail / …) and discipline classification.


2. Information Needs Analysis

2.1 Entities

Things that exist independently and will become OWL Classes.

Entity Module Action Rationale
DrawingSheet adiro_drawing_metadata REUSE The primary object being searched. UC-01 "Drawing" maps here.
Layout adiro_drawing_metadata REUSE A view region within a DrawingSheet; carries discipline and content-type classification.
LayoutContentType adiro_drawing_metadata REUSE View type (Plan / Section / Elevation / Detail / Table / Perspective).
DrawingRevision adiro_drawing_metadata NEW Titleblock data (status, date, persons) changes per revision.
Project adiro_drawing_metadata NEW Drawings are grouped under a project.
Person adiro_provenance NEW Authors, checkers, and approvers appear in the titleblock. (Moved from adiro_drawing_metadata in v0.9.)
DrawingFile adiro_provenance NEW The file a drawing is stored in: a reference to a document, identified by its content hash. (Added in v0.9.)
FilePage adiro_provenance NEW One page of a file, counted from 1; the drawing is on a page, not on a file. (Added in v0.9.)
Configuration adiro_provenance NEW The settings a step of an extraction used (a prompt, rendering settings), kept as text. (Added in v0.17.)
TextReading adiro_provenance NEW The text a step read from a title block or a whole page, or why it read none. (Added in v0.18.)
StepKind adiro_provenance NEW What a step of an extraction did: region detection, text recognition or field extraction. (Added in v0.18.)
Discipline adiro_domain_common REUSE Existing class hierarchy (Structural, MEP, Architectural, …).
StatusCode adiro_drawing_metadata NEW Approval state (IFC, IFR, AFC…) expressed as a controlled vocabulary.
DrawingPackage adiro_drawing_metadata NEW Drawings are grouped into volumes or packages within a project.

Design note — DrawingSheet vs Layout: A DrawingSheet may contain multiple Layouts, each with its own LayoutContentType and Discipline. Queries for "Structural Plan drawings" filter for sheets containing at least one Layout whose content type is Plan and whose discipline is (a subclass of) Structural.

Design note — Titleblock as visual region vs titleblock data: The existing metadata:Titleblock class models the visual region on a sheet (for CV annotation). The information conventionally found inside it (drawingIdentifier, drawingTitle, …) is attached as datatype properties directly on DrawingSheet. The two layers coexist independently: a sheet has a drawing number whether or not its visual Titleblock region has been bounded in annotation.

Design note — :Metadata → :MetadataContainer: The existing :Metadata class has been renamed to :MetadataContainer (team decision). It is the parent of Titleblock, RevisionTable, Legend, and Note — i.e. it models visual supporting regions, not semantic metadata. The rename avoids confusion with UC-01's datatype properties (drawingIdentifier, drawingTitle, etc.) on DrawingSheet.

Design note — DrawingType deprecated: UC-01 v0.2 introduced :DrawingType (Plan, Section, Elevation, Detail, Schedule). This is the same axis as metadata:LayoutContentType (Plan, Section, Elevation, Detail, Table, Perspective). "Schedule" maps to Table. DrawingType is removed in v0.3 — LayoutContentType is reused.

Design note — Discipline reuse: UC-01 v0.2 introduced :Discipline plus a :disciplineCode string property. The existing dcommon:Discipline is already a full class hierarchy (Structural, MEP > Mechanical / Electrical > Lighting / Plumbing, Architectural > Facade / FireLifeSafety, Masterplan). v0.3 reuses it and drops :disciplineCode — discipline filtering uses rdf:type checks against the class hierarchy (e.g. ?disc a dcommon:MEP), which automatically rolls up sub-disciplines via rdfs:subClassOf reasoning.

Design note — curated values vs extracted assertions: UC-01 attaches title-block information as datatype properties directly on DrawingSheet (drawingIdentifier, drawingTitle, …). That remains correct for a validated value. A second, parallel path exists for values that have been machine-extracted and not yet validated: an aprov:FieldAssertion reifies the claim - what was read, from which region (assertedBy), by what (hasInferenceMeta), with what confidence, and with the caption exactly as printed (capturedCaption) - bound to a field kind (aprov:FieldKind) in the TitleblockFieldScheme. aprov:mapsToFieldProperty names the UC-01 property a validated assertion is promoted to, and that property's domain is the class of the subject the value is about (DrawingSheet, Titleblock, Project, …): a region and a field kind meet only through assertions. The two coexist: UC-01's properties are the query surface, the assertion layer is the extraction and provenance record. A value moves from the assertion to the direct property when its assertion is accepted (aprov:hasAcceptance Accepted), by a pipeline rule (a confidence threshold, named by aprov:acceptedUnder) or by a person, and the acceptance records who and when (acceptedBy, acceptedAt). The assertions are never deleted, and the direct properties stay as the permanent query surface of accepted values (#85). When a search finds no value, the assertion carries an outcome instead (aprov:hasOutcome: Empty, Illegible, NotPrinted, NotFound, Failed), and is never promoted. (Added in v0.4; amended in v0.10, v0.18 and v0.21.)

The promotion is a query that tooling runs on accepted assertions, not an inference. Each accepted assertion that has a value, and that no accepted assertion supersedes, directly or through a chain of corrections, gives one direct statement on its subject, with the property its field kind maps to (aprov:mapsToFieldProperty). (Amended in v0.16.)

PREFIX aprov: <https://w3id.org/adiro/adiro_provenance#>

# Promotion: the direct statements that accepted assertions give
CONSTRUCT { ?subject ?property ?value }
WHERE {
  ?assertion a aprov:FieldAssertion ;
             aprov:assertedAbout   ?subject ;
             aprov:assertsFieldKind ?kind ;
             aprov:hasAcceptance   aprov:Accepted .
  ?kind aprov:mapsToFieldProperty ?property .
  { ?assertion aprov:hasLiteralValue ?value } UNION { ?assertion aprov:hasValueEntity ?value }
  FILTER NOT EXISTS { ?newer aprov:supersedes+ ?assertion ; aprov:hasAcceptance aprov:Accepted }
}

An assertion that is pending, rejected, outcome-only (NotPrinted, Empty, Illegible, NotFound) or superseded by an accepted assertion gives nothing. This holds for data that passes assertions.shacl.ttl, which allows an assertion one acceptance status and at most one outcome: the query itself promotes an assertion that carries Accepted among several statuses. The query reads the field-kind concepts too, so it runs over the data together with the ontology. (Added in v0.11, amended in v0.14.)

Supersession takes effect when the superseding assertion is accepted. An assertion that supersedes another proposes to replace it; until it is accepted, the earlier one stays in force, so an unreviewed re-extraction does not remove a reviewed value. A person's correction is an assertion that person accepts, so it takes effect at once. A value known to be wrong is withdrawn by rejecting its own assertion, whether or not a replacement is ready. An accepted assertion withdraws every assertion it supersedes, directly or through a chain, even when an assertion in between was never accepted, so a chain gives at most one value. Every assertion stays as a record, and no timestamp decides. (Added in v0.16.)

A, the earlier assertion B, which supersedes A Promoted
Accepted, with a value Pending A's value
Accepted, with a value Rejected A's value
Accepted, with a value Accepted, with a value B's value
Accepted, with a value Accepted, outcome-only (such as NotPrinted) nothing
Rejected Pending nothing

The query gives the whole current set of direct statements. A store that keeps them replaces the statements it derived before with this set: adding the new set to the old one would leave a withdrawn value in place.

Design note — Person vs Role: Person models what an individual is, not the role they play. Roles (Author, Checker, Approver) are expressed as distinct Object Properties, not as subclasses of Person. Each applies to a DrawingSheet (the person the drawing names, for example the title block's "drawn by") and to a DrawingRevision (the person who made, checked or approved that revision, who can differ from the one named for the drawing). This keeps Person reusable across roles. A drawing that records no author of its own is read as authored by the authors of its revisions (the path metadata:isAuthoredBy|metadata:hasRevision/metadata:isAuthoredBy); a drawing that records its own author keeps just that author, so this is a reading convention and not an OWL entailment. It applies to the author only. (Amended in v0.8.)

2.2 Attributes — Datatype Properties

Characteristics of a single entity. Datatype properties on DrawingSheet are attached directly — no intermediate "metadata container" entity.

Attribute Entity Module Action Expected Type Notes
drawingIdentifier DrawingSheet adiro_drawing_metadata NEW xsd:string Also known as "drawing number".
drawingTitle DrawingSheet adiro_drawing_metadata NEW xsd:string
hasScale DrawingSheet, Layout adiro_drawing_metadata NEW xsd:string The general scale property; drawingScale and layoutScale are its sub-properties. With sub-property entailment a query on hasScale returns values recorded with either; without it, a sheet's scale is read with the path metadata:hasScale\|metadata:drawingScale and a layout's with metadata:hasScale\|metadata:layoutScale. (Amended in v0.7.)
drawingScale DrawingSheet adiro_drawing_metadata NEW xsd:string The scale of the sheet as a whole: most often printed in the title block, also in general notes or other areas outside any layout. Never copied from a layout. Sub-property of hasScale. (Added in v0.7.)
layoutScale Layout adiro_drawing_metadata NEW xsd:string The scale printed in a layout's own caption (or 'NTS' / 'As shown', verbatim); more specific than drawingScale; left empty when the layout prints none. Sub-property of hasScale. (Added in v0.7.)
sheetSize DrawingSheet adiro_drawing_metadata NEW xsd:string Named for the sheet of paper, which has a size; also known as "drawing size". (Noted in v0.7.)
revisionCode DrawingRevision adiro_drawing_metadata NEW xsd:string
issueDate DrawingSheet or DrawingRevision adiro_drawing_metadata NEW xsd:date The date a drawing, or a revision of it, was issued; the title block's date is the drawing's, and "date authored" is the same property. (Amended in v0.8.)
personName Person adiro_drawing_metadata NEW xsd:string
projectName Project adiro_drawing_metadata NEW xsd:string
projectNumber Project adiro_drawing_metadata NEW xsd:string
packageName DrawingPackage adiro_drawing_metadata NEW xsd:string
statusLabel StatusCode adiro_drawing_metadata NEW xsd:string

Where a scale is printed, and which property records it

Where the scale is printed Recorded as Note
In the title block (the "Scale" cell), the usual place drawingScale on the DrawingSheet The sheet's nominal scale.
In a general note or another area of the drawing outside the title block and outside any layout ("all drawings 1:50 unless noted") drawingScale on the DrawingSheet Whether such a scale applies to the whole sheet is judged from its context when the value is extracted; that is a matter for extraction, not for the ontology.
In a layout's own caption layoutScale on that Layout More specific than the sheet's, and may differ from it (a 1:500 plan on a 1:50 sheet).
In the caption of the only layout detected on the sheet layoutScale on that Layout, and nothing on the sheet Not repeated as drawingScale. A scale belongs to a drawing view: if more layouts are detected later, a drawingScale copied from the first would no longer be true of the sheet.
A layout printing "NTS" or "As shown" instead of a ratio layoutScale with that text, verbatim Tells a layout drawn out of scale apart from one that prints no scale.
A layout printing no scale nothing layoutScale stays empty; the sheet's scale is not written into it.

What scale applies to a layout is answered by a query (CQ 1.4), not by a stored value: the layout's own layoutScale if it has one, otherwise the sheet's scale, reported as "assumed from sheet". The fallback is an assumption (a scale can be missing by mistake), so it is never asserted as a layoutScale, which would present an assumption as a printed value. "No scale" (CQ 1.5, CQ 1.6) is a closed-world check: OWL reads a missing value as "not stated", never as an error, so a someValuesFrom restriction would only make a reasoner infer that a scale exists. Such checks are queries, or validation shapes in the wider ABox validation work (#22).

2.3 Relations — Object Properties

Links between two entities. New properties are wired into the existing generic top-level properties via rdfs:subPropertyOf.

Relation Domain Range Module Action subPropertyOf
contains (sheet) DrawingSheet Layout (1..*) adiro_drawing_metadata REUSE —
hasProperty Layout LayoutContentType adiro_drawing_metadata REUSE —
hasDiscipline ⚠️ Layout Discipline (min 1) adiro_domain_common REUSE¹ —
hasRevision DrawingSheet DrawingRevision adiro_drawing_metadata NEW metadata:contains
belongsToProject DrawingSheet Project adiro_drawing_metadata NEW (top-level)
assertsProject Titleblock Project adiro_drawing_metadata NEW (top-level)
belongsToPackage DrawingSheet DrawingPackage adiro_drawing_metadata NEW (top-level)
assertsPackage Titleblock DrawingPackage adiro_drawing_metadata NEW (top-level)
isAuthoredBy DrawingSheet or DrawingRevision Person adiro_drawing_metadata NEW (top-level)
isCheckedBy DrawingSheet or DrawingRevision Person adiro_drawing_metadata NEW (top-level)
isApprovedBy DrawingSheet or DrawingRevision Person adiro_drawing_metadata NEW (top-level)
assertsRevision RevisionTable DrawingRevision adiro_drawing_metadata NEW (top-level)
isOnPage DrawingSheet FilePage adiro_drawing_metadata NEW (top-level)
belongsToFile FilePage DrawingFile adiro_provenance NEW (top-level)
dcterms:isPartOf InferenceMeta (a step) prov:Activity (a run) adiro_provenance (typing stub) NEW (external) (Added in v0.17.)
isReadingOf TextReading Titleblock or FilePage adiro_provenance NEW (top-level) (Added in v0.18.)
coversRegion CoordinateFrame (a crop) BoundingBox adiro_geometry NEW (top-level) (Added in v0.19.)
imageOf DrawingFile (a kept image) CoordinateFrame adiro_geometry NEW (top-level) (Added in v0.19.)
hasStatusCode DrawingRevision StatusCode adiro_drawing_metadata NEW metadata:hasProperty

¹ ⚠️ Open issue (G5): dcommon:hasDiscipline currently has rdfs:domain metadata:LayoutContentType. v0.3 proposes moving the domain to metadata:Layout (along with the min 1 cardinality restriction). Discipline characterises the layout itself, not its content type — and the two are orthogonal axes (see design note below). Pending @alelom / @m-asakihattori sign-off.

Design note — two orthogonal axes on Layout:

Layout
  ├── hasProperty   → LayoutContentType  (exactly 1: Plan / Section / Detail / …)
  └── hasDiscipline → Discipline         (min 1: Structural / Facade / MEP / …)

Content type describes the view nature; discipline describes the engineering domain. A Layout carries one independent value on each axis.


3. Functional Requirements

Each FR describes one representational capability the ontology must have, in implementation-neutral language.

Obligation levels: MUST = mandatory for current scope; SHOULD = important but deferrable; MAY = optional extension.


FR 1 — Drawing Identity Fields

The ontology MUST represent the core identity fields of a drawing sheet — drawing number, title, scale, and sheet size — such that sheets can be retrieved and distinguished by these fields.

  • Source: UC-01
  • Derived terms: metadata:DrawingSheet (REUSE), metadata:drawingIdentifier, metadata:drawingTitle, metadata:hasScale, metadata:drawingScale, metadata:sheetSize (NEW datatype properties on DrawingSheet); metadata:layoutScale (NEW, on Layout). drawingScale and layoutScale are sub-properties of hasScale. (Amended in v0.7.)

FR 2 — Project Membership

The ontology MUST represent the relationship between a drawing sheet and the project it belongs to, such that all sheets within a given project can be retrieved as a set.

  • Source: UC-01
  • Derived terms: metadata:Project (NEW), metadata:belongsToProject (NEW), metadata:assertsProject (NEW, from a Titleblock to the project it names), metadata:projectName, metadata:projectNumber (NEW datatype properties on Project)

FR 3 — Revision History and Temporal Metadata

The ontology MUST represent multiple revisions of the same drawing sheet as distinct entities, each carrying a revision code, issue date, and status code, such that both the current state and the full revision history of a sheet can be queried.

  • Source: UC-01
  • Derived terms: metadata:DrawingRevision (NEW), metadata:hasRevision (NEW, subPropertyOf metadata:contains), metadata:assertsRevision (NEW, from a RevisionTable to each revision it lists), metadata:revisionCode, metadata:issueDate (NEW)

FR 4 — Role-Differentiated Person Attribution

The ontology MUST distinguish between the roles of Author, Checker, and Approver as separate relationships between a person and a drawing, and between a person and a revision of it, such that drawings can be filtered by a specific person in a specific role, and a drawing with no recorded person in a required role can be found.

  • Source: UC-01
  • Derived terms: metadata:Person (NEW), metadata:isAuthoredBy, metadata:isCheckedBy, metadata:isApprovedBy (NEW, top-level), metadata:personName (NEW)

Design note — inverse properties: ADIRO declares no named inverse properties and no owl:inverseOf axioms. Only forward properties are modelled; reverse navigation uses the SPARQL inverse path, e.g. ?rev ^metadata:hasRevision ?sheet. Decided project-wide in #21. (Changed in v0.4.)


FR 5 — Discipline Classification

The ontology MUST support filtering drawing sheets by engineering discipline, reusing the existing dcommon:Discipline class hierarchy (Structural, MEP, Architectural, Facade, FireLifeSafety, Masterplan, plus their sub-disciplines), attached at the Layout level via dcommon:hasDiscipline.

  • Source: UC-01
  • Derived terms: dcommon:Discipline (REUSE), dcommon:hasDiscipline (REUSE — domain proposed to move from LayoutContentType to Layout, see G5)
  • Note: disciplineCode from v0.2 is removed — filtering uses rdf:type against the class hierarchy, which gives automatic sub-discipline rollup (querying dcommon:MEP auto-includes Mechanical, Electrical, Plumbing).
  • Note: Civil is to be added to dcommon:Discipline as a direct subclass of Discipline (confirmed by team discussion).

FR 6 — Layout Content Type Classification

The ontology MUST support filtering drawing sheets by view type, reusing the existing metadata:LayoutContentType controlled vocabulary (Plan, Section, Elevation, Detail, Table, Perspective), attached at the Layout level via metadata:hasProperty.

  • Source: UC-01
  • Derived terms: metadata:LayoutContentType (REUSE), metadata:Layout (REUSE), metadata:hasProperty (REUSE)
  • Note: UC-01 v0.2's :DrawingType (with subclasses Plan / Section / Elevation / Detail / Schedule) is removed — metadata:LayoutContentType already provides this. "Schedule" maps to the existing metadata:Table subclass.

FR 7 — Issue Status

The ontology MUST represent the approval status of each drawing revision using a controlled vocabulary of status codes, such that sheets can be filtered by their current or historical approval state.

  • Source: UC-01
  • Derived terms: metadata:StatusCode (NEW), metadata:hasStatusCode (NEW, subPropertyOf metadata:hasProperty), metadata:statusLabel (NEW)

FR 8 — Package / Volume Grouping — Lowest priority

The ontology SHOULD represent the grouping of drawing sheets into packages or volumes within a project, such that project-scoped and package-scoped searches can both be supported.

  • Source: UC-01
  • Derived terms: metadata:DrawingPackage (NEW), metadata:belongsToPackage (NEW), metadata:assertsPackage (NEW, from a Titleblock to the package it names, when it names one), metadata:packageName (NEW)

FR 9 — Source File and Page

The ontology MUST say in which file, and on which page of it, a drawing is stored, identify and locate that file, and say where the file was obtained from, such that a drawing can be traced to its source, the drawings of a file can be listed, and a file can be found again. (Amended in v0.15.)

  • Source: UC-01 (and every use case that must return to the source of an extraction)
  • Derived terms: aprov:DrawingFile (NEW), aprov:FilePage (NEW), metadata:isOnPage (NEW), aprov:belongsToFile (NEW), aprov:pageNumber (NEW, from 1); the description of a file: aprov:fileName, aprov:storageLocation, aprov:contentHash and aprov:hashAlgorithm, aprov:mediaType, aprov:fileCreatedAt, aprov:fileModifiedAt, aprov:fileCreatedBy, aprov:fileModifiedBy, aprov:pageCount, aprov:fileSize (all NEW); where it was obtained from: aprov:sourceLocation, aprov:sourcePage (NEW in v0.15), with prov:wasDerivedFrom from a file made from another; and of a page: aprov:displayWidthPt, aprov:displayHeightPt, aprov:pdfRotationDeg (moved from the coordinate frame)

Design note — drawing, file, page. A PDF holds many drawings and one drawing can exist in several files, so a drawing is linked to the page it is on (isOnPage), and the page to its file (belongsToFile). The coordinate frame of adiro_geometry reads a page in one convention (describesPage). The measured size of a page is not sheetSize, which is the paper format the drawing is meant for. See the file a drawing is stored in. (Added in v0.9.)


FR 10 — How a Value Was Produced (Added in v0.17.)

The ontology MUST say which run of an extraction produced a recorded value, which step of that run and which model, with which configuration, what image of the page it saw (its resolution, and the region when it saw only part of the page), and which versions of the ontology the run used, such that a value can be traced to the process that produced it and two runs can be compared. (Amended in v0.19.)

  • Source: UC-01 (every value read from a title block is produced by an extraction, and a reviewer must be able to see how)
  • Derived terms: aprov:InferenceMeta (REUSE: a step), aprov:inferredWith (REUSE: the model of a step), aprov:Configuration and aprov:configurationContent (NEW), with the typing stubs dcterms:isPartOf (NEW: a step is part of its run), prov:startedAtTime (NEW: when a run started) and prov:used (REUSE: the configuration and the frame a step used, and the ontology versions a run used); geom:CoordinateFrame (REUSE: the image a step saw), geom:resolutionDpi, geom:coversRegion and geom:imageOf (NEW)

Design note — runs and steps. An extraction run is a prov:Activity. Each of its steps (detecting the title block, reading its text, extracting the fields) is an InferenceMeta with the model it used (inferredWith), and is part of the run (dcterms:isPartOf). A value's assertion points to the step that produced it (hasInferenceMeta). What the step used besides its model is a Configuration (prov:used): a prompt, rendering settings, size limits, kept as text whose format ADIRO does not model, with no credentials in it. A configuration is identified by its content, so one used on every page of a run is one individual. The recommended IRI is built from a hash of the content: the SHA-256 of the UTF-8 bytes of configurationContent exactly as recorded, with no normalisation, in lowercase hexadecimal, appended to the producer's own namespace (for example <producer namespace>/configuration/sha256-9f2c…). So that the same configuration gives the same text, and the same IRI, whichever producer writes it, the producer writes the text with \n line endings and no trailing newline, and writes settings as JSON with sorted keys and no insignificant whitespace. The hash is not recorded: the content is, and anyone can compute it again. Where a configuration varies from page to page, the InferenceMeta of that page records it, so one step of a run can be several InferenceMeta with the same model; two runs are compared by run and model, not by the IRI of a step. The run records the ADIRO versions it used as prov:used their version IRIs (for example <https://w3id.org/adiro/adiro_provenance/2.1.0>), written in that form, which is how a query tells them from anything else the run used. The resolution a page was rendered at is not a configuration: coordinates depend on it, so it is recorded on the coordinate frame it gives. Every image a step feeds to its model is a pixel CoordinateFrame of the page with its resolution (resolutionDpi), and a crop is a frame limited to a region (coversRegion, a BoundingBox in another frame of the page); the step records the frame it used (prov:used), so the data says what each model saw without the image being kept. Between a frame and the page there is only a uniform scale, so no transform is recorded (#93 holds the general case). An image that is kept, for a viewer, is a DrawingFile that is an image of its frame (imageOf), with its contentHash, mediaType and a storageLocation that may be relative to the root of the dataset. (Amended in v0.19.) UC-03's provenance profile (#96) uses the same pattern. (Added in v0.17.)


FR 11 — Text Read from a Drawing (Added in v0.18)

The ontology MUST hold the text an extraction read from a title block and from a whole page, with its language when it is known and whether or not any of it was read as a field, and why none was read (empty, illegible, or a step that failed, with its error); and it MUST say what kind of step each step of a run was, such that a drawing can be found by any text of its title block, and the pages a run processed, and those on which it detected no title block, can be listed.

  • Source: UC-01 (a drawing is searched for by any word of its title block, not only by the fields read from it; a reviewer checks what a run covered)
  • Derived terms: aprov:TextReading, aprov:isReadingOf, aprov:readText, aprov:hasReadingOutcome, aprov:errorMessage, aprov:StepKind (RegionDetection, TextRecognition, FieldExtraction) with aprov:hasStepKind, and the outcome value aprov:Failed (all NEW)

Design note — readings and coverage. A TextReading is an InferredEntity, so each has the step that produced it, and two runs that read the same title block keep two readings; the latest is the one whose run started last. It reads one thing (isReadingOf): a Titleblock, or a whole FilePage. Its text is readText, with the language as the literal's language tag ("Erdgeschoss"@de) when it is known. A reading that read nothing has one outcome instead: Empty, Illegible, or Failed with its errorMessage; Failed is also an outcome of a field assertion. A step that failed before producing anything records its errorMessage on itself, so a detection that timed out is not read as a page with no title block. The latest reading of a target is the latest, whatever its outcome: a later failed reading hides an earlier text in CQ 11.2, which answers what the latest run read, while CQ 11.1 still finds the earlier text. A run with no recorded start counts as the oldest. The outcome of a reading is a property of its own (hasReadingOutcome), not hasOutcome, whose domain is FieldAssertion: widening that domain would change what an existing property implies, and a reading is not a claim about a field. Every step says what kind of step it is (hasStepKind), so a step that found nothing is still known for what it looked for: "no title block detected" needs no term of its own, it is a page that a region detection that did not fail used, with no title block on it; "not processed" is a page no step used. (Added in v0.18.)


4. Competency Questions

CQs are grouped by the FR they validate. Each must be translatable directly into a SPARQL query against the term inventory above.

CQ Group 1 — Drawing Identity (validates FR 1)

ID Competency Question
CQ 1.1 What drawing sheets have a drawing number beginning with "ST-"?
CQ 1.2 What is the title of the sheet with drawing number "ST-101"?
CQ 1.3 What drawing sheets are drawn at scale 1:50? (Only sheets with a sheet-level scale are returned; a sheet whose only scale is in its single layout's caption is not.)
CQ 1.4 What scale applies to this layout: its own, or otherwise its sheet's?
CQ 1.5 Which drawing sheets state no scale at all?
CQ 1.6 Which layouts have no scale of their own and sit on a sheet with no scale, so that their scale cannot be determined?
CQ 1.7 Which layouts are drawn at a different scale from their sheet?

CQ Group 2 — Project Membership (validates FR 2)

ID Competency Question
CQ 2.1 What drawing sheets belong to project "HS 2-N 400"?
CQ 2.2 How many drawing sheets are currently registered under project "X"?
CQ 2.3 Which project does the title block of drawing "ST-101" name? (Added in v0.8.)
CQ 2.4 Which drawings are filed under a project other than the one their title block names? (Added in v0.8.)

CQ 2.4 as a query (assertsProject is the title block's claim, belongsToProject the filing):

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 2.4: the drawings filed under another project than their title block names
SELECT ?drawing ?named ?filed WHERE {
  ?titleblock a metadata:Titleblock ;
              metadata:assertsMetadataFor ?drawing ;
              metadata:assertsProject     ?named .
  ?drawing metadata:belongsToProject ?filed .
  FILTER (?named != ?filed)
}

CQ Group 3 — Revision History (validates FR 3)

ID Competency Question
CQ 3.1 What is the latest revision code of the sheet with drawing number "ST-101"?
CQ 3.2 What sheets were issued after 1 January 2024?
CQ 3.3 How many revisions has sheet "ST-101" gone through, and what were their issue dates?
CQ 3.4 From which revision table was revision "B" of drawing "ST-101" read? (Added in v0.8.)

CQ Group 4 — Role-Differentiated Persons (validates FR 4)

ID Competency Question
CQ 4.1 What sheets were authored by "J. Smith"?
CQ 4.2 What sheets were checked by "A. Chen"?
CQ 4.3 For sheet "ST-101 Rev C", who was the approving authority?
CQ 4.4 Which drawings have no recorded author, neither their own nor a revision's? (Added in v0.8.)
CQ 4.5 Which drawings have no recorded checker, or no recorded approver? (Added in v0.8.)
CQ 4.6 For each drawing with no recorded author, why: not printed, empty, illegible, not found, failed, awaiting acceptance, rejected, accepted and not yet promoted, or recorded with no value? (Added in v0.10, amended in v0.13 and v0.18.)

CQ 3.4 and CQ 4.4 as queries (CQ 4.5 is the same pattern with isCheckedBy or isApprovedBy alone, without the path through the revisions, which is for the author only):

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 3.4: the table a revision was read from
SELECT ?table WHERE {
  ?table a metadata:RevisionTable ;
         metadata:assertsRevision ?revision .
  ?revision metadata:revisionCode "B" .
}
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 4.4: the drawings with no recorded author (a revision's author counts when the drawing records none)
SELECT ?drawing WHERE {
  ?drawing a metadata:DrawingSheet .
  FILTER NOT EXISTS { ?drawing metadata:isAuthoredBy|(metadata:hasRevision/metadata:isAuthoredBy) ?person }
}

A drawing must have an author; whether it was checked or approved varies, so CQ 4.5 is a plain query and not a check. CQ 4.4 is a closed-world check: the ontology cannot state "every drawing has an author" (an OWL cardinality would infer an author, not report its absence), so the same rule is also a data-validation shape (#179). The query lists the drawings with no recorded person; it cannot say whether the extraction missed the author or the drawing names none; CQ 4.6 does.

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>

# CQ 4.6: why a drawing has no recorded author, one row per assertion about it or one of its revisions
SELECT ?drawing ?subject ?assertion ?value ?outcome ?acceptance ?reason WHERE {
  ?drawing a metadata:DrawingSheet .
  FILTER NOT EXISTS { ?drawing metadata:isAuthoredBy|(metadata:hasRevision/metadata:isAuthoredBy) ?person }
  OPTIONAL {
    ?drawing (metadata:hasRevision)? ?subject .
    ?assertion aprov:assertedAbout ?subject ; aprov:assertsFieldKind metadata:DrawnByField .
    FILTER NOT EXISTS { ?newer aprov:supersedes+ ?assertion ; aprov:hasAcceptance aprov:Accepted }
    OPTIONAL { ?assertion aprov:hasLiteralValue|aprov:hasValueEntity ?value }
    OPTIONAL { ?assertion aprov:hasOutcome ?o }
    OPTIONAL { ?assertion aprov:hasAcceptance ?s }
    BIND (STRAFTER(STR(?o), "#") AS ?outcome)
    BIND (STRAFTER(STR(COALESCE(?s, aprov:Pending)), "#") AS ?acceptance)
  }
  BIND (IF(!BOUND(?assertion), "NotProcessed",
        IF(?acceptance = "Rejected", "Rejected",
        IF(BOUND(?outcome), ?outcome,
        IF(!BOUND(?value), "NoValue",
        IF(?acceptance = "Accepted", "AcceptedNotPromoted", "Pending"))))) AS ?reason)
}

The query reads the assertions about the drawing and about each of its revisions, following the reading convention of CQ 4.4, and gives one row per assertion, with its subject, so the causes of several revisions stay apart. An assertion has one value or one outcome, and one acceptance; one that records two (malformed data) gives a row for each, so the disagreement is visible. An assertion superseded by an accepted one is not read, as in the promotion; one superseded only by a pending or rejected assertion is still in force and has its row. The acceptance and the outcome are separate columns; an assertion with no acceptance recorded is Pending. The reason:

  • NotPrinted is a defect of the drawing; NotFound and Failed (a step that did not complete) are retried; Empty and Illegible are reviewed. The acceptance column says whether that finding was accepted or still awaits review.
  • Pending is a value found and awaiting acceptance.
  • Rejected is an assertion a person or a rule rejected; its value or outcome is in its columns for inspection, and it is neither a finding nor awaiting review.
  • AcceptedNotPromoted is an accepted value that the promotion has not yet turned into isAuthoredBy.
  • NoValue is an assertion with neither a value nor an outcome (malformed data): nothing can be promoted from it, so it is corrected, not awaited.
  • NotProcessed means no assertion about the author of the drawing or its revisions exists, so the field was not looked at.

(Amended in v0.13, v0.16 and v0.18.)

CQ Group 5 — Discipline (validates FR 5)

ID Competency Question
CQ 5.1 What sheets contain at least one Layout classified under the Structural discipline?
CQ 5.2 What disciplines are represented across the Layouts of project "X"?

CQ Group 6 — Layout Content Type (validates FR 6)

ID Competency Question
CQ 6.1 What sheets contain a Layout of content type Section?
CQ 6.2 What content types are used across the Layouts of project "X"?

CQ Group 7 — Issue Status (validates FR 7)

ID Competency Question
CQ 7.1 What sheets currently carry the status "Issued for Construction"?
CQ 7.2 Which sheets changed from status "Issued for Review" to "Approved for Construction" across revisions?

CQ Group 8 — Package Grouping (validates FR 8)

ID Competency Question
CQ 8.1 What sheets belong to package "Volume 3"?
CQ 8.2 Which sheets in package "Volume 3" still have status "Issued for Comment"?
CQ 8.3 Which package does the title block of drawing "ST-101" name, if it names one? (Added in v0.8.)
CQ 8.4 Which drawings are filed in a package other than the one their title block names? (Added in v0.8.)

CQ 8.4 as a query (a title block that names no package is not compared):

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 8.4: the drawings filed in another package than their title block names
SELECT ?drawing ?named ?filed WHERE {
  ?titleblock a metadata:Titleblock ;
              metadata:assertsMetadataFor ?drawing ;
              metadata:assertsPackage     ?named .
  ?drawing metadata:belongsToPackage ?filed .
  FILTER (?named != ?filed)
}

CQ Group 9 — Source File and Page (validates FR 9)

ID Competency Question
CQ 9.1 In which file, and on which page, is drawing "ST-101" stored? (Added in v0.9.)
CQ 9.2 Which drawings are in file "A101-ground-floor.pdf"? (Added in v0.9.)
CQ 9.3 Which files hold more than one drawing? (Added in v0.9.)
CQ 9.4 Which drawings are in files last modified after 1 January 2026? (Added in v0.9.)
CQ 9.5 Where was the file that drawing "ST-101" is stored in obtained from, including when that file was made from another file? (Added in v0.15.)

CQ 9.1, CQ 9.3 and CQ 9.5 as queries:

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>

# CQ 9.1: the file and the page of a drawing
SELECT ?fileName ?pageNumber WHERE {
  ?drawing metadata:drawingIdentifier "ST-101" ;
           metadata:isOnPage          ?page .
  ?page aprov:pageNumber ?pageNumber ;
        aprov:belongsToFile ?file .
  ?file aprov:fileName ?fileName .
}
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>

# CQ 9.3: the files that hold more than one drawing
SELECT ?file (COUNT(DISTINCT ?drawing) AS ?drawings) WHERE {
  ?drawing metadata:isOnPage ?page .
  ?page aprov:belongsToFile ?file .
}
GROUP BY ?file HAVING (COUNT(DISTINCT ?drawing) > 1)
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX prov:     <http://www.w3.org/ns/prov#>

# CQ 9.5: where the file of a drawing was obtained from, following the files it was made from
SELECT ?file ?origin ?sourceLocation ?sourcePage WHERE {
  ?drawing metadata:drawingIdentifier "ST-101" ;
           metadata:isOnPage          ?page .
  ?page aprov:belongsToFile ?file .
  ?file prov:wasDerivedFrom* ?origin .
  ?origin aprov:sourceLocation ?sourceLocation .
  OPTIONAL { ?origin aprov:sourcePage ?sourcePage }
}

CQ Group 10 — How a Value Was Produced (validates FR 10)

ID Competency Question
CQ 10.1 For the title of drawing "ST-101": which run produced each value recorded for it, when the run started, which step, which model or person, and with which configuration? (Added in v0.17.)
CQ 10.2 Which versions of the ADIRO ontologies did each extraction run use, and when did it start? (Added in v0.17.)
CQ 10.3 For the title of drawing "ST-101": which assertions were made, by which model or person, when, and how was each reviewed (pending, accepted, rejected, superseded by a correction)? (Added in v0.18.)
CQ 10.4 For the title of drawing "ST-101": what image did the step that read each value see: at which resolution, which region of the page, and where is the image kept, if it is? (Added in v0.19.)
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX prov:     <http://www.w3.org/ns/prov#>
PREFIX dcterms:  <http://purl.org/dc/terms/>

# CQ 10.1: the run, the step, the model and the configuration behind each value of a field of a drawing
SELECT ?assertion ?value ?run ?started ?step ?model ?agent ?configuration WHERE {
  ?drawing metadata:drawingIdentifier "ST-101" .
  ?assertion aprov:assertedAbout    ?drawing ;
             aprov:assertsFieldKind metadata:DrawingTitleField ;
             aprov:hasInferenceMeta ?step .
  OPTIONAL { ?assertion aprov:hasLiteralValue|aprov:hasValueEntity ?value }
  OPTIONAL { ?step aprov:inferredWith ?model }
  OPTIONAL { ?step aprov:inferredBy ?agent }
  OPTIONAL { ?step dcterms:isPartOf ?run . OPTIONAL { ?run prov:startedAtTime ?started } }
  OPTIONAL { ?step prov:used ?configuration . ?configuration a aprov:Configuration }
}

The query reads the data as written, with no inference: the configuration is recognised by its type, and the model by inferredWith. A value typed by a person has a step with no model and no run, and is listed with the person (inferredBy) and those left empty.

PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX prov:     <http://www.w3.org/ns/prov#>
PREFIX dcterms:  <http://purl.org/dc/terms/>

# CQ 10.2: the ADIRO versions each extraction run used
SELECT DISTINCT ?run ?started ?version WHERE {
  ?step a aprov:InferenceMeta ;
        dcterms:isPartOf ?run .
  ?run prov:used ?version .
  FILTER(REGEX(STR(?version), "^https://w3id[.]org/adiro/[a-z_]+/[0-9]+[.][0-9]+[.][0-9]+$"))
  OPTIONAL { ?run prov:startedAtTime ?started }
}

A version is recognised by the form of its IRI, https://w3id.org/adiro/<module>/<major>.<minor>.<patch>, which is the owl:versionIRI of every ADIRO release, so a run's data answers the question without the ontology loaded beside it. The run is found through its steps, because dcterms:isPartOf has no domain and is used for other things too.

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>

# CQ 10.3: the history of the values of a field of a drawing, oldest first
SELECT ?assertion ?value ?outcome ?model ?agent ?at ?acceptance ?acceptedBy ?supersededBy WHERE {
  ?drawing metadata:drawingIdentifier "ST-101" .
  ?assertion aprov:assertedAbout    ?drawing ;
             aprov:assertsFieldKind metadata:DrawingTitleField .
  OPTIONAL { ?assertion aprov:hasLiteralValue|aprov:hasValueEntity ?value }
  OPTIONAL { ?assertion aprov:hasOutcome ?outcome }
  OPTIONAL {
    ?assertion aprov:hasInferenceMeta ?step .
    OPTIONAL { ?step aprov:inferredWith ?model }
    OPTIONAL { ?step aprov:inferredBy ?agent }
    OPTIONAL { ?step aprov:inferredAt ?at }
  }
  OPTIONAL { ?assertion aprov:hasAcceptance ?status }
  BIND (COALESCE(?status, aprov:Pending) AS ?acceptance)
  OPTIONAL { ?assertion aprov:acceptedBy ?acceptedBy }
  OPTIONAL { ?supersededBy aprov:supersedes ?assertion }
}
ORDER BY ?at ?assertion

Every assertion is listed, the superseded ones included, oldest first: a model's value and a person's correction that supersedes it appear one after the other, with who accepted each. An assertion with no acceptance recorded is Pending, as in CQ 4.6. It uses only terms that CQ 4.6 and CQ 10.1 already use.

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX geom:     <https://w3id.org/adiro/adiro_geometry#>
PREFIX prov:     <http://www.w3.org/ns/prov#>

# CQ 10.4: the image of the page that the step behind each value of a field saw
SELECT ?assertion ?value ?step ?frame ?dpi ?region ?box ?image ?location WHERE {
  ?drawing metadata:drawingIdentifier "ST-101" .
  ?assertion aprov:assertedAbout    ?drawing ;
             aprov:assertsFieldKind metadata:DrawingTitleField ;
             aprov:hasInferenceMeta ?step .
  OPTIONAL { ?assertion aprov:hasLiteralValue|aprov:hasValueEntity ?value }
  OPTIONAL {
    ?step prov:used|aprov:inferredFrom ?frame .
    ?frame a geom:CoordinateFrame .
    OPTIONAL { ?frame geom:resolutionDpi ?dpi }
    OPTIONAL { ?frame geom:coversRegion ?region . OPTIONAL { ?region geom:bboxXYXY ?box } }
    OPTIONAL { ?image geom:imageOf ?frame . OPTIONAL { ?image aprov:storageLocation ?location } }
  }
}

A frame is recognised by its type, so the page, the configuration and the model, which the step also used, are not taken for one. A frame with no region shows the whole page; ?box is the region in the coordinates of its own frame (usually page_display_pt). A frame whose image was not kept has no ?image: what the model saw is recorded either way. A value whose step recorded no frame (typed by a person, or read by a step that does not record one) is listed with the frame columns empty, as CQ 10.1 lists a value with no run.

CQ Group 11 — Text Read from a Drawing (validates FR 11)

ID Competency Question
CQ 11.1 Which drawings mention "ground floor" anywhere in their title block, whether or not it was read as a field? (Added in v0.18.)
CQ 11.2 For page 1 of file "A101-ground-floor.pdf": what text did the latest run read from its title block and from the whole page, in which language, and if it read none, why (empty, illegible, failed, with the error)? (Added in v0.18.)
CQ 11.3 Which pages of file "A101-ground-floor.pdf" did each run process, and with what outcome? (Added in v0.18.)
CQ 11.4 Which pages were searched for a title block by a detection that did not fail, and the store holds no title block on them? (Added in v0.18.)
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>

# CQ 11.1: the drawings whose title block mentions a text, in any reading of it
SELECT DISTINCT ?drawing ?identifier WHERE {
  ?drawing metadata:contains ?titleblock .
  ?titleblock a metadata:Titleblock .
  ?reading aprov:isReadingOf ?titleblock ;
           aprov:readText    ?text .
  FILTER (CONTAINS(LCASE(STR(?text)), "ground floor"))
  OPTIONAL { ?drawing metadata:drawingIdentifier ?identifier }
}
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX prov:     <http://www.w3.org/ns/prov#>
PREFIX dcterms:  <http://purl.org/dc/terms/>

# CQ 11.2: what the latest run read from the title block and from the whole of a page, or why it read nothing
SELECT ?target ?text ?language ?outcome ?error ?run WHERE {
  ?file aprov:fileName "A101-ground-floor.pdf" .
  ?page aprov:belongsToFile ?file ;
        aprov:pageNumber    ?number .
  FILTER (?number = 1)
  ?page (^metadata:isOnPage/metadata:contains)? ?target .
  FILTER (?target = ?page || EXISTS { ?target a metadata:Titleblock })
  ?reading aprov:isReadingOf ?target ;
           aprov:hasInferenceMeta/dcterms:isPartOf ?run .
  OPTIONAL { ?run prov:startedAtTime ?started }
  FILTER NOT EXISTS {
    ?later aprov:isReadingOf ?target ;
           aprov:hasInferenceMeta/dcterms:isPartOf/prov:startedAtTime ?laterStart .
    FILTER (!BOUND(?started) || ?laterStart > ?started)
  }
  OPTIONAL { ?reading aprov:readText ?text }
  OPTIONAL { ?reading aprov:hasReadingOutcome ?outcome }
  OPTIONAL { ?reading aprov:errorMessage ?error }
  BIND (LANG(?text) AS ?language)
}
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX prov:     <http://www.w3.org/ns/prov#>
PREFIX dcterms:  <http://purl.org/dc/terms/>

# CQ 11.3: each page of a file, the runs that processed it, and the outcome of its reading
SELECT DISTINCT ?number ?run ?status WHERE {
  ?file aprov:fileName "A101-ground-floor.pdf" .
  ?page aprov:belongsToFile ?file ;
        aprov:pageNumber    ?number .
  OPTIONAL {
    ?step a aprov:InferenceMeta ;
          prov:used|aprov:inferredFrom ?page ;
          dcterms:isPartOf ?run .
    OPTIONAL { ?step aprov:errorMessage ?stepError }
  }
  OPTIONAL {
    ?reading aprov:isReadingOf ?page ;
             aprov:hasInferenceMeta/dcterms:isPartOf ?run .
    OPTIONAL { ?reading aprov:readText ?text }
    OPTIONAL { ?reading aprov:hasReadingOutcome ?o }
  }
  BIND (IF(!BOUND(?run), "NotProcessed",
        IF(BOUND(?o), STRAFTER(STR(?o), "#"),
        IF(BOUND(?stepError), "Failed",
        IF(BOUND(?text), "Read", "Processed")))) AS ?status)
}
ORDER BY ?number ?run
PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX aprov:    <https://w3id.org/adiro/adiro_provenance#>
PREFIX prov:     <http://www.w3.org/ns/prov#>
PREFIX dcterms:  <http://purl.org/dc/terms/>

# CQ 11.4: the pages a region detection searched, on which no title block was detected
SELECT DISTINCT ?file ?number WHERE {
  ?step aprov:hasStepKind aprov:RegionDetection ;
        prov:used|aprov:inferredFrom ?page .
  FILTER NOT EXISTS { ?step aprov:errorMessage ?error }
  ?page aprov:belongsToFile ?file ;
        aprov:pageNumber    ?number .
  FILTER NOT EXISTS {
    ?drawing metadata:isOnPage ?page ;
             metadata:contains ?titleblock .
    ?titleblock a metadata:Titleblock .
  }
}

The queries read the data as written, with no inference. A step records a page it used with prov:used, or with inferredFrom, its sub-property, so both are read. In CQ 11.3 a page is NotProcessed when no step of any run used it and nothing read it; its reading's outcome when a reading of it has one; Failed when a step of the run that used it failed; Read when it has text; otherwise Processed (used without its text being read). CQ 11.4 leaves out a detection that failed, and reads every other page a region detection used as searched for a title block (open point G13). It answers for the pages as the store now holds them, not per run: a title block is not tied to the run that detected it, so a later run that misses a title block an earlier run found does not list the page.

CQ Group I — Integration / Multi-field Queries

ID Competency Question FRs exercised
CQ-I 1 What sheets in project "X" contain a MEP Layout and were approved by "R. Jones" after March 2024? FR 2, FR 4, FR 5, FR 7
CQ-I 2 What sheets at scale 1:50 contain a Structural Layout and belong to project "Y"? (Only sheets with a sheet-level scale are returned; see CQ 1.3.) FR 1, FR 2, FR 5
CQ-I 3 What sheets in project "X" contain a Structural Layout of content type Detail? FR 2, FR 5, FR 6

5. SPARQL Validation

How the recorded queries are run. (Added in v0.18.) Every query recorded in this document is written for a store in which each run's data is a named graph of its own, corrections are in another, and nothing is inferred:

  • Union default graph. The queries name no graph: they read the union of the named graphs, so a value, the step that produced it and the run it is part of are found together wherever each was written, and a correction in its own graph supersedes an assertion of a run. A store whose default graph is not the union of its named graphs is configured so, or each query is given its graphs with FROM. A question about one run selects it by its IRI (CQ 10.2, CQ 11.3), not by its graph.
  • No inference. The queries read the data as written: a class or a property is matched as stated, never through rdfs:subClassOf or rdfs:subPropertyOf, and where a sub-property can carry the same fact both are named (prov:used|aprov:inferredFrom in CQ 11.3 and CQ 11.4). The one fact the queries take from the ontology, the property a field kind is promoted to (aprov:mapsToFieldProperty, read by the promotion), is read from the ontology modules loaded into the store as data, in a graph of their own.

The tests run every recorded query twice: on the case's data as one graph, and on the same triples spread over several named graphs through the union default graph, and the answers must be the same (#241; tests/conftest.py). No test loads a reasoner.

The following example demonstrates that the term inventory is sufficient to answer integration query CQ-I 1.

CQ-I 1: What sheets in project "X" contain a MEP Layout and were approved by "R. Jones" after March 2024?

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>
PREFIX dcommon:  <https://w3id.org/adiro/adiro_domain_common#>
PREFIX xsd:      <http://www.w3.org/2001/XMLSchema#>

SELECT ?sheet ?drawingIdentifier WHERE {
  ?sheet  a                          metadata:DrawingSheet ;
          metadata:drawingIdentifier     ?drawingIdentifier ;
          metadata:belongsToProject  metadata:ProjectX ;
          metadata:hasRevision       ?rev ;
          metadata:contains          ?layout .

  ?layout a                          metadata:Layout ;
          dcommon:hasDiscipline      ?disc .
  ?disc   a                          dcommon:MEP .

  ?rev    metadata:isApprovedBy       ?person ;
          metadata:issueDate         ?date .
  ?person metadata:personName        "R. Jones" .

  FILTER (?date > "2024-03-01"^^xsd:date)
}

Every filter condition maps to a defined property:

  • metadata:DrawingSheet, metadata:drawingIdentifier, metadata:belongsToProject, metadata:hasRevision, metadata:contains — reused / new in adiro_drawing_metadata.
  • metadata:Layout, dcommon:hasDiscipline, dcommon:MEP — reused; note the rdf:type check against the class hierarchy automatically matches Mechanical, Electrical, Plumbing, Lighting via rdfs:subClassOf reasoning.
  • metadata:isApprovedBy, metadata:issueDate, metadata:personName — new in adiro_drawing_metadata.

The query is fully expressible, confirming that CQ-I 1 is covered by the current term inventory. It reads the discipline through the class hierarchy, so it needs subclass reasoning: it illustrates the term inventory and is not one of the recorded queries, which run without inference (see above). For a store without a reasoner, the discipline pattern is ?disc a/rdfs:subClassOf* dcommon:MEP, with the ontology loaded as data. (Amended in v0.20.) The previous v0.2 placeholder prefix (https://example.org/aec-ontology#) is retired in favour of the real module namespaces.

Scale competency questions

CQ 1.3 and the scale questions CQ 1.4–1.7 are expressible without a reasoner. Each path lists the parent property together with its sub-property, so values written with either are found whether or not sub-property entailment has been applied: a sheet's scale is read with (metadata:drawingScale|metadata:hasScale) and a layout's with (metadata:layoutScale|metadata:hasScale). A sheet's layouts are reached with metadata:contains, as in CQ-I 1. The queries were run with rdflib, without a reasoner, on a small example: a sheet with a title-block scale and three layouts (one with its own scale, one with none, one marked "NTS"), a sheet whose scale was written with hasScale, a sheet with no scale, and a sheet with a single detected layout.

CQ 1.3: What drawing sheets are drawn at scale 1:50? Only a sheet with a sheet-level scale is returned: a layout's scale is never copied to its sheet, so a sheet whose only scale is in the caption of its single layout is not returned.

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 1.3: the drawings drawn at scale 1:50
SELECT ?sheet WHERE {
  ?sheet  a                                         metadata:DrawingSheet ;
          (metadata:drawingScale|metadata:hasScale) "1:50" .
}

CQ 1.4: What scale applies to this layout: its own, or otherwise its sheet's?

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 1.4: the scale of each layout, its own or otherwise its drawing's
SELECT ?layout ?scale ?basis WHERE {
  ?sheet  a metadata:DrawingSheet ;
          metadata:contains ?layout .
  ?layout a metadata:Layout .
  OPTIONAL { ?layout (metadata:layoutScale|metadata:hasScale)  ?own }
  OPTIONAL { ?sheet  (metadata:drawingScale|metadata:hasScale) ?nominal }
  BIND(COALESCE(?own, ?nominal) AS ?scale)
  BIND(IF(BOUND(?own), "own",
          IF(BOUND(?nominal), "assumed from sheet", "none")) AS ?basis)
}

CQ 1.5: Which drawing sheets state no scale at all?

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 1.5: the drawings that state no scale
SELECT ?sheet WHERE {
  ?sheet a metadata:DrawingSheet .
  FILTER NOT EXISTS { ?sheet (metadata:drawingScale|metadata:hasScale) ?scale }
}

CQ 1.6: Which layouts have no scale of their own and sit on a sheet with no scale, so that their scale cannot be determined?

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 1.6: the layouts whose scale cannot be determined
SELECT ?layout WHERE {
  ?sheet  a metadata:DrawingSheet ;
          metadata:contains ?layout .
  ?layout a metadata:Layout .
  FILTER NOT EXISTS { ?layout (metadata:layoutScale|metadata:hasScale)  ?own }
  FILTER NOT EXISTS { ?sheet  (metadata:drawingScale|metadata:hasScale) ?nominal }
}

CQ 1.7: Which layouts are drawn at a different scale from their sheet?

PREFIX metadata: <https://w3id.org/adiro/adiro_drawing_metadata#>

# CQ 1.7: the layouts drawn at another scale than their drawing
SELECT ?layout ?own ?nominal WHERE {
  ?sheet  a metadata:DrawingSheet ;
          (metadata:drawingScale|metadata:hasScale) ?nominal ;
          metadata:contains ?layout .
  ?layout a metadata:Layout ;
          (metadata:layoutScale|metadata:hasScale) ?own .
  FILTER (?own != ?nominal)
}

CQ 1.5 and CQ 1.6 are the closed-world checks for a missing scale (see §2.2).


6. Traceability Matrix

OWL Term Module Action CQ(s) FR(s)
metadata:DrawingSheet adiro_drawing_metadata REUSE CQ 1.x, CQ 2.x, CQ 3.x, CQ 5.x, CQ 6.x, CQ 8.x FR 1, FR 2, FR 3, FR 5, FR 6, FR 8
metadata:Layout adiro_drawing_metadata REUSE CQ 1.4, CQ 1.6, CQ 1.7, CQ 5.x, CQ 6.x, CQ-I 1, CQ-I 2, CQ-I 3 FR 5, FR 6
metadata:LayoutContentType adiro_drawing_metadata REUSE CQ 6.x, CQ-I 3 FR 6
metadata:DrawingRevision adiro_drawing_metadata NEW CQ 3.x, CQ 4.x, CQ 7.x FR 3, FR 4, FR 7
metadata:Project adiro_drawing_metadata NEW CQ 2.x, CQ-I 1 FR 2
metadata:Person adiro_drawing_metadata NEW CQ 4.x, CQ-I 1 FR 4
dcommon:Discipline adiro_domain_common REUSE CQ 5.x, CQ-I 1, CQ-I 2, CQ-I 3 FR 5
metadata:StatusCode adiro_drawing_metadata NEW CQ 7.x, CQ 8.2 FR 7
metadata:DrawingPackage adiro_drawing_metadata NEW CQ 8.x FR 8
metadata:contains adiro_drawing_metadata REUSE CQ 1.4, CQ 1.6, CQ 1.7, CQ-I 1, CQ-I 2, CQ-I 3 (structural)
metadata:hasRevision adiro_drawing_metadata NEW CQ 3.x FR 3
metadata:isAuthoredBy adiro_drawing_metadata NEW CQ 4.1, CQ 4.4 FR 4
metadata:isCheckedBy adiro_drawing_metadata NEW CQ 4.2, CQ 4.5 FR 4
metadata:isApprovedBy adiro_drawing_metadata NEW CQ 4.3, CQ 4.5, CQ-I 1 FR 4
metadata:assertsRevision adiro_drawing_metadata NEW CQ 3.4 FR 3
metadata:hasStatusCode adiro_drawing_metadata NEW CQ 7.x, CQ 8.2 FR 7
metadata:belongsToProject adiro_drawing_metadata NEW CQ 2.x, CQ-I 1, CQ-I 2, CQ-I 3 FR 2
metadata:assertsProject adiro_drawing_metadata NEW CQ 2.3, CQ 2.4 FR 2
dcommon:hasDiscipline adiro_domain_common REUSE CQ 5.x, CQ-I 1, CQ-I 2, CQ-I 3 FR 5
metadata:hasProperty adiro_drawing_metadata REUSE CQ 6.x, CQ-I 3 FR 6
metadata:belongsToPackage adiro_drawing_metadata NEW CQ 8.x FR 8
aprov:DrawingFile adiro_provenance NEW CQ 9.2, CQ 9.3 FR 9
aprov:FilePage adiro_provenance NEW CQ 9.1, CQ 9.3 FR 9
metadata:isOnPage adiro_drawing_metadata NEW CQ 9.1, CQ 9.2, CQ 9.3, CQ 9.4 FR 9
aprov:belongsToFile adiro_provenance NEW CQ 9.1, CQ 9.2, CQ 9.3, CQ 9.4 FR 9
aprov:fileName, aprov:pageNumber adiro_provenance NEW CQ 9.1, CQ 9.2 FR 9
aprov:fileModifiedAt adiro_provenance NEW CQ 9.4 FR 9
aprov:storageLocation, aprov:contentHash, aprov:hashAlgorithm, aprov:mediaType, aprov:fileCreatedAt, aprov:fileCreatedBy, aprov:fileModifiedBy, aprov:pageCount, aprov:fileSize adiro_provenance NEW none yet: they identify, locate and describe the file (the first set of the file brainstorm) FR 9
aprov:sourceLocation, aprov:sourcePage, prov:wasDerivedFrom (a typing stub) adiro_provenance NEW CQ 9.5 FR 9
aprov:InferenceMeta, aprov:inferredWith, aprov:inferredBy adiro_provenance REUSE CQ 10.1, CQ 10.2, CQ 10.3 FR 10
aprov:inferredAt, aprov:hasAcceptance, aprov:supersedes adiro_provenance REUSE CQ 10.3 FR 10
geom:CoordinateFrame, geom:bboxXYXY, aprov:storageLocation adiro_geometry, adiro_provenance REUSE CQ 10.4 FR 10
geom:resolutionDpi, geom:coversRegion, geom:imageOf adiro_geometry NEW CQ 10.4 FR 10
aprov:TextReading, aprov:isReadingOf, aprov:readText, aprov:hasReadingOutcome, aprov:errorMessage adiro_provenance NEW CQ 11.1, CQ 11.2, CQ 11.3 FR 11
aprov:StepKind (RegionDetection, TextRecognition, FieldExtraction), aprov:hasStepKind adiro_provenance NEW CQ 11.4 FR 11
aprov:Configuration, aprov:configurationContent adiro_provenance NEW CQ 10.1 FR 10
dcterms:isPartOf, prov:startedAtTime (typing stubs) adiro_provenance NEW CQ 10.1, CQ 10.2 FR 10
prov:used (typing stub) adiro_provenance REUSE CQ 10.1, CQ 10.2 FR 10
metadata:assertsPackage adiro_drawing_metadata NEW CQ 8.3, CQ 8.4 FR 8
metadata:drawingIdentifier adiro_drawing_metadata NEW CQ 1.1, CQ 1.2 FR 1
metadata:drawingTitle adiro_drawing_metadata NEW CQ 1.2 FR 1
metadata:hasScale adiro_drawing_metadata NEW CQ 1.3–1.7, CQ-I 2 FR 1
metadata:drawingScale adiro_drawing_metadata NEW CQ 1.3–1.7, CQ-I 2 (directly, or through hasScale with entailment) FR 1
metadata:layoutScale adiro_drawing_metadata NEW CQ 1.4, CQ 1.6, CQ 1.7 (directly, or through hasScale with entailment) FR 1
metadata:sheetSize adiro_drawing_metadata NEW — FR 1
metadata:revisionCode adiro_drawing_metadata NEW CQ 3.1, CQ 3.3 FR 3
metadata:issueDate adiro_drawing_metadata NEW CQ 3.2, CQ 3.3, CQ-I 1 FR 3
aprov:Person adiro_provenance NEW CQ 4.x, CQ-I 1 FR 4
aprov:AssertionOutcome (Empty, Illegible, NotPrinted, NotFound, Failed), aprov:hasOutcome adiro_provenance NEW CQ 4.6, CQ 10.3, CQ 11.2, CQ 11.3 FR 4, FR 11
aprov:AcceptanceStatus (Pending, Accepted, Rejected), aprov:hasAcceptance adiro_provenance NEW CQ 4.6 FR 4
aprov:supersedes adiro_provenance NEW CQ 4.6 FR 4
aprov:acceptedBy adiro_provenance NEW CQ 10.3 FR 4
aprov:acceptedAt, aprov:acceptedUnder adiro_provenance NEW none yet: the record of an acceptance (the decision of #85), not asked by a question FR 4
metadata:personName adiro_drawing_metadata NEW CQ 4.x, CQ-I 1 FR 4
metadata:statusLabel adiro_drawing_metadata NEW CQ 7.x FR 7
metadata:projectName adiro_drawing_metadata NEW CQ 2.x FR 2
metadata:projectNumber adiro_drawing_metadata NEW CQ 2.x FR 2
metadata:packageName adiro_drawing_metadata NEW CQ 8.x FR 8

7. Module Alignment Summary

This section makes the placement of every UC-01 term in the existing module hierarchy explicit, per PR #15 review point #2 (@alelom).

Module hierarchy (updated in v0.6):

adiro_provenance                      (NEW - foundational, domain-neutral)
        |
        +---- adiro_geometry          (NEW - foundational: BoundingBox + CoordinateFrame; imports adiro_provenance)
                |
                +---- adiro_drawing_metadata
                        |
                        +---- adiro_common_symbols       (imports adiro_drawing_metadata only)
                        |
                        +---- adiro_domain_common        (imports adiro_drawing_metadata only)
                                |
                                +---- adiro_facade_domain   (also imports adiro_drawing_metadata)

Term placement:

Module UC-01 contribution
adiro_drawing_metadata New classes: DrawingRevision, Project, StatusCode, DrawingPackage. New properties: all UC-01 datatype properties; hasRevision (⊂ contains), hasStatusCode (⊂ hasProperty), belongsToProject, belongsToPackage, isAuthoredBy, isCheckedBy, isApprovedBy, isOnPage.
adiro_provenance New classes: FieldKind (the class of the field kinds of the TitleblockFieldScheme), Configuration (FR 10, with configurationContent), TextReading and StepKind (FR 11, with the outcome value Failed), DrawingFile, FilePage, and the agents Party, Person and Organisation (moved here from adiro_drawing_metadata), with the file and page properties of FR 9. Reused (new module): FieldAssertion, InferenceMeta, hasConfidence, capturedCaption, assertedBy, inferredBy/inferredWith/inferredFrom/inferredAt, and the TitleblockFieldScheme binding via assertsFieldKind. Carries extracted title-block values before validation - see the design note in §2.1.
adiro_geometry Reused (new module): the Titleblock region may carry a BoundingBox (via hasBoundingBox) interpreted by a CoordinateFrame (which reads the page the drawing is on, via describesPage) — i.e. where the title block sits on the page. The extracted field values are read from within that one region and are not individually localised. New: resolutionDpi, coversRegion and imageOf (FR 10): the image of the page, or of a region of it, that a step saw, at its resolution, and the kept image file. (Added in v0.5; amended in v0.19.)
adiro_common_symbols No UC-01 contribution.
adiro_domain_common Reused: Discipline and its subclasses; hasDiscipline (with proposed domain change from LayoutContentType to Layout — see G5).
adiro_facade_domain No UC-01 contribution.

SubProperty wiring:

metadata:contains (already exists)
  └── metadata:hasRevision (NEW)

metadata:hasProperty (already exists)
  └── metadata:hasStatusCode (NEW)

All other new object properties (belongsToProject, belongsToPackage, isAuthoredBy, isCheckedBy, isApprovedBy, assertsRevision, assertsProject, assertsPackage) are declared at the top level — they are associative or role-differentiated and do not fit the "containment" or "characterising property" generalisations.


8. Open Issues — Pending Team Discussion

These items affect UC-01 but cannot be unilaterally decided in the ORSD; recording for review.

ID Issue
G5 Should hasDiscipline domain move from LayoutContentType to Layout? v0.3 proposes yes — discipline characterises the layout, not its content type.
G13 What a region detection looked for. CQ 11.4 reads every page that a region detection used as searched for a title block, which holds while UC-01's extraction detects only title blocks. A run that detects several kinds of region (a title block, a legend) in separate steps would need each step to say what it looked for, which ADIRO does not record yet. Nor is a region tied to the run that detected it, so CQ 11.4 cannot say which run missed a title block another run found. (Added in v0.18.)
G5b Should DrawingSheet itself carry a hasDiscipline (a "primary discipline" for the whole sheet) in addition to Layout-level discipline?
G11 ~~Direct properties vs FieldAssertion.~~ Resolved (#85, #187): a value is promoted when its assertion is accepted, by a pipeline rule or a person, with the acceptance recorded on the assertion; both layers are kept, and the direct properties are permanent. See the design note in §2.1.
G12 ~~A missing person is two different facts.~~ "The extraction did not find the author" and "the drawing names none" must be told apart (the first is retried or reviewed, the second is a defect of the drawing). Decided: record absence as a value-less FieldAssertion with an outcome. Resolved: the vocabulary is in adiro_provenance (hasOutcome, hasAcceptance, #187), and CQ 4.6 reports a drawing by cause.
G10 ~~:Metadata class name misleading~~ — resolved: renamed to :MetadataContainer (team decision). The class models visual supporting regions (titleblock, legend, etc.), not semantic metadata.
— ~~Project-wide convention for owl:inverseOf~~ — resolved in #21: ADIRO does not declare inverse properties. isRevisionOf removed; use ^metadata:hasRevision.
— ~~"Civil" discipline~~ — resolved: Civil to be added as a direct subclass of dcommon:Discipline (team decision).

9. Version History

v0.21 (current — draft)

Changes from v0.20, made when field kinds were given a class of their own and their scheme was documented (#254, #255, planned in #257). MAJOR in substance (an entity added); the number stays in the 0.x series because the document is still a draft:

  • aprov:FieldKind added (§2.1 design note, §7): the field kinds of the TitleblockFieldScheme and the sentinel UnidentifiedField are individuals of it as well as of skos:Concept. It serves the questions that read an assertion's field kind (CQ Group 10, the promotion in §2.1); none of them changes, since they select field kinds by IRI or by scheme.
  • The design note on curated values and extracted assertions (§2.1) says how a field kind relates to a region: through assertions, and through the domain of the property the kind maps to.

v0.20 (draft)

Changes from v0.19, made when the recorded queries were released as a pinnable artefact (#240). MINOR: no entity, attribute, relation or competency question changes:

  • The scale queries are recorded (§5): the queries of CQ 1.3 to CQ 1.7 now open with the comment line that names a recorded query (# CQ 1.3: …), so they are tested and released with the others.
  • CQ-I 1 is an illustration (§5): it reads the discipline through the class hierarchy, which needs a reasoner, so it is not a recorded query; the text gives the pattern for a store without one.

v0.19 (draft)

Changes from v0.18, made when the images a model sees were modelled for UC-01 (#239, decided on Discussion #235). MAJOR in substance (a requirement amended, attributes, relations and a competency question added); the number stays in the 0.x series because the document is still a draft:

  • FR 10 amended (§3): a value is traced to the image of the page its step saw, at its resolution and, for a crop, the region. The design note under FR 10 states the pattern: every image fed to a model is a pixel CoordinateFrame with resolutionDpi, a crop covers a region (coversRegion), the step uses the frame (prov:used), and a kept image is a DrawingFile that is an image of its frame (imageOf), stored at a location that may be relative to the root of the dataset. No transform is recorded.
  • CQ 10.4 added (§4), with its query.
  • resolutionDpi, coversRegion and imageOf added (§2.3, §6, §7) in adiro_geometry; a shape checks frames and kept images (data-validation/frames.shacl.ttl).

v0.18 (draft)

Changes from v0.17, made when text readings were modelled for UC-01 (#238, decided on Discussion #235) the history of a value was asked for (#236), and the queries were checked over named graphs (#241). MAJOR in substance (a functional requirement, classes, attributes and competency questions added); the number stays in the 0.x series because the document is still a draft:

  • FR 11 and CQ Group 11 added (§3, §4): the text read from a title block or a page, its language and why none was read (CQ 11.1, CQ 11.2), which pages a run processed (CQ 11.3) and on which it detected no title block (CQ 11.4). The coverage questions that #236 would have recorded as pending in §8 are answered here instead.
  • CQ 10.3 added (§4): the history of the values of a field, by model or person, with how each was reviewed, from existing terms only. acceptedBy is now asked by a question (§6).
  • TextReading, StepKind and the outcome Failed added (§2.1, §2.3, §6, §7), with isReadingOf, readText, hasReadingOutcome, errorMessage and hasStepKind; a shape checks that a reading has a text or an outcome (data-validation/readings.shacl.ttl). The design note under FR 11 says why a reading has its own outcome property.
  • CQ 4.6 gains the reason Failed, retried like NotFound.
  • G13 added (§8): what a region detection looked for, when a run detects several kinds of region.
  • How the recorded queries are run (§5, #241): over named graphs, one per run and one for corrections, through the union default graph, with no inference; the ontology is loaded as data where the promotion needs it. Every recorded query is tested both ways, and none needed a change.

v0.17 (draft)

Changes from v0.16, made when runs were modelled for UC-01 (#237, decided on Discussion #235). MAJOR in substance (a functional requirement, a class, an attribute and a competency question added); the number stays in the 0.x series because the document is still a draft:

  • FR 10 and CQ Group 10 added (§3, §4): which run, step and model produced a value, with which configuration, and which ontology versions the run used. CQ 10.1 and CQ 10.2 are recorded as queries, run without inference; CQ 10.2 recognises a version by the form of its IRI. The design note recommends how a configuration's IRI is built from its content.
  • Configuration and configurationContent added (§2.1, §6), with the typing stubs dcterms:isPartOf (a step is part of its run, §2.3) and prov:startedAtTime; a shape checks that a configuration has exactly one content (data-validation/configuration.shacl.ttl). The design note under FR 10 states the pattern: a run is a prov:Activity, its steps are InferenceMeta, as UC-03's provenance profile (#96) does.

v0.16 (draft)

Change from v0.15, made when the meaning of supersession was decided (#221). MINOR: the rule of a recorded query, no entity, attribute, relation or competency question changes; the number stays in the 0.x series because the document is still a draft:

  • Supersession takes effect on acceptance. The promotion query withdrew any assertion that another one supersedes, whatever that one's acceptance, so a pending re-extraction that superseded an accepted title left the drawing with no title until it was reviewed, and a rejected one left it with none for good. Only an accepted assertion now withdraws the ones it supersedes. A correction by a person, who accepts it, still takes effect at once, and a value known to be wrong is withdrawn by rejecting it. The section after the promotion query states the rule and its cases.
  • Through a chain. The withdrawal follows supersedes transitively (aprov:supersedes+), so an accepted correction of a correction withdraws the original even when the one in between was never accepted, and a chain gives at most one value. A cycle of supersedes is a validation error.
  • CQ 4.6 reads the same rule. It no longer hides an assertion superseded only by a pending or rejected one, so a drawing with two unreviewed attempts shows both.
  • Keeping the derived statements. A store that keeps the promoted statements replaces the earlier set; it does not add to it.

v0.15 (draft)

Changes from v0.14, made when the place a file was obtained from was modelled (#229). MAJOR in substance (attributes, a relation and a competency question added); the number stays in the 0.x series because the document is still a draft:

  • FR 9 says where a file was obtained from (§3). Before, it asked to identify and locate a file, and storageLocation recorded only where copies are kept, so a public drawing copied into internal storage before processing kept only internal addresses. sourceLocation (the address the bytes were obtained from) and sourcePage (the page describing the file at its origin) are new (§3, §6). A file made from another file points back to it with prov:wasDerivedFrom, and only the original records a source.
  • CQ 9.5 added (§4), with its query: where the file of a drawing was obtained from, following the files it was made from. A data check warns about a file with no recorded origin, and, for a public release, reports an address that is not on a public host (the file a drawing is stored in).

v0.14 (draft)

Change from v0.13, made when the data checks of an assertion's status and outcome were added (#220). MINOR: a clarification, no entity, attribute, relation or competency question changes; the number stays in the 0.x series because the document is still a draft:

  • The promotion statement is tied to validated data. The sentence after the promotion query said that a pending, rejected, outcome-only or superseded assertion gives nothing, without condition. The query promotes any assertion that has Accepted among its statuses, so an assertion both Accepted and Rejected was promoted. The shapes now report such an assertion, and the sentence says it holds for data that passes them.

v0.13 (draft)

Change from v0.12, made when the CQ 4.6 query was found to misreport two cases (#219). MINOR: a correction of a recorded query, no entity, attribute or relation changes; the number stays in the 0.x series because the document is still a draft:

  • CQ 4.6 reads the acceptance. It reported a rejected value as Pending, because it took any assertion without an outcome to be awaiting acceptance, and a rejected NotPrinted as a finding that the drawing names no author. A rejected assertion is now Rejected, and an accepted value not yet promoted is AcceptedNotPromoted; an assertion with neither a value nor an outcome, which can never be promoted, is NoValue. The acceptance and the outcome are separate columns.
  • CQ 4.6 reads the assertions about the revisions. CQ 4.4 counts a revision's author, but CQ 4.6 looked only at the assertions about the drawing, so a drawing whose revision's author was illegible was NotProcessed. It now gives one row per assertion about the drawing or one of its revisions, with its subject.

v0.12 (draft)

Change from v0.11, made when the modules were renamed from aec_* to adiro_* (#171). MINOR: no entity, attribute, relation or competency question changes, only the module names and the namespaces of the IRIs this document cites (the competency-question queries now use the adiro_* namespaces); the number stays in the 0.x series because the document is still a draft. The entries below keep the names of their time.

v0.11 (draft)

Change from v0.10, made when the promotion rule was written down (#85). MINOR: an example added; the number stays in the 0.x series because the document is still a draft:

  • The promotion is recorded as a SPARQL CONSTRUCT after the design note in §2.1: an accepted assertion that has a value, and that no later assertion supersedes, gives the direct statement its field kind maps to. It runs on small data in tests/test_uc01_competency_queries.py. This is the "documented rule that the tooling runs" of the decision on #85.

v0.10 (draft)

Changes from v0.9, made when the outcome and the acceptance of an assertion were modelled (#187, decided in #85 and #179). MINOR: a design note amended, open issues resolved, one competency question added; the number stays in the 0.x series because the document is still a draft:

  • The design note "curated values vs extracted assertions" (§2.1) is amended: a value is promoted when its assertion is accepted, the assertions are kept, the direct properties are permanent. G11 is resolved.
  • AssertionOutcome, AcceptanceStatus and their properties added in aec_provenance (§6): hasOutcome (Empty, Illegible, NotPrinted, NotFound, following the ground-truth observation statuses), hasAcceptance (Pending, Accepted, Rejected), acceptedBy, acceptedAt, acceptedUnder and supersedes. G12 is resolved.
  • CQ 4.6 added, with its query: a drawing with no recorded author, by cause.

v0.9 (draft)

Changes from v0.8, made when the file a drawing is stored in was modelled (#192). MAJOR in substance (entities and relations added, one moved, one removed); the number stays in the 0.x series because the document is still a draft:

  • FR 9 and CQ Group 9 added (§3, §4): the file a drawing is stored in, and the page of it. DrawingFile, FilePage, isOnPage and belongsToFile are new (§2.1, §2.3, §6), with the properties that describe a file and a page; CQ 9.1 and CQ 9.3 are recorded as queries. The design is in the file a drawing is stored in.
  • Person moved to aec_provenance (§2.1, §6), with its new parent Party and Organisation: they are domain-neutral, and a file's creator needs them too. personName stays in aec_drawing_metadata.
  • hasCoordinateFrame removed: the coordinate frames of a drawing are reached with isOnPage and describesPage. A region of the drawing stays a BoundingBox (hasBoundingBox), now stated as a restriction on MetadataContainer, on Layout and on DrawingElement, so the title block, a revision table, a legend, a key plan, a note, a layout and any symbol or component may each carry one.

v0.8 (draft)

Changes from v0.7, made when the person roles were extended to the drawing and the revision table was linked to its revisions (#179, #69). MAJOR in substance (relations re-scoped and added, competency questions added); the number stays in the 0.x series because the document is still a draft:

  • isAuthoredBy, isCheckedBy and isApprovedBy now apply to a DrawingSheet as well as a DrawingRevision (§2.3, FR 4, §6). The title block names who drew, checked and approved the drawing; a revision can be made by other people, so the two are different facts and both are kept. The "Person vs Role" note is amended. The domain is the union of the two classes; no cardinality, because an extraction may find nobody (#84). A drawing that records no author is read as authored by its revisions' authors (a path, not an entailment).
  • assertsRevision added (RevisionTable to DrawingRevision, §2.3, FR 3, §6): one link per row of a printed revision table, so a table with revisions A, B and C asserts three. It records which table a revision was read from; it does not say which revision is the latest (that is read from issueDate).
  • issueDate applies to a DrawingSheet as well as a DrawingRevision (§2.2): the title block's date is the drawing's, and "date authored" is the same property, not a second one.
  • assertsProject added (Titleblock to Project, §2.3, FR 2, §6) with CQ 2.3 and CQ 2.4: the project a title block names is a claim, and the project a drawing is filed under (belongsToProject) is a fact; the two can differ, and CQ 2.4 finds the drawings where they do.
  • assertsPackage added (Titleblock to DrawingPackage, §2.3, FR 8, §6) with CQ 8.3 and CQ 8.4, on the pattern of assertsProject. A title block may or may not name a package, so it is optional (no cardinality, nothing to compare when it names none).
  • CQ 3.4, CQ 4.4 and CQ 4.5 added, with the queries for CQ 3.4 and CQ 4.4. A drawing must have an author; a checker and an approver are optional. CQ 4.4 is a closed-world check, and the same rule is a data-validation shape.
  • Open issue G12 added: a missing person is two different facts (not found, not printed); decided in principle, vocabulary open.

v0.7 (draft)

Changes from v0.6, made when the scale was split into a sheet-level and a layout-level property (#162). MAJOR in substance (attributes added); the number stays in the 0.x series because the document is still a draft:

  • metadata:drawingScale (on DrawingSheet) and metadata:layoutScale (on Layout) added as sub-properties of metadata:hasScale, in the §2.2 attributes table, the FR 1 derived terms and the §6 traceability matrix. drawingScale is the scale of the sheet as a whole (usually in the title block); layoutScale is the scale in a layout's own caption.
  • hasScale is unchanged; CQ 1.3 and CQ-I 2 are about the sheet's scale and are answered with or without entailment: with sub-property entailment a value asserted with drawingScale is also a hasScale value; without it, the sheet's scale is read with the property path metadata:hasScale|metadata:drawingScale. CQ 1.3 and CQ-I 2 are unchanged in substance; their text now states that they return only sheets with a sheet-level scale, so a sheet whose only scale is in its single layout's caption is not returned.
  • Where a scale is printed. §2.2 gains a table of where a scale is printed and which property records it. drawingScale is the scale of the sheet as a whole (the title block is the usual place, and a general note outside any layout also counts, judged from context at extraction); layoutScale is the scale in a layout's own caption, "NTS" / "As shown" are recorded verbatim, and a layout that prints no scale gets none. A layout's scale is not copied to the sheet: a scale belongs to a drawing view, and a drawingScale taken from the only layout detected would stop being true once more layouts are detected.
  • CQ 1.4–1.7 added (Group 1): the scale that applies to a layout, sheets with no scale, layouts whose scale cannot be determined, and layouts at a different scale from their sheet. layoutScale is now named by CQ 1.4, 1.6 and 1.7. A missing scale is a closed-world check, answered by a query and not by an OWL restriction. §5 gives the SPARQL for CQ 1.3–1.7, run without a reasoner.
  • sheetSize naming noted. sheetSize keeps "sheet" because a sheet of paper has a size, while the printed fields say "drawing"; "drawing size" is recorded as a synonym (skos:altLabel) so that a second term is not added. No requirement changed.
  • Labelling. drawingIdentifier, drawingTitle and drawingScale are marked isComputerVisionLabel, so annotation tooling can box each as a text field. No requirement changed.

v0.6 (draft)

Changes from v0.5, made when the unused owl:imports of aec_common_symbols was removed from aec_domain_common and aec_facade_domain (#134). MINOR — suite-accuracy only, no UC-01 term changes:

  • §7 module hierarchy corrected. aec_common_symbols and aec_domain_common each import aec_drawing_metadata only, and aec_facade_domain imports aec_drawing_metadata and aec_domain_common; the earlier diagram drew a single linear chain through aec_common_symbols, which was never the import graph.

v0.5 (draft)

Changes from v0.4, made in PR #76 when the aec_geometry module was added (#90). MINOR:

  • New foundational module aec_geometry added to the §7 module hierarchy — a second foundational root (imports aec_provenance), which aec_drawing_metadata now imports.
  • aec_geometry row added to the §7 term-placement table: the Titleblock region may carry a page BoundingBox (via hasBoundingBox) interpreted by a CoordinateFrame (owned by the sheet via hasCoordinateFrame). Title-block fields are not individually localised — only the title block itself carries a box.

v0.4 (draft)

Changes from v0.3, made in PR #76 when aec_provenance was added to the suite:

  • New design note in §2.1, "curated values vs extracted assertions." UC-01's datatype properties on DrawingSheet remain the query surface for a validated value; a machine-extracted, not-yet-validated value now travels as an aprov:FieldAssertion carrying capturedCaption, assertedBy, hasInferenceMeta and hasConfidence, and is promoted via aprov:mapsToFieldProperty.
  • aec_provenance row added to the §7 term-placement table.
  • §7 module hierarchy updated — aec_provenance is a new foundational root above aec_drawing_metadata.
  • New open issue G11 — when a value is promoted from an assertion to a direct property, and whether the direct properties eventually deprecate (#85).

  • BREAKING — metadata:isRevisionOf removed. #21 decided project-wide that ADIRO declares no named inverse properties and no owl:inverseOf axioms. Navigate from a revision to its sheet with the SPARQL inverse path ^metadata:hasRevision. The §2.3 relations table, the FR 3 derived terms, the traceability matrix and the §7 module table are updated; no competency question changed, and no SPARQL validation query in this document used the removed property.

A relation was removed, so this is a MAJOR revision in substance; the number stays in the 0.x series because the document is still a draft and v0.4 was never released.

v0.3

Aligned with the existing ontology modules (aec_drawing_metadata, aec_domain_common) per PR #15 review (@alelom):

  • Drawing → metadata:DrawingSheet; Layout added as a first-class entity (G1).
  • dcommon:hasDiscipline proposed to move from LayoutContentType to Layout (G5 — open issue).
  • Reuse dcommon:Discipline class hierarchy; drop disciplineCode string property (G3).
  • Reuse metadata:LayoutContentType; drop DrawingType / hasDrawingType / typeLabel (G4).
  • Datatype properties (drawingIdentifier, drawingTitle, hasScale, sheetSize) attached directly to DrawingSheet — no intermediate entity (G2).
  • New object properties wired into metadata:contains / metadata:hasProperty via rdfs:subPropertyOf (G6).
  • SPARQL placeholder namespace replaced with real module prefixes (G8).
  • Only isRevisionOf materialised as owl:inverseOf; other inverses deferred (G9). (Reversed in v0.4 — no inverse properties are declared at all.)
  • Stray editing artifact on FR 4 removed.
  • New §7 Module Alignment Summary added.

v0.2 and earlier

Predate this changelog.


End of ORSD — UC-01 v 0.3