MIF is moving to a dedicated organization (modeled-information-format)

[zircote]

MIF (Modeled Information Format) will soon move from its current home at
zircote/MIF to a dedicated GitHub organization, modeled-information-format.
The move is administrative. The specification, its version, and its semantics
do not change as a result.

This announcement exists so that consumers can prepare in advance. Nothing
breaks on the day of the transfer, but several pointers are worth updating at
your convenience.

Why the move

MIF has outgrown a personal namespace. A dedicated organization gives the
project clearer governance, room for additional maintainers, and a stable home
for the specification, the conformance suite, and the tooling. The MIF mark is
retained. The working expansion remains Modeled Information Format.

What does not change

• The specification. Spec v1.0.0 and its content model are unchanged. The
  base knowledge types (semantic, episodic, procedural), typed
  relationships, provenance, trust tiers, and validity semantics are identical.
• OKF (Open Knowledge Format) compliance. MIF remains an OKF-compliant
  superset, pinned to OKF v0.1.
• Namespace and schema identifiers. Any $id, JSON-LD context, or namespace
  URI you depend on is unaffected by the repository move.
• The documentation site. mif-spec.dev remains the canonical docs URL.
• Your existing bundles. No migration of MIF content is required. Bundles
  valid today remain valid.

What changes (and what to do)

• The canonical repository URL becomes
  github.com/modeled-information-format/MIF (final organization-relative path
  confirmed at transfer time).

• GitHub redirects are automatic. After the transfer, GitHub forwards the
  old URLs (clones, links, issues, pull requests, discussions) to the new
  location. Existing git remote settings continue to function through the
  redirect.

• Update your git remotes when convenient. Redirects are a safety net, not a
  permanent guarantee. Run:

  git remote set-url origin git@github.com:modeled-information-format/MIF.git
  

• Update hard-coded links in your own documentation, dependency manifests,
  CI configuration, and bookmarks to point at the organization.

• Stars, watchers, forks, issues, pull requests, and this discussion history
  transfer with the repository. You do not need to re-star or re-subscribe.

Timeline

The transfer is planned for the near term. A follow-up comment on this
discussion will confirm the exact date and the final repository path before the
move, and a second comment will confirm completion afterward. Watch this thread
or the repository for those updates.

Questions

If the move affects an integration, a downstream tool, or an automation you
maintain, raise it on this thread before the transfer. Surfacing a concern early
is far cheaper than discovering it after the fact.