Thanks Norbert, that's great. I won't be able to get back to this project
for another week or two (some stuff has come up) but will let you know if I
have any questions.
On Thu, Jan 10, 2019 at 2:52 AM Norbert Hartl via Pharo-users <
pharo-users@lists.pharo.org> wrote:
> Hi Eric,
>
> I‘m late to
--- Begin Message ---
Hi Eric,
I‘m late to the game but I‘m interested to talk abd cooperate. I implemented
JSON schema [1] not long ago. This can also be used to add a mapping from
object to json. It has also a type key inside the json object. I did it with an
intermediate object. The
Hi Sven, thanks for the response.
Unfortunately since I'm working with a standard here, there is always going
to be an explicit `"type": ` attribute rather than having the key
itself be the name of the type. I guess I'll stick to the two-pass read
solution. But the writing solution can use the
Eric,
> On 9 Jan 2019, at 00:34, Eric Gade wrote:
>
> Hey guys,
>
> I'm toying with the idea of a Pharo implementation of ActivityStreams
> (https://www.w3.org/TR/activitystreams-core/#introduction) which is based on
> a subset of JSON called JSON-LD (for "linked data").
>
> While I do not
This could be very useful, in the past I used ExtJS which serialized its
components in JSON format with a similar "xtype" attribute that was used to
lookup the proper class to instantiate.
But NeoJSON being stream based, and requiring a mapping to instantiate
specific classes, the only, dirty,
Hey guys,
I'm toying with the idea of a Pharo implementation of ActivityStreams (
https://www.w3.org/TR/activitystreams-core/#introduction) which is based on
a subset of JSON called JSON-LD (for "linked data").
While I do not believe this would entail creating a whole JSON-LD
implementation, I
