Date: Thu, 28 Mar 2024 11:12:10 +0000 (UTC) Message-ID: <696227928.409.1711624330338@[3.220.22.64]> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_408_631945115.1711624330338" ------=_Part_408_631945115.1711624330338 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The template design requirements include:
Requirement D.1: Placeholders for values
Templates should allow for placeholders (= i.e. slots) to be specified, wherever a concept, expression, token or attri= bute value can be used.
Requirement D.2 Slot names
Templa= tes should allow each slot to be assigned a name, enabling the slot to be referenced outside the slot (e.g. fo= r specifying input data).
Requirement D.3 Slot types
Template slots should be able to be const= rained to only permit a specific type of value (e.g. only allowing precoord= inated concepts to replace a slot).
Requirement D.4: Template value constraints
Templates slots should be able to be cons= trained to only permit values from a specific value set (e.g. only allowing= expressions that satisfy a given expression constraint).
Requirement D.5: Repeatability of template components= p>
Templates should support a way of indicat= ing how many times each focus concept, relationship group and attribute val= ue pair can be repeated when the template is populated.