Sources & relationship vocabulary
The catalogue, gallery and knowledge graph are generated together from one normalized dataset. The checked snapshot includes complete creator searches and a separate contributor search. The owner-supplied activity ledger adds dated occurrences and personal roles to the graph. Activities and research works use distinct identities. The existing bibliography beyond Zenodo is retained, and the verified o-bib article has been added. Download the catalogue, graph, semantic JSON-LD or BibTeX.
Identities and versions
A work represents a version family. Its record ID, version DOI and concept DOI are distinct. Citations describe the displayed version; the concept DOI opens the complete version history. Publication dates keep their original day, month or year precision. An unverified date remains unknown.
People with an ORCID use that identity. Names without ORCID are local to their source record; identical names alone do not establish an identity. Three confirmed exceptions identify Lukas as creator in the DALIA curation concept, hu-berlin-bundle and biblatex-arthistory-bonn records. The ProjectMember role in record 20641349 remains a contribution, separate from authorship. Affiliations describe the source record and do not assert current employment.
Reading relationships
Every arrow runs from its subject to its object. Inspect its evidence to see the source, metadata field, role, original reference and statement source version.
| Relationship | Meaning and evidence |
|---|---|
| undertakenBy | Activity → person, with the exact role from the personal ledger; it does not establish publication authorship. |
| atEvent | Activity → the dated event occurrence recorded in the ledger. |
| recordedIn | An item → its explicit content collection, including activities, skills, projects and tours. |
| authoredBy | Work → person, from the ordered creator metadata. |
| contributedBy | Work → person, retaining the actual contributor role. |
| taggedWith | Item → topic, using original keywords, preserved bibliography tags, documented exact aliases or reviewed source passages. Editorial associations retain a quote, source and version; original keywords remain unchanged. |
| explains | Work or tour → framework, with an explicit editorial source and explanation. |
| usesTool | Item → tool, supported by explicit methods, executable source or recorded responsibilities. Precomputed browser examples name the original build tools; they do not claim native execution in the browser. |
| archivesProject | Work → maintained project, with a confirmed repository and the original archived version kept distinct. |
| associatedWithEvent | Work → event, from published meeting metadata. It does not assert who presented. |
| aboutTool | Work, skill or material → a tool it explicitly discusses. Exact keyword aliases establish coverage, never tool use. |
| teachesTool | Published guide → the tool taught by its stated objectives and examples. |
| usesDataset | Learning material → the concrete dataset used, retaining its pinned version DOI. |
| hasMaterial | Skill, project or activity → an explicitly associated work or learning example. It does not establish who presented it. |
| hasSkill / worksOn | Person → a practice, tool or area explicitly recorded in the owner’s profile. No proficiency score is inferred. |
| hasEducation / awardedBy | Person → recorded qualification → the named awarding institution, preserving the original timeframe. |
| heldRole / atOrganization | Person → recorded professional role → organization, with original dates and responsibilities. Historical affiliations alone never create employment assertions. |
| teaches | Person → teaching-material overview, with the instructor/helper role as recorded. |
| containsItem | Website overview → a real item or populated content collection. |
| linksTo | Explicit guide-to-guide hyperlink. The original reference is retained, including older /tours/ prefixes; canonical targets come from the verified directory. |
| appliesFramework / isBasedOn | Self-check → the implemented framework; checked data experiment → its exact source tour and executable source version. |
| Other Zenodo relationships | Keep the original relation name and direction, e.g. isDerivedFrom, supplements or isSupplementedBy. Concrete version references are retained even when the visual endpoint is grouped into a work family. |
Evidence classes are imported metadata, editorial mapping and rule-derived. The topic rule keyword-alias-v1 maps exact, case-insensitive aliases to a controlled term. All unmatched keywords remain accessible as topics. Title similarity is never used to invent relationships.
Semantic export
The JSON-LD uses Schema.org CreativeWork, Person, DefinedTerm, Event, LearningResource, Project, SoftwareApplication, Action, Collection, EducationalOccupationalCredential, Role, Organization and Course. Authorship maps to schema:author, contributions to schema:contributor, and topic links to schema:about. RDF statements record individual directed relationships and their evidence, with prov:wasDerivedFrom linking the source.
Our namespace is https://lukascbossert.de/research/vocab#. These identifiers are stable:
| Local term | Definition |
|---|---|
| recordedIn / containsItem | Explicit membership of the website and its populated content collections. |
| presentsWork | A manually verified activity-to-work link; never inferred from a similar title. |
| activityDate / activityEndDate | Day-precision occurrence dates, preserving the original interval. |
| activityRole / activityType | Original personal role and occurrence type from the ledger. |
| recordedStatus | Status as supplied, without inferring completion from elapsed dates. |
| archivesProject | Links a specific software archive to its maintained project. |
| usesTool / aboutTool / teachesTool | Documented use, topical coverage and instructional coverage remain distinct. |
| usesDataset | Explicit dataset use with the concrete original version reference. |
| hasMaterial | Documented material association without inferring a presentation role. |
| hasSkill / worksOn | Owner-recorded capabilities and areas of work; mapped to Schema.org knowsAbout. |
| hasEducation | Person → qualification; mapped to Schema.org hasCredential. |
| awardedBy | Qualification → named institution. |
| heldRole / atOrganization | Recorded professional role and institution. |
| teaches | Explicitly recorded teaching role. |
| linksTo | Literal published hyperlink with a reviewed canonical target. |
| appliesFramework | Local interactive resource implementing a published framework. |
| isBasedOn | Exact source-guide association; mapped to Schema.org isBasedOn. |
| localPage / contentFile | Local page URI and the Markdown file backing the item. |
| recordedTimeframe / recordedStart / recordedEnd | Original education/employment time strings, without invented date components. |
| explains | Explicitly documented explanatory coverage of a framework. |
| associatedWithEvent | Meeting association from source metadata. |
| zenodo/{relation} | Original Zenodo/DataCite relation, with unchanged direction. |
| authorsInOrder | RDF ordered list of the creators in the displayed source version. |
| datePrecision | The preserved publication date precision: year, month, day or unknown. |
| displayedVersion | DOI of the specific version shown in the catalogue. |
| evidence | Serialized evidence attributes: source field, class, rule and reason. |
| role | Actual contributor role from the source. |
| originalRelation | Unmodified source relation type. |
| originalReference | Unmodified target record, DOI or URL in the source statement. |
| sourceVersion | DOI of the source version making the relationship statement. |
Sources and known uncertainties
Zenodo Records API and search documentation define the import. The catalogue header reports the snapshot retrieval date. Complete pagination, published-version markers and latest-version links are validated before replacing the local source snapshot. Normal visits never call the Zenodo API.
The former entry “Eins für alles: Der Einsatz von Emacs im Forschungszyklus” is retained as an undated manuscript. Its former “NN (forthcoming) 2025” assertion is preserved in the source bibliography; a published venue or date has not been verified. An unavailable related Zenodo record (14886334, HTTP 410) remains a reference with its original identifier.
CTAN lists archaeologie 2.5.1, released 4 July 2026, and links the Codeberg repository. The archived Zenodo version is cited with its own version DOI; the current CTAN package release is a separate fact.
The SHAPE self-check reproduces the original questions and criteria from version 0.9.11, with attribution and the original PDF. The experiment uses the published ROOT & SHAPE tour, its native toolchain and independent reference calculations. Preview images come from Zenodo’s supplied first-page thumbnails; each links to its original licensed material. Other entries use typographic cards.
Personal activity ledger
The supplied Org ledger contains 61 tagged activity headings. Its generated summary tables are views of those headings and are not imported again. Shared preparation-note identifiers do not merge separate occurrences. Organization, presenting, coauthorship, teaching and attendance remain distinct roles. Personal participation dates are separate from an event’s longer duration; the 2025 shell course records two teaching days, 3 and 7 November.
Activities enter the graph as Schema.org Actions linked to their agent and event, and to the recorded activity collection. They do not increase the publication count. Event nodes preserve each explicitly recorded date or interval; broader conference or series durations are not guessed. Source classification is an owner-provided editorial record, with public links where supplied. Internal Org IDs are not public links or exported identifiers.
The EASST 2026 attendance entry retains its supplied “in-progress” status and is flagged on the activity page because the recorded dates have passed. No automatic completion status or title-based link to a publication is asserted.
File-backed website
The homepage is the knowledge graph. The separate Toha profile is
compiled from the same canonical skills, qualifications, professional roles and
projects. Each node has a Markdown file under content/knowledge/ and a readable
page in the knowledge library. Imported metadata is separate from
editable prose and explicit editorial connections. Ordinary builds read those
files; only an explicit source synchronization refreshes imported fields.
All currently listed 19 learning tours are represented as individual nodes, with their HTML/PDF links and checked source hashes. The visualization-comparison tour explicitly uses the Titanic archive at version DOI 10.5281/zenodo.22983324. The version reference remains visible even though the graph endpoint groups the work’s version family. ROOT workshop methods, SPARQL-based network analyses, profile responsibilities and original material links supply further reviewed connections. No relationship is generated solely from similar titles.