Re: The survey results are in and they look great

I agree too. The only issue with my heracles library [1] was handling 
Hydra in RDF-agnostics way. For now I'm pulling in rdf-ext to work at 
triple level and that way I'm also handling any RDF serialization. Does 
it count as framework-agnostic? ;)

I think that a Hydra client should be aware of RDF anyway. The only 
requirement is that it's transparent to a consumer uninterested.

Would you guys agree?

Thanks,
Tom

[1]: https://github.com/wikibus/heracles

On 2016-06-16 17:01, Thomas Hoppe wrote:
> Maintaining several open source JS objects and working with several front-end frameworks like Angular and Ember, I can only support that and that's why we have written hyjax in a framework agnostic way
>
> ‎https://github.com/pajax/hyjax
>
> And based on that a service for Ember for example.
> ‎
>   Original Message
> From: Dietrich Schulten
> Sent: Donnerstag, 16. Juni 2016 16:21
> To: public-hydra@w3.org
> Subject: Re: The survey results are in and they look great
>
>
>
> Am 15.06.2016 um 10:27 schrieb Pablo Dorgambide:
>
>> At Javascript language (for web platform) we must take in consideration the
>> great frameworks that exist (Angular, Ember, React ) and I think that the
>> Hydra Client must be implemented to integrated with each of them.
>
> And here the discussion starts ;-)
>
> I'd rather see a mostly "pure" js implementation, as modern as possible,
> preferably based on EcmaScript 2015 (which can be babelified and
> polyfilled to run with older browsers), e.g. using Promises for remote
> communication - rather than having to maintain clients which follow the
> opinionated approaches of various frameworks.
>
> The json-ld implementation [1] is a good example. Almost no dependencies
> required.
>
> [1] https://github.com/digitalbazaar/jsonld.js
>
> My 2 cents.
>
> Best regards,
> Dietrich
>
>
>
>
>
>
>

Received on Thursday, 16 June 2016 18:17:05 UTC