gx prefix maps to dead Graphite/Synaptica namespace instead of Gaia-X

[jdsika]

Problem

The merged context maps the gx prefix to a dead Synaptica/Graphite namespace, while the active and widely-used Gaia-X Trust Framework ontology uses gx: as its canonical prefix.

Source	Prefix	Namespace	Status
prefixmaps (from prefix.cc)	gx	https://graphite.synaptica.net/extension/	Unreachable — no RDF vocabulary served
prefixmaps (from prefix.cc)	gax	http://w3id.org/gaia-x/core#	Dead — returns HTTP 404
Gaia-X official ontology	gx	https://w3id.org/gaia-x/development#	Active — persistent w3id.org URL

Evidence

gx → Graphite/Synaptica (current mapping, inactive)

• Synaptica was acquired by Squirro — the company still exists but has rebranded.
• The Graphite product is still marketed at squirro.com, but the namespace URL https://graphite.synaptica.net/extension/ is unreachable — no RDF vocabulary or ontology is published at that URL.
• The mapping originates from prefix.cc and was registered by a community user with no formal ownership.

gax → old Gaia-X (dead)

• http://w3id.org/gaia-x/core# returns HTTP 404. This was an earlier Gaia-X namespace that has been superseded.

gx → Gaia-X (should be canonical)

• Gaia-X is a major European data infrastructure initiative.
• The official Gaia-X ontology uses @prefix gx: <https://w3id.org/gaia-x/development#> — documented in:
  • Gaia-X Architecture Document 25.05
  • Gaia-X Trust Framework Implementation
  • Gaia-X Ontology npm package
  • Gaia-X Lab Compliance GitLab
• The ontology is published via persistent w3id.org identifiers and is actively maintained (24.04, 25.05 releases).
• The ontology is built with LinkML and published as SHACL shapes, JSON-LD context, and OWL — directly relevant to this ecosystem.
• The Gaia-X Trusted Shape Registry actively uses @prefix gx: in its published SHACL shapes.

Root cause

Both gx and gax originate from prefix.cc, which uses a community vote-based system for conflict resolution. The gx → Graphite mapping was presumably registered first. We are working on correcting this upstream at prefix.cc (see below).

Proposed resolution

1. Upstream fix at prefix.cc: We are proposing the correct gx → https://w3id.org/gaia-x/development# mapping and requesting community votes (tracked separately).
2. Curated override: If the prefix.cc fix takes time, consider adding gx: https://w3id.org/gaia-x/development# to linked_data.curated.yaml as a tie-breaker, similar to the approach used for W3C standard prefixes in bioregistry changes have broken the merged prefix map #70 / fix: add W3C/OGC standard prefixes to linked_data curated context #81.
3. Remove dead gax: The gax → http://w3id.org/gaia-x/core# mapping should be marked as deprecated or removed, as the namespace is a dead 404 URL.

Related

• Discovered while investigating rdflib/prefixmaps alignment for linkml/linkml#3446 (--normalize-prefixes flag)
• Related to bioregistry changes have broken the merged prefix map #70 / fix: add W3C/OGC standard prefixes to linked_data curated context #81 (W3C standard prefix casing fixes)

[jdsika]

Status Update

1. prefix.cc upstream fix ✅

The gx prefix at prefix.cc now correctly resolves to https://w3id.org/gaia-x/development# (verified via http://prefix.cc/gx.file.json). The Graphite/Synaptica mapping has been outvoted.

2. Bioregistry registration ⏳

PR to add gx as a new prefix to the Bioregistry/Semantic Farm: biopragmatics/bioregistry#1939 — awaiting final review.

3. Curated override in linked_data.curated.yaml

With the prefix.cc fix in place, the next make etl / data refresh should pick up the correct gx mapping automatically. A curated override may no longer be necessary, but could still be added as a safety net.

4. Dead gax mapping

gax → http://w3id.org/gaia-x/core# remains in prefix.cc (returns 404). We downvoted it but it hasn't been removed yet.

[jdsika]

Release request: v0.2.8

With PR #81 now merged (W3C/OGC standard prefixes) and the prefix.cc gx fix live upstream, could we run make etl to regenerate merged.csv and cut a v0.2.8 release?

This would unblock linkml/linkml#3446, which currently hardcodes a static prefix map and needs to be refactored to use prefixmaps as the canonical source (per @matentzn's review feedback).

@kevinschaper