Add seeAlso term (rdfs:seeAlso) to context for resource discovery

[melvincarvalho]

Closes #19.

Maps a bare seeAlso keyword to rdfs:seeAlso, giving nostr-context documents (including did:nostr) a lightweight, standards-based "follow your nose" predicate for linking to related resources — method docs, the spec, an explorer — without per-document verbosity or a bespoke term.

Change

One term added to context.jsonld:

"seeAlso": {
  "@id": "rdfs:seeAlso",
  "@type": "@id"
}

• Reuses rdfs:seeAlso (the rdfs prefix is already mapped) rather than minting a nostr: term.
• @type: @id makes values proper IRI node-links, so documents stay clean:

"seeAlso": "https://init-agent.com/SKILL.md"

• No @container: @set, so a bare string is valid; an array still works for multiple targets.
• No collision with https://www.w3.org/ns/cid/v1 (it's @protected but does not define seeAlso).

JSON validated. Rationale and alternatives considered (service, didDocumentMetadata, minting a nostr: term) are in #19.

[Copilot]

Pull request overview

Adds a seeAlso keyword to the JSON-LD context, mapping it to rdfs:seeAlso so Nostr-context documents can link to related resources using a standards-based predicate.

Changes:

• Add "seeAlso": { "@id": "rdfs:seeAlso", "@type": "@id" } to context.jsonld.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[melvincarvalho]

seeAlso is intentionally scoped to context.jsonld only.

The vocab artifacts (vocab.json, vocab.jsonld, index.html) define nostr-owned terms — each as an ontology subject with rdfs:label/domain/range. context.jsonld additionally carries mappings for reused external terms. seeAlso is rdfs:seeAlso — external, exactly like the existing comment / domain / label / title / isDefinedBy / range aliases, which likewise have a context mapping but no vocab definition.

So there's no mirror to sync:

• The consumer @context map isn't duplicated in the vocab files — those embed a separate authoring context (dc:title, rdfs:comment, domain, range…), a different term set. The nostr terms appear in their bodies as definitions, not as @context mappings.
• There's no build/generation step (package.json has no build), and nothing references context.jsonld internally — the published vocab page is driven by the embedded vocab, independent of the context file.

Adding seeAlso to the vocab would re-document an external RDFS term and break the convention that the vocab defines only nostr-owned terms. No drift.