- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 24 Aug 2015 10:48:08 +0200
- To: "Charpenay, Victor (ext)" <victor.charpenay@siemens.com>
- Cc: "public-hydra@w3.org" <public-hydra@w3.org>
Hi Victor, > If so, may you give me a hint on where to search in the mail archive (e.g. which mail subject)? These are good places to start: – https://lists.w3.org/Archives/Public/public-hydra/2015Jan/0022.html – https://github.com/HydraCG/Specifications/issues/90 > I'd like to develop a method to automatically turn ontological elements into REST-accessible resources (i.e. automatically generate Hydra specs out of an OWL ontology). Having such a design where classes are practically seen as individuals/class instances does not facilitate the thing, it would be of great help if I understood why. There's probably no place in such a system where you'd have to use hydra:Resource and hydra:Class explicitly. Also, in RDF, classes are instances by definition, i.e., all classes are instances of rdfs:Class. Best, Ruben
Received on Monday, 24 August 2015 08:48:38 UTC