Re: Error Ontology

Hi,

 

Hi,

 

I am working on REST API’s for validation and evaluation. 

 

To make my life more complicated, for every triple <function, action, asset>  I want two API, one returns the possible evaluation paths (eg. <agreement, rule, <any messages>> and a second one returns actual evaluation outcome <result, activation, <any messages>>.

 

For consistency, I have two types of response (an internal JSON for my IDE, and either RDF or JSON-LD for general consumption) and I have 2 types of errors :

 
The API errors (e.g. 500) – these are simple to represent;
The “traversal” errors (like my example error below: “enquiry for subject A on world B => subject A doesn’t exist) could turn out to be complicated (e.g. the validation could be a sequence logical constraint X not satisfied in rule R for party A in world B), and I am wondering if the best representation for a machine would be an RDF (or JSON-LD) output to “understand the error” – those would go in the <any messages> section of a response.
 

So the answer is sort of ‘both’: machine-readable that could be easily templated for human consumption.

 

Thanks,

 

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: <Research@OatGrain-InnovationS.de>
Date: Tuesday 16 July 2024 at 06:09
To: 'Joshua Cornejo' <josh@marketdata.md>, <public-odrl@w3.org>
Subject: RE: Error Ontology
Resent-From: <public-odrl@w3.org>
Resent-Date: Tue, 16 Jul 2024 05:09:44 +0000

 

Hello Joshua.Cornejo,

Hallo @all,

What ist the  goal of usage for the error representation?
Seeking human readable info for an occurred error message.
Support of error and parsing mechanisms (in a compiler)
 

Yours,

Dipl.-Phys. Frank.Haferkorn




 

From: Joshua Cornejo <josh@marketdata.md> 
Sent: Montag, 15. Juli 2024 17:14
To: public-odrl@w3.org Group <public-odrl@w3.org>
Subject: Error Ontology

 

Hi,

 

Does anyone know of a “broadly” used ontology to represent errors?

 

ex:returnedError               a on:Error;

               terms:description "did:odrlw:0190b6bc-7d30-7062-a56c-f5b2be29edfa subject {efe046cc-4e45-4c4f-915d-146a81dd5749} not found"@en.

 

I am looking to return useful information (for example above, the party - in red - wasn’t found in the world - in blue).

 

Regards,

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain