W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

Re: [foaf-protocols] low memory & WebID?

From: Peter Williams <home_pw@msn.com>
Date: Fri, 30 Dec 2011 13:08:13 -0800
Message-ID: <snt0-eas249F4B77D3496B5F1A839D092920@phx.gbl>
To: Leif Warner <abimelech@gmail.com>
CC: Henry Story <henry.story@bblfish.net>, Jiří Procházka <ojirio@gmail.com>, WebID XG <public-xg-webid@w3.org>, "foaf-protocols@lists.foaf-project.org" <foaf-protocols@lists.foaf-project.org>
Binary XML should be fast, for files with just 4 or 5 tripled in 2 or 3 layers of nesting.

Asn1 is binary , and electronics (routers operating at 1g) have optimized coders decides for all the fixed types (including Certs). 

On one 68020 us crypto box (whose firmware I got to reverse engineer) a famous telco/Internet company doing optimized secure data protocols was handling Certs in less than 1000 bytes of code space in the (then) rom. Not generalized type theory! Just bit decoder for fixed tagging and field sizes, in nested tlvs (like binary XML).

Sent from my iPhone

On Dec 30, 2011, at 12:57 PM, "Leif Warner" <abimelech@gmail.com> wrote:

> N-Triples are certainly the easiest format to parse - I wrote a very simple parser for them:
> http://code.google.com/p/scardf/source/browse/trunk/src/main/scala/org/scardf/NTriplesParser.scala

> Could just have easily been in C.
> 
> -Leif
> 
> 2011/12/30 Henry Story <henry.story@bblfish.net>
> 
> On 30 Dec 2011, at 20:42, Jiří Procházka wrote:
> 
> > Hi,
> > I think WebID should be flexible enough to be used on low memory
> > embedded systems, does this put any restrictions on the mandated
> > syntaxes? I figure turtle because of prefixes would be no go, and other
> > syntaxes too - the algorithm for webid validation (client code),
> > including the parsers for all required syntaxes, would be best to have
> > constant space complexity...
> > I don't think such concerns nor the use case are so outlandish they
> > shouldn't be taken in consideration.
> 
> I am trying to keep that in mind and keep in mind development for the freedombox.
> Swap-scala from Dan Connolly seems to indicate that you can write parsers in very little
> space for all the well known serialisations.
> 
>  http://code.google.com/p/swap-scala/

> 
> So there is a lot that can be done I think to reduce the space consumption of tools like Jena.
> 
> Henry
> 
> 
> >
> > Best,
> > Jiri
> >
> > _______________________________________________
> > foaf-protocols mailing list
> > foaf-protocols@lists.foaf-project.org
> > http://lists.foaf-project.org/mailman/listinfo/foaf-protocols

> 
> Social Web Architect
> http://bblfish.net/

> 
> _______________________________________________
> foaf-protocols mailing list
> foaf-protocols@lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols

> 
Received on Friday, 30 December 2011 21:09:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 December 2011 21:09:01 GMT