{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://openeik.org/schemas/0.1/proposed/railings/index.json",
  "$comment": "Proposed for OpenEik 0.2: Part II, 12.2.1, a hosted railing's profile. Written by hand from Part II, 12.2.1, not generated: tools/generate-schemas.mjs keeps this folder and lists none of it in index.json, and the element schema of 0.1 still asks every element for its profile. A validator lets such a railing leave it out, and warns of it where it is deprecated, only when asked for the proposal (@openeik/tools: proposals [\"railings\"]).",
  "title": "A hosted railing's profile, proposed for 0.2",
  "description": "The index of the proposal railings (Part II, 12.2.1, proposed for 0.2). It is a schema that asserts nothing: its member x-eik-proposal names the member of a record of 0.1 that the proposal makes optional, and that it deprecates, each by its record, its categories, its path and when it applies, and says that the proposal adds no file and no member. Schema paths are relative to https://openeik.org/schemas/0.1/.",
  "x-eik-proposal": {
    "name": "railings",
    "part": "II",
    "status": "proposed for 0.2",
    "files": [],
    "optional": [
      {
        "record": "element",
        "categories": [
          "railing"
        ],
        "path": [
          "profile"
        ],
        "when": "it names a host (hostId) and no side (railing.side): on the outline of a slab or a shaft, on a wall's top or along a slab edge element",
        "section": "12.2.1",
        "rules": [
          "1",
          "2"
        ]
      }
    ],
    "deprecated": [
      {
        "record": "element",
        "categories": [
          "railing"
        ],
        "path": [
          "profile"
        ],
        "when": "its host is a slab, a shaft, a wall or a slab edge element: its line is derived (Part IV, 11.2)",
        "section": "12.2.1",
        "rules": [
          "1",
          "2"
        ],
        "code": "railing-profile"
      }
    ]
  }
}