search

Accord-Project / aec3po

AEC3PO: Architecture, Engineering, Construction Compliance Checking and Permitting Ontology
https://w3id.org/lbd/aec3po/
2 stars 1 forks source link

Functions #35

Closed beachtom closed 1 year ago

beachtom commented 1 year ago

We need to be able to represent a function in the ontology.

It should have a name - a return type (singular or array) and a set of parameters.

We should be able to relate the function to an implementation. I.e. SPARQL, Shacl - or a microservice

EdliraK commented 1 year ago

https://fno.io/spec/ looks like there is already a Function ontology. Will have a think about it.

beachtom commented 1 year ago

Just to recap what I think the requirements are we should be able to represent:

  1. What is the name of the function
  2. What is its parameters (they could either be number, boolean, string or a GlobalID(UUID))
  3. What is its return type, wither boolean, a number, a string, a GlobalID or a list of GlobalID
  4. Some mapping to the microservice where it could be implemented.
Gonsco commented 1 year ago

@beachtom Could you provide some example of how you think this function could be represented in the ontology to have a clearer idea. I think it could be useful.

beachtom commented 1 year ago

I am not really sure how we would represent it - but I think we need some sort of function class - with data properties for the other elements

EdliraK commented 1 year ago

@Gonsco , @beachtom we will reuse the Function ontology for this: https://fno.io/spec/