-
Notifications
You must be signed in to change notification settings - Fork 11
Closed
Description
What is missing?
Capturing information and making it interoperable is not really the end goal. In the end, the goal is to harness the captured knowledge for better decision-making. Currently, any kind of knowledge extraction and query for information should be done via custom 'hard-coded' logic, even for simple query and filter tasks. This has been mentioned many times: #169, #158, #144, #7.
How should it be fixed?
So clearly the community needs an interoperable way to query various repository, join them, filter and extract information. Similar to DTDL query language, the AAS community must agree on some form of abstract syntax. Then there should also be a tool that can translate the syntax to SQL, SPARQL, MongoDB, ... query.
This can serve as an example:
Select Submodel2.average_temperature, Submodel1.property1, AAS.ID
FROM "URL_TO_AAS_REPOSITORY"
WHERE AAS.SeamnticID MATCH "https://semantic-id-matching.com"
WITH SubmodelRepository ON "URL_TO_SUBMODEL_REPOSITORY"
BIND Submodel1
{
Submodel.anotherjsonpath AS property1
WHERE
Submodel.jsonpath.value == 12 #filter on element value
Submodel.SemanticID MATCH "https://another-semantic-id.com" #filter on semantic id
}
BIND Submodel2
{
AVG(Submodel.jsonpath.value) as average_temperature # aggregation operator support
WHERE
Submodel.SemanticID MATCH "https://yet-another-semantic-id.com"
}
- I have signed the required Developer Certificate of Origin (DCO) already.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request