Versioning: package.json is stale and the ontology carries no version metadata

[melvincarvalho]

Observations

While adding the seeAlso term (#19, #20) it became clear the repo has no working versioning convention:

• package.json version is 0.0.17 and was not bumped when changes merged — it's effectively vestigial. Nothing consumes it (the context is served at the stable URL w3id.org/nostr/context).
• No git tags / releases.
• The ontology is unversioned — the owl:Ontology node (nostr:) has only title/description, no owl:versionInfo or dcterms:modified.
• ("@version": 1.1 in context.jsonld is the JSON-LD spec version, not a schema version.)

Immediate action

Bump package.json 0.0.17 → 0.0.18 as a consistency marker for the recent context change (separate PR).

Worth deciding

For a published vocabulary, package.json isn't the meaningful signal. The more honest, machine-readable mechanisms are:

1. owl:versionInfo (and/or dcterms:modified) on the owl:Ontology node — recommended.
2. A versioned context IRI (e.g. /nostr/context/v1) — heavier; only if breaking-change isolation is needed.

Proposal: adopt owl:versionInfo on the ontology going forward, and keep package.json in sync as a convenience. Opening for discussion before changing the ontology.