- From: David Booth <david@dbooth.org>
- Date: Wed, 29 Apr 2015 14:15:05 -0400
- To: rsiemens77@hotmail.com
- CC: public-linked-json@w3.org
On 04/29/2015 01:37 PM, Ron Siemens wrote:
> Thanks for the explanations, Markus.
>
> >The problem is that you have a data model that you only implicitly
> expose in your JSON representations. The properties you use are context
> sensitive (in the traditional sense; not talking about JSON-LD contexts
> here).
>
> If I use unique property names, rather than the value prefixes in your
> example, would that also lead to a viable context solution?
>
> I've implemented an experimental content negotiation solution that
> provides JSON as the below. Could you suggest an appropriate context?
> Also have posted this as an open problem here
> http://www.guru.com/emp/projectDetail.aspx?ProjectId=1126285 if you'd
> prefer that venue.
That URI seems to require a login to view the content. Can you please
post a URI that allows public visibility?
Thanks,
David Booth
>
> Ron
>
> tree
> {
> "tree_id":"100",
> "tree_name":"maple",
> "root_branch":"root_branch"
> }
>
> branch
> {
> "branch_id":"200",
> "branch_name":"root_branch",
> "branches":[ { "branch_id":"201", "branch_name":"sub1_branch" }, {
> "branch_id":"202", "branch_name":"sub2_branch" } ],
> "leaves":[ { "leaf_id":"500", "leaf_name":"leaf1" }, {
> "leaf_id":"501", "leaf_name":"leaf3" }, { "leaf_id":"502",
> "leaf_name":"leaf4" } ],
> "age":"20"
> }
>
> leaf
> {
> "leaf_id":"500",
> "leaf_name":"leaf1",
> "area":"10",
> "age":"3"
> }
>
Received on Wednesday, 29 April 2015 18:15:34 UTC