- From: stuartmyles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Dec 2016 14:15:13 +0000
- To: public-poe-archives@w3.org
Yes - I admit, I raised the question of auto-generating XML from the Ontology, to illustrate why I think auto-generating the JSON from the Ontology is also not a good idea. I don't seriously think that we should auto-generate either XML or JSON. In both cases, the auto-generating the schema will result in ugly documents, Fine for people who never plan to work with the formats directly (i.e. those who only like the RDF data model but are indifferent to how it is expressed). But for people who only care about their preferred format (XML or JSON) then they are going to be put off by the details of the auto-generated encoding. And, worst case, create their own. This, for example, is what happened with the PRISM Rights Expression Language: they liked the ODRL data model, but decided to create their own XML encoding, because they don't like some of the details of the ODRL 2.1 encoding. See, for example, http://www.prismstandard.org/specifications/3.1/Draft_Rights_Summary_Guide_3.1.htm#_Toc406232056 As Renato says, there are already implementations of ODRL in both XML and JSON. Now, we can't make an omelette without breaking a few eggs. And, I'm not under the illusion that what we will end up with is exactly the same thing as ODRL 2.1. But I think this group should decide on purpose whether they want to specify the XML and JSON encodings of the ODRL (POE) data model. Or whether we are content for others to take the data model and make up their own encodings, which is what I predict will happen, if POE doesn't specify a JSON encoding. Regards, Stuart On Tue, Dec 13, 2016 at 8:56 AM, Ivan Herman <notifications@github.com> wrote: > > > On 13 Dec 2016, at 14:03, Renato Iannella <notifications@github.com> > wrote: > > > > We still have XML implementations. When we asked the community in > October, both Associated Press and Reuters News said they will use the XML > encoding. > > > > O.k. (But that is another discussion then; it should certainly not be > RDF/XML.) > > > > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/poe/issues/46#issuecomment-266744347>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ADwBfzp_ilISkIRtiU9_xdqgsy4_vnRgks5rHqP1gaJpZM4KZWR0> > . > -- GitHub Notification of comment by stuartmyles Please view or discuss this issue at https://github.com/w3c/poe/issues/46#issuecomment-267043875 using your GitHub account
Received on Wednesday, 14 December 2016 14:15:19 UTC