Terms coined for the ÖKOBAUDAT wrapper, and only those the
reused vocabularies do not already carry. schema:, dcat:, dcterms:, skos:, org:,
qudt: (2.1), prov: and foaf: do the rest. @en
A result set produced by keyword matching. Kept distinct
from a plain result set because ÖKOBAUDAT's name and description filters are
case-insensitive SUBSTRING matches that run across both the German and English
variants of a record — so a hit is a candidate for a human to judge, not an
identification. @en
A third-party-verified declaration of a construction
product's life-cycle environmental performance under EN 15804. Subclass of
dcat:Dataset because that is what it is: a published dataset about a product,
not the product. @en
An ILCD flow: a product, an elementary flow, or one of the EN 15804
reminder flows that carry inventory values. Only a flow ÖKOBAUDAT types
"Product flow" is additionally a schema:Product — that typing is what lets a
product be identified rather than guessed at, and it held on 24 of 24 reference
flows measured. @en
A measurable property of a flow — mass, area, energy content.
Together with its value on a flow this is what lets a declaration stated per m²
be related to a quantity of material at all. @en
One indicator's value for one life-cycle module — the
intersection of a row and a column in an EPD's results table. Addressable on
purpose: "the GWP-total of module A1-A3 of this EPD" is the single most-cited
figure in the whole register, and a blank node could not be cited at all.
Deliberately shaped like an RDF Data Cube observation — exactly two dimensions
(indicator, module) and one measure — so that adding qb:Observation later is
purely additive and nothing has to be re-minted. @en
An EN 15804 life-cycle inventory indicator, such as PERE or
NHWD. Upstream carries these as exchanges rather than as LCIA results, which is
a modelling distinction in ILCD, not a difference in kind for a reader. @en
An EN 15804 life-cycle stage: A1-A3 product, A4-A5
construction, B1-B7 use, C1-C4 end of life, D benefits and loads beyond the
system boundary. The set an EPD reports is NOT fixed — observed EPDs carry
anywhere from one module to fifteen. @en
What was asked of /search, kept as its own resource so a
consumer can check the answer against the question.
That matters more here than it looks: ÖKOBAUDAT's filters do not combine
uniformly — name and description are ORed with each other while every other
filter narrows — so a result count cannot be reasoned back to the query. @en
A published ÖKOBAUDAT snapshot, e.g. OBD_2023_I. Releases
genuinely archive: the same EPD UUID carries different content and a different
dataSetVersion in different releases, and membership changes between them. @en
A set of units and the factors between them, relative to one
reference unit. Serving the unit names without the factors leaves a document
listing units you cannot convert between, which is what this originally did. @en
Which vocabulary a location code is read as belonging to:
iso3166, ecoinvent, grouping, nonstandard or freetext. ÖKOBAUDAT mixes all of
them without reconciling them, so this records the wrapper's reading of a code
rather than anything upstream declares. @en
The standard a declaration was verified against.
The vintage is not a formality: EN 15804+A1 and +A2 use different reference
substances, so acidification is kg SO2 eq. under one and mol H+ eq. under the
other. Declarations citing different vintages are not comparable indicator for
indicator. @en
Something the wrapper noticed while converting that a
consumer should know — an unparseable value, an unknown indicator, a lapsed
validity. A statement about the DOCUMENT and its conversion, never about the
product. @en
The organisation that owns a declaration — in practice the
manufacturer.
The ROLE is carried by this property, not by the organisation it points at: the
same body can be owner here, registration authority there and publisher
elsewhere, so a role asserted on the organisation would be wrong half the
time. @en
ILCD's own version string for a record.
Load-bearing for the Memento views: the same UUID carries different versions in
different releases (20.21.060 in OBD_2021_II, 20.23.050 in OBD_2023_I), which is
what makes a memento a real archived state rather than a relabelled copy. @en
A search for the DECLARATIONS this organisation owns — not
its products, which are one hop further via :declaredProduct on each.
That distinction is the shape of the data, not pedantry: ÖKOBAUDAT attaches
ownership to the declaration and never to the product, so there is no direct
company-to-product edge to publish. Reaching a company's products means walking
each declaration.
ÖKOBAUDAT names an owner on every declaration but publishes NO link back, so
this search is the only route. It is keyed on the organisation's NAME, because
upstream offers no search by contact identifier — so the result is a candidate
set, and another company whose name contains this one's would appear in it. @en
How much of the product the figures are for — 1 m², 1 kg.
A fact about the DECLARATION's reference, not about the product, which is why it
sits here and not on the schema:Product. @en
A search for the declarations about this product — the route
from a product to its manufacturer, since the flow record names no owner and the
declaration does.
ÖKOBAUDAT publishes no link from a flow back to the declarations that use it,
and offers no search by flow identifier, so this is keyed on the product NAME.
It is therefore a CANDIDATE set: a product whose name is a substring of
another's brings back both.
Reaching the manufacturer is three hops — product, this search, a declaration,
then :dataSetOwner — and no shorter route exists, because the flow record names
no owner and upstream attaches ownership to the declaration. @en
The product this declaration is about — the ILCD product
flow, which ÖKOBAUDAT publishes as a data set in its own right.
Note that product identity does NOT persist across declarations: the same named
product re-declared under a later standard gets a different flow UUID, and there
is no GTIN or model number anywhere in the data to join them by. This property
therefore says what this declaration is about, and does not claim that two
declarations describe the same product. @en
A substring the declaration's description must
contain. Same substring-and-cross-language behaviour as :nameContains, and ORed
with it rather than intersected. @en
True when the declaration's validity has lapsed. Such an EPD
is still served — an assessment made while it was current still cites it, and
its URI must keep resolving — but it must not be read as a current
declaration. @en
One property of a flow with its value — the mass per square
metre of a board, say. This is what lets a declaration stated per m² be related
to a quantity of material at all; without it the figures cannot be converted. @en
ILCD's typeOfDataSet for a flow: "Product flow",
"Elementary flow", "Other flow" and so on. A product flow is additionally typed
schema:Product, which is what gives a named product such as an AQUAPANEL board
a resource of its own rather than a fragment of the declaration about it. @en
Upstream's prose on how far the figures represent the region
named by :location — ILCD's descriptionOfRestrictions. The code says where; this
says how well, e.g. whether proxy data stood in where country-specific data were
unavailable. Language-tagged as declared, in every language upstream gives. @en
What was measured. Points at the LCIA method or the flow that
defines it, which is where the indicator's own identity lives — the same code
can be backed by different method datasets across vintages of the standard. @en
An inventory result — primary energy, waste, water, the
EN 15804 reminder flows. ILCD carries these as exchanges rather than as
assessment results; see :lciaResult. @en
An impact assessment result — GWP, acidification, and the rest
of the EN 15804+A2 indicators.
Kept distinct from :lciResult because ILCD sources them differently (LCIAResults
versus exchanges), though for a reader they are the same shape: an indicator, a
module, a number and a unit. @en
Marks a document whose upstream record states no licence at
all. Measured over a sample of twelve processes, eleven declared "Free of charge
for all users and uses" and one declared nothing — so this is a real branch on
real data. Deliberately NOT a dcterms:license: asserting a grant nobody made
would be worse than recording its absence. @en
The ILCD location code exactly as declared. A mixed
vocabulary: ISO 3166 country codes (DE, AT, GB) alongside ecoinvent-style
regions (RER, GLO, EU-27). Kept as a literal as well as a concept because the
two schemes are not reconciled upstream. @en
A search that lists what is in this category. Browsing the
tree gives you the labels; this gives you the things. ÖKOBAUDAT publishes no
membership listing, so the search is the only route. @en
A prior state of a resource, in the sense of RFC 7089. For a
declaration this is the document as one published release carried it. Restated
in the graph as well as in the HTTP headers, because a document that has been
saved or passed on has lost its headers, and "which release is this?" then has
no answer in the bytes. @en
When in the life cycle the figure applies. The set of modules a
declaration reports is NOT fixed: observed declarations carry between one and
fifteen, so nothing may assume a shape. @en
A substring the declaration's name must contain.
Not a word match and not language-specific: ÖKOBAUDAT matches case-insensitive
substrings across EVERY language a record carries, so a German term returns
records whose English name looks unrelated, and a shorter term returns a
superset of a longer one. ORed with :descriptionContains. @en
A substring of the dataset owner's name — in practice the
manufacturer. This is how a manufacturer's declarations are found: ÖKOBAUDAT
names an owner on every declaration but publishes no link from an owner back to
their declarations, so the search is the only route. @en
The flow that IS the declared product.
Reached through ILCD's referenceToReferenceFlow, which carries a
dataSetInternalID — not a UUID, and not an array position. Read as a position it
names a different exchange: measured, that was wrong on a third of the register,
and the wrong answer looks plausible. @en
The programme operator that registered a
declaration — Institut Bauen und Umwelt for most of the register.
Distinct from :dataSetOwner, and frequently a different body. The ROLE is
carried by this property rather than asserted on the organisation, because the
same body is registration authority for one declaration and owner of
another. @en
Whether a data stock is a published release, a variant (an
eLCA import copy, an A1-only cut, project declarations), a test stock, or the
root reference stock. Only releases form the register's timeline; presenting a
test stock as a point in its history would misstate what was published when. @en
How representative a declaration is: specific, average, generic,
representative or template.
Worth reading before using a figure. A specific dataset describes one
manufacturer's product; an average or generic one stands for a class and must
not be attributed to a single supplier. @en
What the product is for — the uses the declaration's figures
are meant to apply to. Worth reading before reusing a figure for a different
application than the one declared. @en
What the declaration actually covers — the manufacturing and
life-cycle steps included in the figures.
This is the ONLY prose in an EN 15804 declaration; everything else is a number
or a code. It also explains why ILCD calls a declaration a "process" when it
plainly is not a manufacturing step: the real steps are described HERE, in a
paragraph, while the modelled process is the product's whole life cycle
collapsed into a single node with one output. @en
One unit of a group, with its factor relative to the group's
reference unit. This is what a unit group is FOR; serving only the unit names
left a document that listed units with no way to convert between them. @en
The unit exactly as ÖKOBAUDAT states it, e.g. "kg CO_(2) eq".
A literal rather than a qudt:unit wherever the quantity is a weighted aggregate
rather than a physical unit: kg CO2 equivalent is a characterisation result, and
QUDT has no honest term for it. Where a real unit IS meant — MJ, kg, m3 — the
resource carries qudt:unit as well, and this label alongside it. @en
The year a declaration's validity lapses, as stated.
Note that ÖKOBAUDAT's SEARCH filter of the same name is not this: it is a lower
bound. See :validUntilAtLeast. Measured over a 1 000-row sample, about 273 of
1 000 declarations are already past this year; they are still served, flagged
with :expired, because a completed assessment cites them. @en
A LOWER BOUND on validity, which is what ÖKOBAUDAT's
validUntil filter actually is — deliberately NOT :validUntil, which on a
declaration is a value.
MEASURED 2026-08-25: the counts fall monotonically as the year rises (2026 →
4 738, 2031 → 757) and the year sets overlap, summing to 17 405 against a
register of 7 028. So validUntil=2030 asks for declarations valid through at
least 2030, not those expiring in 2030 — the reading this wrapper's own
documentation implied until a live test measured it. @en