Saltar al contenido

Registro de cambios

Todo cambio notable de la especificación, del más reciente al más antiguo. Se lee del repositorio en vez de transcribirse, así que esta página y la versión que describe no pueden contradecirse.

  1. Sin publicar

    Cambiado

    • 0.1 is no longer labelled a draft. The introduction's DRAFT statement is removed and every section's status is normative. The specification continues to change through the RFC process, which is what the introduction now says instead — the label was the disclaimer, not the mechanism. §8.1's rule is untouched: a release candidate still becomes normative only after a publisher ships it publicly. 0.1 went from draft to normative without an RC stage, so the rule does not bind this transition. It does mean the spirit of that clause — the spec never outruns its implementers — is carried by the registry rather than by a label from here on.
  2. 0.1.0-draft

    Agregado

    • Initial public draft, transformed from the founding design record (docs/context/PROTOCOL_DESIGN.md, including Addendum A's mesa técnica integration — HXL on-ramp §1.3, official-channels link-out §7.1, CAP reference and quantity_covered reservation §8.5, place-id shape harmonization §5.2).
    • Sections §0–§8 + non-normative Appendix A (decision log + the implementability walkthrough).
    • Schemas 0.1: manifest.schema.json, place-feed.schema.json (JSON Schema 2020-12, absolute $ids).
    • Five worked examples: 2 valid, 3 invalid with designed error messages (the validator's acceptance fixtures).
    • Profiles: Core, Extended. Vocabulary: the equivalence dictionary.
    • RFC process seeded: template + RFC-0001 (the founding agreement, draft).

    Status: DRAFT under working-group review — nothing is normative yet.

El validador y la skill

Aparecerán en esta línea de tiempo cuando publiquen versiones. Mientras tanto no se listan como carriles vacíos: una línea de tiempo con filas en blanco se lee como un proyecto que se detuvo, no como uno que todavía no ha comenzado.

RFC