der: The current implementation also includes the "context" property (on
the RDF) which provides the name/uri mapping and inferred type information
for every property. See GoogleCode?. This enables round tripping for
well-behaved RDF. While round tripping is a non-goal at this stage
we-Epimorphics need a simple update version of the protocol and including
the context enables that. As a side effect the context also means that all
the available properties are communicated to the client.
JT: The disadvantage is that it can add a huge amount of weight to the JSON
representation, at least in its current form. Putting the information at
the metadata endpoint makes it accessible (for the purposes of
round-tripping) without having the repetitive burden in every single document.
Original issue reported on code.google.com by leigh.do...@gmail.com on 20 Mar 2010 at 5:35
Original issue reported on code.google.com by
leigh.do...@gmail.com
on 20 Mar 2010 at 5:35