Aggregated Distribution
note: maybe we will do them, maybe we won't
- t.2025.11.08.09 probably not. Better to go the other way: from a payload dataset, create all its named nodes and link back to the original; keeps things flow-y
- probably won't do unified distributions except via API.
A node's aggregated distribution is a compilation of all the child flows of itself and its contained nodes (their _payload/_default/ snapshots), situated directly under the parent node with an intuitive filename like "nodename.ext".
Essentially, it's a "(sub-)mesh in a single file."
Perhaps its only available via API.
Purpose
Aggregated distributions support composability and transposability by:
- Combining contained nodes' data into a single resource
- Supporting modular ontology and knowledge base construction
Issues
config options
- zipping/compression?
- user data only, or include metadata/config
Generation Process
During Weave Process, aggregated distributions are created by:
- Scanning contained payload nodes recursively within the mesh structure
- Collecting
_payload/_default/distributions from each flow - Merging content with proper URI resolution and prefix handling
- Excluding
_configand_metadatasets (data content only) - Generating multiple distributions (.ttl, .rdf, .jsonld) as configured
Examples
Composable Ontology
/my-ontology/
├── my-ontology.ttl ← Aggregated distribution
├── my-ontology.rdf ← Aggregated distribution
├── my-ontology.jsonld ← Aggregated distribution
├── Person/ ← payload node (class definition)
├── hasName/ ← payload node (property definition)
└── Organization/ ← payload node (class definition)
Knowledge Base
/biotech-kb/
├── biotech-kb.ttl ← Aggregated distribution
├── biotech-kb.jsonld ← Aggregated distribution
├── companies/
│ ├── genentech/ ← Company payload node
│ └── moderna/ ← Company payload node
└── products/
├── drug-x/ ← Product payload node
└── vaccine-y/ ← Product payload node
Technical Considerations
Merging logic handles:
- Relative path resolution - Converting relative URIs to absolute
- Prefix consolidation - Deduplicating namespace declarations
- Graph merging - Combining RDF graphs from multiple sources; de-duplicating
- Base URI handling - Ensuring consistent URI resolution
Use Cases
- Ontologies - Classes and properties from contained nodes
- Vocabularies - Terms and definitions from specialized nodes
- Catalogs - Dataset metadata from multiple sources
- Knowledge bases - Facts distributed across domain-specific nodes
- Configuration data - Settings aggregated from component services
Related Concepts
- payload flow - Source datasets for aggregation
- Weave Process - Process that generates aggregated distributions
- FlowShot - Contains the actual distributions being aggregated
Backlinks