OPF-O · Conformance合规

GB/T 48000.3—2026 ConformanceGB/T 48000.3—2026 对齐自声明Self-declared alignment · not a certification自声明对齐 · 非认证

Self-declared. This page has not been assessed by any certification, testing or standardization body and constitutes no certification, accreditation or conformity-assessment conclusion. The GB/T 48000.3—2026 text is copyright its publisher; this page cites clause numbers and requirement points only, not the original text.自声明（self-declared）。本页未经任何认证机构、检测机构或标准化组织评估，不构成认证、认可或合格评定结论。GB/T 48000.3—2026 正文版权归其发布机构所有，本页仅引用条款编号与要求要点，不复制原文。

Scope: the OPF v2.0.0 semantic exports (ontology https://oprocess.net/ns/opf), excluding MCP-server runtime behavior. Anyone can re-run the validation: uv run python -m scripts.validate_semantic.声明对象：OPF v2.0.0 语义导出物（本体 https://oprocess.net/ns/opf），不含 MCP Server 运行时行为。任何第三方可复跑校验：uv run python -m scripts.validate_semantic。

Clause mapping条款对齐

Clause条款	Requirement要求要点	OPF implementationOPF 实现
`§5.1`	Cross-domain sharing; avoid local-context dependency跨领域共享，避免局部语境依赖	Reuses common W3C vocabularies; the oprocess:// internal alias appears in no export复用 W3C 通用词汇；oprocess:// 内部别名不出现在导出物中
`§5.2`	Entity types + datatype/object properties + axioms实体类型 + 数据/对象属性 + 公理	3 entity types, 9 datatype + 5 object properties, disjoint / functional / irreflexive axioms3 实体类型、9 数据属性、5 对象属性、不相交/功能性/非自反公理
`§5.3`	W3C ontology language + Turtle/JSON-LD + SHACL validationW3C 本体语言 + Turtle/JSON-LD + SHACL 校验	OWL/RDFS + dual Turtle/JSON-LD serialization + SHACL; all 2,442 nodes conform (timestamped validation-report.txt, reproducible)OWL/RDFS + Turtle/JSON-LD 双序列化 + SHACL；2442 节点校验通过（附时间戳报告 validation-report.txt，可复跑）
`§5.4`	IRI = namespace + local identifier, globally uniqueIRI = 命名空间 + 本地标识符，全球唯一	Centralized IRI policy; instance IRIs carry no version segment, remaps via id_aliasesIRI 政策集中；实例 IRI 不带版本段，重映射走 id_aliases
`§6.1.2`	Reuse existing entity types where an ontology already defines them现有本体已有实体类型应直接采用	Adopts skos/dcterms directly; opf:ProcessNode declared a subclass of skos:Concept直接采用 skos/dcterms；opf:ProcessNode 声明为 skos:Concept 子类
`Ch. 8`	Disjointness / unique identity / enumerations / functional / hierarchy不相交/唯一标识/枚举/功能性/层次结构规则	AllDisjointClasses; exactly-one notation + SPARQL global-uniqueness; two-valued domain enum; functional level/domain; top-concept XOR single parent; irreflexive precedes guard (applies once the edge layer ships)AllDisjointClasses；notation 恰一 + SPARQL 全局唯一性约束；domain 二值枚举；level/domain 功能性；顶层 XOR 单父；precedes 非自反守卫（边层发布后对实例生效）
`Ch. 9`	Own namespace, modular extension, core left unchanged自有命名空间、模块化扩展、不改核心	Extension vocabulary confined to opf:; SKOS/DC core untouched; opf:precedes is a Chapter-9 own-namespace extension, not a core-property alignment扩展词汇收敛于 opf:；SKOS/DC 核心零改动；opf:precedes 属第 9 章自有扩展、非核心属性对齐
`App. A`	Appendix-A entity/property metadata elements实体八要素 / 属性七要素元数据	Self-checks a subset of Appendix-A elements: bilingual label, definition, isDefinedBy, property domain/range — 0 gaps; Name / superclass / equivalence not yet fully verified自检附录 A 部分要素：双语 label、定义、isDefinedBy、属性 Domain/Range，0 缺口；Name/父子类/等价类等未完整核验
`App. D`	Turtle instantiation style (informative)Turtle 实例化风格参照	@prefix, bilingual labels and instance naming follow the Appendix-D examples@prefix、双语标签、实例命名对照附录 D 样例

Boundaries边界

Chapters 6/7 model 'standards documents'; OPF is a process-classification domain ontology and extends within the opf: namespace per Chapter 9, claiming no implementation of the full documentary entity set and changing no core definition.第 6/7 章面向“标准文献”建模；OPF 为流程分类领域本体，按第 9 章在 opf: 命名空间扩展，不声明实现文献实体全集，不改核心定义。
Multilingual labels fixed at source (P0-6): all 2,442 node names and descriptions carry genuine Chinese (0 zh==en placeholders, 0 residue; English source untouched, KPI names re-translated too), so Appendix A's multilingual requirement is met at source; the export keeps the zh==en filter as a defensive guard.多语言标签已在源头修复（P0-6）：全部 2442 个节点名称与描述均为 genuine 中文（zh==en 占位符 0、无中文残留 0；英文源不变，KPI 名同步重译），附录 A 多语言要求实质满足；导出仍保留 zh==en 过滤器作为防御守卫。
KPI and role instances ship with the later edge layer; provenance uses W3C PROV (not specified by the standard, a compatibility addition).KPI 与岗位实例随后续边层发布；溯源采用 W3C PROV（国标未规定，兼容性补充）。

Licensing许可

The ontology and constraint files (opf.ttl / opf-shapes.ttl / context.jsonld) are CC BY 4.0; the node data dump (opf-nodes.ttl) is evaluation-use-only for now, with a formal license pending confirmation of the source-framework IP boundary. The PCF / ITIL / SCOR source datasets are not published, and no rights are claimed over third-party framework names, original hierarchy or their protected expression.本体与约束文件（opf.ttl / opf-shapes.ttl / context.jsonld）采用 CC BY 4.0；节点数据转储（opf-nodes.ttl）当前仅供评估用途，正式许可待源框架 IP 边界确认。不发布 PCF / ITIL / SCOR 原文数据集，也不主张对第三方框架名称、原始层级或其受保护表达享有权利。

Full declaration (with scope table and deviations): conformance.md.完整声明（含范围表与差异说明）：conformance.md。