The Defense Supply Chain and Documentation Ontology (DSCDO) provides a formal model for representing knowledge about supply chain networks, processes, and entities. It enables interoperability and knowledge sharing between supply chain information systems by providing a common vocabulary and conceptual structure and supporting documentation providing supply chain provenance. Key concepts modeled include: - Supply chain stages such as suppliers, manufacturers - Products, materials, and information flows between supply chain stages - Supply chain processes such as procurement, production, and transportation The ontology is designed to be extensible to support modeling of domain-specific supply chains and integration with other enterprise ontologies. It aims to facilitate supply chain analytics, decision support, knowledge management, and semantic integration of heterogeneous supply chain data sources.
An ontology for describing supply chain documentation.
This work is licensed under a Creative Commons Attribution 4.0 International License.
Defense Supply Chain and Documentation Ontology (DSCDO)
0.1.0 - intial release of pattern skeletons
0.1.1 - adding supply chain events from the supply chain pattern and connecting to the documentation extraction pattern
0.1.2 - adding identifier patterns and beginning of shapes
0.1.3 - chaning iri namespace and ontology prefix
The Defense Supply Chain and Documentation Ontology (DSCDO) is a sophisticated framework designed to capture and link supply chain documentation artifacts to relevant events and Tradable Resource Units (TRUs). This ontology serves as a comprehensive model for representing the complex interactions and transactions within the defense supply chain, ensuring that every document, event, and resource unit is accurately documented and interconnected. Key Components of DSCDO: 1. **Event Pattern**: The ontology leverages an Event Pattern to model various types of events such as TransferEvent, TransformationEvent, CustodyChangeEvent, OwnershipChangeEvent, TransportEvent, and ObservationEvent. Each event is linked to spatiotemporal aspects through the SpatiotemporalExtent class, which captures the time and place of occurrence. 2. **Participant Role**: Events are connected to participants through roles such as SourceRole, TargetRole, EquipmentRole, and CustodianRoles (both Source and Target). This ensures that every event is associated with one or more agents (e.g., organizations, individuals) fulfilling specific roles. 3. **Container and Containment Relations**: The ontology models containers and their types, along with the relationships of containment. This includes modeling the TemporalExtent of containment, allowing for the tracking of resources over time and space. 4. **Identifier Encoding**: To maintain traceability, DSCDO includes a detailed Identifier framework, encompassing IdentifierEncoding, IdentifierSource, and IdentifierType. This system ensures that each resource unit can be uniquely identified and traced through the supply chain. 5. **Traceable Resource Unit (TRU)**: The TRU is a core concept representing units that are tracked through the supply chain. This includes QuantityOfMaterial, which is further detailed by Material types, measurements, and units, ensuring precise tracking and management of resources. 6. **Observation and Measurement**: Observations are linked to TRUs to capture measurement data, such as quantity and quality, ensuring that all resource units are accurately monitored and recorded. Knowledge Extraction Workflow: The DSCDO is integrated into a knowledge extraction workflow designed to process supply chain documentation. This workflow involves: 1. **Document Acquisition**: Using advanced OCR technologies (e.g., Azure OCR), documents are scanned and converted into machine-readable formats. 2. **Knowledge Extraction**: Leveraging LLM AI-driven pipelines (e.g., LangGraph, LangChain), the extracted text is processed to identify and link relevant entities and events according to the DSCDO patterns. 3. **Triple Generation**: The processed information is transformed into RDF triples, forming a structured, queryable knowledge graph that adheres to the DSCDO schema. This enables advanced querying and analysis, facilitating decision-making and supply chain management. Application and Benefits: By implementing DSCDO, defense supply chain management can achieve higher levels of transparency, traceability, and efficiency. The ontology ensures that all documentation artifacts are systematically captured and linked to corresponding events and resource units, providing a robust framework for managing the complexities of defense logistics and procurement. In summary, the DSCDO provides a comprehensive and structured approach to managing defense supply chain documentation, leveraging advanced knowledge extraction techniques to produce a detailed and interconnected view of supply chain activities.
Center for Research Computing, University of Notre Dame
PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used.
A prov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven .
An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity.
The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable.
A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.
Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable.
This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] . Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified. prov:wasInfluencedBy should not be used without also using one of its subproperties.
Relates an agent to the role it plays in an event.
assumes role
Indicates that the document content was derived from a specific digital document.
has contained in relation
has further documentation
Property relating Event to InformationObject in this pattern. The domain of this property is not restricted to Event since it is possible that non-event to have an information object. The range is always InformationObject since it makes no sense to have a property named hasInformationObject to point to anything other than information object.
has information object
has postcondition
has precondition
has spatiotemporal extent
Property relating Event to SpatioTemporalExtent in this pattern. The range is always SpatioTemporalExtent (globally) since it makes no sense to have a property named hasSpatioTemporalExtent to point to anything other than spatiotemporal extent. The domain is not set to Event as non-Event may also have spatiotemporal extent.
has temporal extent
Associates an information extraction workflow with a specific pipeline.
Links a digital document to its content extracted via OCR.
Specifies the type or category of a digital document.
occurs at
produced at
Property relating Event to ParticipantRole in this pattern. The range is always ParticipantRole since it makes no sense to have a property named as providesParticipantRole not to point to a participant role. The domain is not set to Event as non-Event may also provide a participant role.
provides participant role
provides role
Property expressing partonomic relation between two events. Domain and range are always Event.
sub event of
Connects the document content to the workflow that processed it.
The processed text of a digitized document.
An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary.
An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous.
The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics.
An organization is a social or legal institution such as a company, society, etc.
Person agents are people.
A software agent is running software.
An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
An entity participating in a supply chain event, such as a person, organization, or system.
An entity participating in an event, such as a person, organization, or system.
Agent
The role of goods or materials being observed or measured.
Being Measured Role
The role of goods or materials being shipped or transported.
Being Shipped Role
Represents a containment relationship between events.
Contained In Relation
An event where the custody of goods or materials changes.
Custody Change Event
Represents a digital document that has been scanned and digitized, and is part of the broader document processing workflow.
Represents the type or classification of a document.
A source of documentation or information related to an event.
Documentation Source
Represents the content extracted from a document.
The role of equipment or machinery used in an event.
Equipment Role
Represents any kind of events. An event possesses a spatiotemporal extent, provides at least one participant-role, which is performed by some entity (agents or otherwise), and may be a sub-event of another event. An event may also have additional descriptive information, which is consolidated through an information object.
Event
Represents a pipeline used in the information extraction process.
An entity that encapsulates all descriptive or non-defining information of the corresponding event, e.g., names, additional identifiers, textual descriptions, etc. Should normally be aligned to a separate Information Object pattern.
Information Object
Represents a workflow or process of extracting information from documents.
An event where an observation or measurement is made on goods or materials.
Observation Event
An event where the ownership of goods or materials changes.
Ownership Change Event
Every ParticipantRole represents a reified relationship between an event and one of its participants. Should normally be aligned to a separate Participant-Role pattern.
Participant Role
Represents digital document that is supply chain documentation
The role of the entity that has custody of goods or materials before an event.
Source Custodian Role
The role of the entity that owns goods or materials before an event.
Source Owner Role
The role of the entity from which goods or materials originate.
Source Role
Hook to a complex notion representing a unified spatial and temporal extent. Intended to cover non-static or discontinuous spatiotemporal extent. Should be aligned to a separate Spatiotemporal Extent pattern.
Spatiotemporal Extent
An event occurring in a supply chain process.
Supply Chain Event
A role played by an entity in a supply chain event.
Supply Chain Role
Represents the spatial and temporal extent of a supply chain event.
Supply Chain Spatiotemporal Extent
The role of the entity that gains custody of goods or materials after an event.
Target Custodian Role
The role of the entity that gains ownership of goods or materials after an event.
Target Owner Role
The role of the entity to which goods or materials are destined.
Target Role
Represents the temporal extent of an event.
Temporal Extent
An event involving the transfer of goods or materials.
Transfer Event
An activity or process that transforms goods or materials.
Transformation Activity
An event where goods or materials undergo a transformation process.
Transformation Event
An event involving the transportation of goods or materials.
Transport Event
The most generic kind of creative work, including books, movies, photographs, software programs, etc.