{
  "test": {
    "id": "tests/1.0/ordered/common-generic-extraction",
    "directory": "tests/1.0/ordered/common-generic-extraction",
    "manifestPath": "tests/1.0/ordered/common-generic-extraction/manifest.ttl",
    "scenarioPath": "tests/1.0/ordered/common-generic-extraction/scenario.yaml",
    "expectedPath": "tests/1.0/ordered/common-generic-extraction/expected/events.ndjson",
    "iri": "https://www.pieter.pm/ldes-client-conformance-test-suite/1.0#ordered-common-generic-extraction",
    "title": "Generic member extraction in ordered mode",
    "description": "The member extraction algorithm is not mode-specific, so the comprehensive generic-extraction case is also exercised in ordered mode: focus-node discovery scoped to the event stream, the default-graph subject star, all quads in the graph named by the member IRI, recursive blank nodes with cycle protection, and no emission of unrelated subjects or other streams' members. LDES 1.0 permits a client that implements ordered mode only, and this fixture lets such a client demonstrate the mandatory extraction obligations. The stream carries ordering metadata and the second member's IRI sorts before the first, so an ID fallback cannot satisfy the oracle.",
    "requirement": "LDES10-EXTRACT-002",
    "requirements": [
      "LDES10-EXTRACT-002",
      "LDES10-EXTRACT-003",
      "LDES10-EXTRACT-004",
      "LDES10-EXTRACT-005",
      "LDES10-EXTRACT-006",
      "LDES10-EXTRACT-007",
      "LDES10-EXTRACT-008"
    ],
    "requirementLevel": "Must",
    "group": "MemberExtraction",
    "requiredCapabilities": []
  },
  "outcome": "inapplicable",
  "events": [],
  "requests": [],
  "diagnostics": [
    "scenario runs require ordered mode; adapter declares unordered"
  ]
}