Add Academy NTO for the Bardioc Academy

[boosc]

What

A new NTO/Academy ontology for the Bardioc Academy: courses and their
dependencies, learner enrollment and progress, verifiable certificates, the
catalogue and its tracks. Background: Almato offers courses via the Area9 LMS;
the Bardioc graph is the source of truth for users, catalogue, progress,
ratings and certificates.

Scope of the change

• 1 new entity -- ogit.Academy:Enrollment: a reified learner<->course
  relationship carrying the cmi5 lifecycle status, the xAPI Result fields, a
  resume pointer, lifecycle timestamps and the per-course licence window. It is
  reified because OGIT edges cannot carry attributes (precedent: ogit:Rating).
• 4 new verbs -- enrolledIn (Enrollment->Course), resultedIn
  (Enrollment->Certificate), certifies (Certificate->Course), supersedes
  (Course->Course, version/re-training). With these, no Academy edge uses the
  generic ogit:relates.
• 45 new ogit.Academy attributes -- course/catalogue metadata, certificate
  VC 2.0 / OB 3.0 fields, enrollment/xAPI Result fields.
• Extensions to existing core types (additions only, no removals):
  ogit:Course, ogit:Certificate, ogit:Person, ogit:Catalog,
  ogit:Organization, ogit:Rating, ogit.Auth:Account -- each gains
  allowed-edge entries and (where noted) optional attributes. Tracks reuse
  ogit.ClassificationStandard; badges reuse ogit.Forum:Award; prior knowledge
  reuses ogit.HR.Recruiting:Skill.

Standards alignment

Designed as a lossless superset of the variable mandatory cores of Open Badges
3.0 / W3C Verifiable Credentials 2.0 (certificates), xAPI (IEEE
9274.1.1-2023) + cmi5 (learning records) and schema.org Course (catalogue).
The export mapping and a conformance-deviation table (the few
standard-mandatory fields that cannot be enforced on the shared SGO core types,
enforced at the application layer instead) are documented in
NTO/Academy/README.md.

Conventions

• TTL comments/labels in English; dcterms:creator "Almato AG" on all new
  artifacts; README.md in the new NTO directory; every ogit:allowed target is
  a concrete vertex type; fixed-value attributes carry ogit:validation-type "fixed" + ogit:validation-parameter.

Validation

• rdflib Turtle parse: all new + edited files parse cleanly.
• Cross-reference check: every OGIT identifier referenced by the new/edited files
  is defined in the repository.

Open question

dcterms:creator is set to "Almato AG" (post arago->Almato merger). Please
confirm the preferred creator/owner string for new contributions, or advise if a
different owner attribution is expected.

🤖 Generated with Claude Code

https://claude.ai/code/session_018ehGgXoZabSmS3Hp5F4mGx