The maturity layer · MRK-2.0 · the namespace
Every term, defined where it points.
Every key in the MRK-1.1 JSON-LD context that is not borrowed from Dublin Core, SKOS or RDFS resolves to one namespace, https://machinereadyknowledge.com/ns#. This page is that namespace's documentation and its dereference target: 44 terms, each with a stable fragment, so a term IRI in a graph, a shape or a query lands on its definition.
The same address serves three forms. A browser gets this page. A client that asks for Turtle or JSON-LD gets the vocabulary itself, ready to load next to your corpus graph.
One IRI, three forms
The namespace IRI is /ns. The server picks the representation from the Accept header, and the forms are also served at fixed addresses so you can link or download them without negotiating.
- HTML: this page, the default for browsers.
- Turtle: ns.ttl, served as
text/turtleforAccept: text/turtle. - JSON-LD: ns.jsonld, served as
application/ld+jsonforAccept: application/ld+json.
Every term used by mrk-1.1.context.jsonld and shapes.ttl is defined here; the build for this vocabulary checks that no term is used without a definition. Terms from Dublin Core (title, publisher, language, replaces, references, isPartOf), SKOS and RDFS are reused as published and are not redefined.
Identifiers in examples are illustrative
The article and section IRIs you see in examples across this site, such as kb/ck-ops-1#resolution, and the concept IRIs under /vocab/, are illustrative. They show how an id becomes a node; they are not dereferenceable and nothing is served at them. Only /ns and the files served at this root resolve.
The terms
Properties show their domain and range on the right. A dash for the range means the object is a structured node or an open value. Each term's name is its anchor: /ns#requires jumps to its row.
| mrk:Article | A governed knowledge article: one MRK front-matter block and the sections it declares. | class |
|---|---|---|
| mrk:Section | An addressable part of an article, typed by role, quotable and citable on its own by its id (article-id#anchor). | class |
| mrk:mrkVersion | The MRK spec version the article declares conformance to (front-matter key mrk_version). | Article → xsd:string |
|---|---|---|
| mrk:profile | The MRK profile the article follows (for example software-product). | Article → xsd:string |
| mrk:articleType | The article's type from the closed MRK type list (front-matter key type), such as issue-resolution or concept. | Article → xsd:string |
| mrk:verified | The date the article was last verified accurate. | Article → xsd:date |
| mrk:lifecycle | Content state: draft, unreleased, current, superseded, retired or expired. Retrieval treats only current as answerable. | Article → xsd:string |
| mrk:visibility | Audience boundary: public, internal or confidential. A safety gate for answer assembly. | Article → xsd:string |
| mrk:entitlement | An entitlement a reader must hold to see the article. | Article → xsd:string |
| mrk:localizedFrom | The source-language article this article is a localization of. | Article → mrk:Article |
| mrk:concept | A governed vocabulary concept the article or section is about; the IRI resolves under /vocab/ and is a skos:Concept. | skos:Concept |
| mrk:appliesTo | Applicability scope: who and what the article is true for. Its object is a node carrying the dimension properties below. | Article → any |
| mrk:provenance | Where the article came from and how it was checked. Its object carries derivedFrom, validatedBy, graduatedFrom and confidence. | Article → any |
| mrk:relation | A typed relation from this article to another. Its object carries relType and relTarget; the projector also expands it into the direct edges below. | Article → any |
| mrk:hasSection | Links an article to each of its declared sections. At least one is required (shape ArticleShape). | Article → mrk:Section |
| mrk:plan | Applicability dimension: the commercial plan(s) the article applies to. | xsd:string |
|---|---|---|
| mrk:region | Applicability dimension: the region(s) the article applies to. | xsd:string |
| mrk:product | Applicability dimension: the product(s) the article applies to. | xsd:string |
| mrk:component | Applicability dimension: the product component(s) the article applies to. | xsd:string |
| mrk:audience | Applicability dimension: the audience the article is written for. | xsd:string |
| mrk:appliesToRole | Applicability dimension: the user role(s) the article applies to (front-matter key role inside applies_to). | xsd:string |
| mrk:jurisdiction | Applicability dimension: the legal jurisdiction(s) the article applies to. | xsd:string |
| mrk:versionRange | Applicability dimension: a product version range expression. | xsd:string |
| mrk:versionMin | Applicability dimension: lowest product version the article applies to. | xsd:string |
| mrk:versionMax | Applicability dimension: highest product version the article applies to. | xsd:string |
| mrk:versionExact | Applicability dimension: the single product version the article applies to. | xsd:string |
| mrk:dimensions | Open applicability dimensions beyond the named ones, for adopter-defined scoping. | any |
| mrk:derivedFrom | A source the article was derived from (ticket, document, incident). | any |
|---|---|---|
| mrk:validatedBy | Who or what validated the content. | any |
| mrk:graduatedFrom | The earlier content state this article graduated from, in the Content Graduation Model. | any |
| mrk:confidence | Declared confidence in the content, as a provenance signal. | any |
| mrk:relType | The kind of a relation (depends_on, prerequisite_of, references, part_of, see_also, applies_with, supersedes). | xsd:string |
|---|---|---|
| mrk:relTarget | The article a relation points at. | mrk:Article |
| mrk:dependsOn | Direct edge: this article cannot be applied correctly without the target. Basis of impact analysis; the target must be an Article (shape DependsOnIntegrityShape). | Article → mrk:Article |
| mrk:prerequisiteOf | Direct edge: this article must be done before the target. | Article → mrk:Article |
| mrk:appliesWith | Direct edge: this article is meant to be used together with the target. | Article → mrk:Article |
| mrk:sectionRole | The section's role from a closed list: context, symptom, cause, resolution, procedure, verification, concept, reference, prerequisite, result, caveat, example. | Section → xsd:string |
|---|---|---|
| mrk:selfContained | Human attestation that the section can be lifted alone and still be understood: it restates its prerequisites rather than pointing above. | Section → xsd:boolean |
| mrk:requires | Section-level edge: this section depends on the target section. Also the declaration a transclusion marker must agree with. The target must be a Section (shape RequiresIntegrityShape). | Section → mrk:Section |
| mrk:ArticleShape | SHACL node shape for Articles: title, verified date, lifecycle and visibility values, at least one Section. | node shape |
|---|---|---|
| mrk:SectionShape | SHACL node shape for Sections: exactly one role from the closed list, and a self-contained flag. | node shape |
| mrk:RequiresIntegrityShape | Every object of mrk:requires must be a Section in the corpus graph; a dangling requires fails. | node shape |
| mrk:DependsOnIntegrityShape | Every object of mrk:dependsOn must be an Article in the corpus graph. | node shape |
| mrk:SupersedesIntegrityShape | Every object of dcterms:replaces (front-matter supersedes) must be an Article in the corpus graph. | node shape |
Two of the properties are worth reading alongside their pages: mrk:requires is the edge that managed reuse declares and checks, and the shapes at the bottom are the L4 gate described on the graph projection.