Skip to content

Prepare web redirects for Croissant vocabulary namespace/URIs, spec, and documentation for 1.1 version #935

@kepae

Description

@kepae

Breaking out this issue from #923 discussion. Aside from handling human- and machine-readability of Croissant vocabulary, there need to be redirects that will handle lookups to Croissant URIs, handling both the current 1.0 and upcoming 1.1 versions. This would successfully resolve terms under the mlcommons.org/croissant namespace (such as http://mlcommons.org/croissant/Field, which yields a 404).

The strawman describes using a one-page "hash" namespace:

Strawman suggestion:

  1. Create a redirect from mlcommons.org/croissant/1.0/term to mlcommons.org/croissant/1.0#term
  2. Same thing for 1.1: mlcommons.org/croissant/1.1/term to mlcommons.org/croissant/1.1#term
  3. Redirect mlcommons.org/croissant/term to mlcommons.org/croissant/1.0/term until we launch 1.1 and then to mlcommons.org/croissant/1.1/term

Originally posted by @benjelloun in #923

For now, I propose just serving the current markdown spec from the mlcommons.org/croissant namespace to make use of what we have, and can improve later.

MVP steps (discussed a little in #923 (comment)):

  • Serve current markdown spec from mlcommons.org/croissant/1.0 (or setup re-direct)
  • Make sure redirects follow default versions and keep terms follow to proper anchors per above:
    mlcommons.org/croissant/term -> mlcommons.org/croissant/1.0#term
  • If desired, resolve the bare namespace – mlcommons.org/croissant – to the spec, rather than the working group (currently goes to https://mlcommons.org/working-groups/data/croissant/ )

If we really wanted to do something quick, we could just handle redirects directly for all Croissant terms in the RDF, e.g. croissant:FileSet. however the docs are served:
https://docs.mlcommons.org/croissant/docs/croissant.ttl

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions