feat: initial commit

.github/workflows/build.yml

@@ -0,0 +1,50 @@
+name: build
+
+on:
+  push:
+    branches: [ main ]
+    tags:
+      - 'v*'
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+      with:
+        token: ${{ github.token }}
+        submodules: true
+
+    - uses: actions/upload-artifact@v3
+      if: startsWith(github.ref, 'refs/tags/v') || github.ref == 'refs/heads/main'
+      with:
+        name: package
+        path: |
+          concepts
+          *.meta.yaml
+
+  release:
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+    - uses: actions/download-artifact@v3
+      with:
+        name: package
+
+    - name: Display structure of downloaded files
+      run: ls -R
+
+    - name: Compress files
+      run: zip -9 -r package.zip ./*
+
+    - name: Upload release
+      id: upload-release-asset
+      uses: softprops/action-gh-release@v1
+      with:
+        body: Automatic release of ${{ github.ref }}
+        files: |
+          package.zip

.gitignore

@@ -0,0 +1,2 @@
+# Side effect of tc204-termbase or Relaton?
+db

README.adoc

@@ -0,0 +1,12 @@
+== ISO/TC 204 Geolexica Glossarist database
+
+This repository contains the latest snapshot of ISO/TC 204 Geolexica glossary in YAML format.
+
+This repository is managed by Glossarist desktop app and is built into
+https://github.com/geolexica/isotc204.geolexica.org[ISO/TC 204 Geolexica website],
+availabe at https://geolexica.org/.
+
+NOTE: The YAML data in this repository is not yet an authoritative data source.
+Currently, data stored in this structure is imported from the latest published
+ISO/TC 204 Multi-Lingual Glossary of Terms spreadsheets.
+In the future, all data will be managed through the Glossarist desktop application.

branding.yaml

@@ -0,0 +1,2 @@
+name: ISO/TC 204 Geolexica
+symbol: iso-logo-blue.png

concepts/concept-3.1.1.1.yaml

@@ -0,0 +1,15 @@
+---
+termid: 3.1.1.1
+term: entity
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: entity
+  definition:
+  - content: concrete or abstract thing that exists, did exist, or can possibly exist,
+      including associations among these things
+  notes: []
+  examples:
+  - content: "{{person,Person}}, object, event, idea, process, etc."
+  language_code: eng

concepts/concept-3.1.1.2.yaml

@@ -0,0 +1,14 @@
+---
+termid: 3.1.1.2
+term: immaterial entity
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: immaterial entity
+  definition:
+  - content: "{{entity}} that does not occupy three-dimensional space"
+  notes: []
+  examples:
+  - content: Idea, process, organization, etc.
+  language_code: eng

concepts/concept-3.1.1.3.yaml

@@ -0,0 +1,15 @@
+---
+termid: 3.1.1.3
+term: material entity
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: material entity
+  definition:
+  - content: "{{entity}} that occupies three-dimensional space"
+  notes:
+  - content: All material entities have certain characteristics that can be described
+      and therefore this concept is important for ontology purposes.
+  examples: []
+  language_code: eng

concepts/concept-3.1.1.4.yaml

@@ -0,0 +1,13 @@
+---
+termid: 3.1.1.4
+term: non-biological entity
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: non-biological entity
+  definition:
+  - content: "{{material entity}} that is not and has never been a living organism"
+  notes: []
+  examples: []
+  language_code: eng

concepts/concept-3.1.1.5.yaml

@@ -0,0 +1,13 @@
+---
+termid: 3.1.1.5
+term: biological entity
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: biological entity
+  definition:
+  - content: "{{material entity}} that was or is a living organism"
+  notes: []
+  examples: []
+  language_code: eng

concepts/concept-3.1.1.6.yaml

@@ -0,0 +1,13 @@
+---
+termid: 3.1.1.6
+term: person
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: person
+  definition:
+  - content: "{{biological entity}} that is a human being"
+  notes: []
+  examples: []
+  language_code: eng

concepts/concept-3.1.10.1.yaml

@@ -0,0 +1,21 @@
+---
+termid: 3.1.10.1
+term: data concept
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: data concept
+  definition:
+  - content: "{{data element}}, {{class}}, {{value domain}}, {{data frame}}, {{message}}
+      or {{interface dialogue}} defined, at a minimum, with an unambiguous identifier
+      and a definition"
+  notes:
+  - content: In order to exchange a value corresponding to a data concept, more information
+      than an identifier, a name and a definition can be needed. For a property, a
+      data type is needed. Depending on the kind of property, other data elements
+      such as unit of measure, and language, can be needed as well. The additional
+      information can be given in the {{data dictionary}}, in a data specification
+      that references the data concept or associated with the data themselves.
+  examples: []
+  language_code: eng

concepts/concept-3.1.10.2.yaml

@@ -0,0 +1,14 @@
+---
+termid: 3.1.10.2
+term: meta-attribute
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: meta-attribute
+  definition:
+  - content: documenting characteristic of a {{data concept}} that is stored in a
+      {{data dictionary}}
+  notes: []
+  examples: []
+  language_code: eng

concepts/concept-3.1.10.3.yaml

@@ -0,0 +1,20 @@
+---
+termid: 3.1.10.3
+term: data dictionary
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: data dictionary
+  definition:
+  - content: collection of {{data concept,data concepts}} that allows lookup by {{entity}}
+      identifier
+  notes: []
+  examples: []
+  language_code: eng
+  sources:
+  - type: authoritative
+    origin:
+      ref: ref_17,ISO 22745-2:2010,B.2.16
+    modification: '"collection of data dictionary entries..." replaced with "collection
+      of data concepts...".'

concepts/concept-3.1.10.4.yaml

@@ -0,0 +1,21 @@
+---
+termid: 3.1.10.4
+term: data concept registry
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: data concept registry
+  definition:
+  - content: electronic {{data dictionary}} that follows precise documented rules
+      for the registration and management of stored {{data concept,data concepts}}
+  notes:
+  - content: The data concept registry contains {{meta-attribute,meta-attributes}}
+      about data concepts in terms of their names and representational forms as well
+      as the semantics associated with the data concepts. A data concept registry
+      may contain metadata that assists information interchange and re-use, both from
+      the perspective of human users and for machine-interpretation of data concepts.
+  - content: A data concept registry typically includes advanced features for adding
+      retrieving, and working with its contents.
+  examples: []
+  language_code: eng

concepts/concept-3.1.11.1.yaml

@@ -0,0 +1,18 @@
+---
+termid: 3.1.11.1
+term: data element
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: data element
+  definition:
+  - content: unit of data that is considered in a given context to be indivisible
+      and which includes an unambiguous representational form
+  notes:
+  - content: This definition states that a data element is “indivisible” in a given
+      context. This means it is possible for a data element considered indivisible
+      in one context [e.g. {{location}}] to be divisible in another context (e.g.
+      latitude, longitude, and elevation).
+  examples: []
+  language_code: eng

concepts/concept-3.1.11.2.yaml

@@ -0,0 +1,26 @@
+---
+termid: 3.1.11.2
+term: 'class '
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: 'class '
+  - type: expression
+    designation: "*object class*"
+  definition:
+  - content: set of ideas, abstractions or things in the real world that are identified
+      with explicit boundaries and meaning and whose properties and behaviour follow
+      the same rules
+  notes:
+  - content: Some ISO/TC 204 documents use the term "object class" for consistency
+      with <<ISO_11179_1>>, but within ITS, the term "class" is more generally understood.
+  - content: This is semantically equivalent to a "class" as used within UML (<<ISO19505_2_2012,ISO19505-2:2012>>).
+  examples: []
+  language_code: eng
+  sources:
+  - type: authoritative
+    origin:
+      ref: ref_5,clause 3.3.18
+    modification: term changed to from "object class" to "class" and Notes to entry
+      added.

concepts/concept-3.1.11.3.yaml

@@ -0,0 +1,13 @@
+---
+termid: 3.1.11.3
+term: value domain
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: value domain
+  definition:
+  - content: a set of permissible values
+  notes: []
+  examples: []
+  language_code: eng

concepts/concept-3.1.11.4.yaml

@@ -0,0 +1,17 @@
+---
+termid: 3.1.11.4
+term: data frame
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: data frame
+  definition:
+  - content: specific grouping of {{data element,data elements}} that describes information
+      of interest through a useful grouping of more atomic properties about one or
+      more {{class,classes}}
+  notes:
+  - content: The grouping can be a set, sequence or a choice.
+  - content: A data frame can contain other data frames.
+  examples: []
+  language_code: eng

concepts/concept-3.1.11.5.yaml

@@ -0,0 +1,14 @@
+---
+termid: 3.1.11.5
+term: message
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: message
+  definition:
+  - content: grouping of {{data element,data elements}}, {{data frame,data frames}},
+      or data elements and data frames that is used to convey information
+  notes: []
+  examples: []
+  language_code: eng

concepts/concept-3.1.11.6.yaml

@@ -0,0 +1,20 @@
+---
+termid: 3.1.11.6
+term: interface dialogue
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: interface dialogue
+  - type: expression
+    designation: "*dialog*"
+  - type: expression
+    designation: "*dialogue*"
+  definition:
+  - content: bi-directional communication sequence between two parties in accordance
+      with predetermined protocols
+  notes:
+  - content: The term "dialog" represents the American English spelling.
+  - content: The term "dialogue" can be used when the interface context is known.
+  examples: []
+  language_code: eng

concepts/concept-3.1.12.1.yaml

@@ -0,0 +1,19 @@
+---
+termid: 3.1.12.1
+term: use case
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: use case
+  definition:
+  - content: description of the behavioural requirements of a {{system}} and its {{interaction}}
+      with a {{user}}
+  notes: []
+  examples: []
+  language_code: eng
+  sources:
+  - type: authoritative
+    origin:
+      ref: ref_21,clause 3.15
+    modification: Note 1 to entry removed.

concepts/concept-3.1.12.2.yaml

@@ -0,0 +1,21 @@
+---
+termid: 3.1.12.2
+term: scenario
+eng:
+  terms:
+  - type: expression
+    normative_status: preferred
+    designation: scenario
+  - type: expression
+    designation: use case scenario
+  definition:
+  - content: "<use case> description of the sequence of events from the {{user,user's}}
+      perspective to perform a task in a specified context"
+  notes: []
+  examples: []
+  language_code: eng
+  sources:
+  - type: authoritative
+    origin:
+      ref: ref_20,ISO/IEC 25062:2006,A.17
+    modification: ''