- From: Phillip Lord <phillip.lord@newcastle.ac.uk>
- Date: Wed, 06 Apr 2011 16:07:21 +0100
- To: <public-owl-dev@w3.org>
Peter Frederick Patel-Schneider <pfps@research.bell-labs.com> writes: > I would argue instead that RDF/JSON for OWL axioms would be much more > confusing than a direct transformation. I think that Chris, who asked for this in the first place, has already agreed with this position. For what it's worth, I would also agree. If I want to operate in JSON, then I don't really want to have to think about the RDF syntactic representation of OWL at the same time. As a reduction to absurdity, for example, one way to get a JSON representation of OWL, would be to parse the XML of the OWL into DOM, then JSONify the DOM objects. Or, even more trivially, take the XML, add a quote to the start, a quote to the end, and escape any strings in the middle, and we something which is a valid JSON object. Both of these sort of miss the point, which is presumably to get a representation of the data in the OWL stuffed into a data model which looks like OWL. I agree this comes with the additional costs of having an additional data model, but then the same argument holds for RDF and, for example, XML or even Unicode. Phil
Received on Wednesday, 6 April 2011 15:07:53 UTC