search

linked-usdl / usdl-price

3 stars 1 forks source link

Track variables usage. #8

Closed jorgearj closed 11 years ago

jorgearj commented 11 years ago

We should capture the variables semantics and track their usage. How to do this?

jorgearj commented 11 years ago

We can give some extra semantics for variables by using the rdf:Description.

cpedrinaci commented 11 years ago

"The Description element may be thought of (for purposes of the basic RDF syntax) as simply a place to hold the identification of the resource being described"

Regarding the semantics of the variables, thus I don't think it is appropriate. For capturing the semantics you would either need to give the variable a concrete domain-specific type (problematic), or point to another concept indicating that this is its type (beyond it being a variable). One way to do this is, like in SAWSDL, to use sawsdl:modelReference to point to another concept.

In general this issue has been treated in every semantic Web service model for essentially it is the same problem. Having a look at the solutions adopted would be useful here.

I'm not sure what you understand by "Tracking their usage" though.

drleidig commented 11 years ago

I don't think that we need additional semantic descriptions for variables. They are just variables. Their semantics arise from the formulas the are used in.

cpedrinaci commented 11 years ago

I think adding semantics to these may well be necessary or simply quite handy to understand how the price is calculated. That is, if the price depends on how much information we transfer, as a client we'd better know this.

It should be pretty easy to do though simply by adding something like: "someVariable sawsdl:modelReference domainModel:DataTransfer"

Just one additional triple.

jorgearj commented 11 years ago

We don't need scope for variables for now. We will deal with this when an issue appears.