TriplesMaps reference
Every rr:TriplesMap in mapping/opda-pdtf.rml.ttl
has its own page, plus two indices over the same data giving both directions of
lookup — start from an ontology term, or start from a JSON Schema path.
The numbers
| Metric | Count |
|---|---|
rr:TriplesMap rules | 158 |
| Real predicateObjectMaps (owned directly by a TriplesMap) | 438 |
| Distinct ontology classes/properties touched | 37 classes + 285 properties |
| Distinct JSON Schema paths referenced | 323 |
The mapping file has 526 total
rr:predicateObjectMap triples, but only 438 of
them belong directly to a rr:TriplesMap. The other
88 are nested inside
31 fnml:functionValue blocks — the FNML
function-call pattern (enum→SKOS slugification, date
truncation) — binding a function's name and parameters, not a schema↔ontology
correspondence in their own right. This page's counts and rows are the
438 real ones only; the section overview's
own stat table now makes the same distinction.
By TriplesMap
All 158 rules, one row each. Facet by asserted class to jump straight to,
say, every rule that mints an opda:MonetaryAmount — each links to its own page
with the full predicate breakdown.
By ontology resource
Start from a class or property — which TriplesMap(s) touch it, and which JSON Schema path(s) it reaches.
By JSON Schema path
Start from a schema path — which TriplesMap(s) consume it, and which ontology term(s) it feeds.
Comments
Loading comments…
Sign in to post a comment