This is a preliminary page intended to trial using the Artifact design methodology (simplified) to guide and describe the project. At this stage it is a brainstorming WIP |
Improve (or solve) a <problem> |
Tip: Specific issue or challenge that requires a solution or improvement. Data format incompatibility between data middleware and reasoner |
Tip: Ultimate objective(s) that a solution aims to achieve, typically formed by the stakeholders' desires. In the context of COVESA, the goal of an artifact is inherit from the general COVESA goals defined as an alliance. In other words, each artifact will represent (minor or major) steps towards an ultimate goal. Enabling the data exchange between data middleware and reasoner via websocket |
Tip: Criteria and specifications that the artifact must meet to address the identified problem and achieve the set goals. Typically presented as functional and non-functional.
Functional:
Non-functional:
|
Tip: Represents the tangible outcome of a design that aims to solve the problem and fulfils the specified requirements and goals. Convertor |
Technical Description:
Sequence Diagram | Provide an overview of the real-time converter's architecture, including the components involved and their interactions. This can be depicted using a high-level architectural diagram, showcasing the main modules or layers of the converter. Note that this converter focus one "real-time" side. | ||||||||||||
Mapping | Describe the mechanism used for mapping the JSON data to RDF format. Explain how the converter identifies the relevant JSON schema and maps the data elements to RDF triples or nodes. You can provide examples or a mapping diagram to illustrate this process. Example: | ||||||||||||
RDF Generation | Explain how the converter generates RDF data from the mapped JSON data. Describe the process of creating subject-predicate-object triples or nodes in RDF format based on the JSON schema. You can showcase an example of the JSON data and its corresponding RDF representation. The process of RDF triple generation are based on the triple categories:
There are two types of messages modelled in different ways which needed to treat differently. The main difference lies in where does the types, properties and data type come from.
| ||||||||||||
Real time JSON to RDF | VSS Tree: PDM Tree: | ||||||||||||
Real time RDF to JSON |
| ||||||||||||
Integration with Data Middleware and Reasoner | Describe how the converter integrates with the data middleware and the reasoner. Explain any specific APIs, protocols, or connectors used for communication between the converter and these systems. You can include a deployment diagram to illustrate the integration.
| ||||||||||||
Configuration and Extensibility | Discuss how the converter is configured and how it can be extended Configuration: Input
Output
|