>> 
>> Fuel is included, but that implements a binary, not textual encoding.
>> IMHO it would make sense to include either or both STON and NeoJSON.
>> On the other hand, the same can be said about many external frameworks.
>> You can very easily load both STON or NeoJSON manually.
> 
> Thanks, Sven.
> 
> I just wonder what are the plans for future, because knowing that some 
> functionality will be available by default helps me to introduce new 
> interesting workflows.
> 
Why?


Reply via email to