Re: draft data format for Opentabs

Hi,
I'm trying to read the open tabs spec and it seems really interesting, here
are a few comments.

For pretty much the same reason that I'm against the JSON LD format's colon
prefix notation I think Hungarian notation is a really bad idea.

I'd like to strongly recommend against Hungarian notation. It is quite
unreadable and I can't see any benefits at all from it. If possible it's
even more confusing that JSON-LD's colon prefix notation.

For these standards to take off they need to be very simple, skimmable etc.
JSON is also commonly translated into methods/attributes in the programming
language used.

Besides that I'd also still like to recommend the words "from" and "to"
instead of "source" and "destination". I personally believe that if there
are simple synonyms available they should be preferred over longer more
complex terms. This goes for PaySwarm as well of course.

Finally instead of Ower and Owee I suggest using the the proper English
words Debtor and Creditor. I know these words can be loaded with other
meanings, but still they are the correct terms.

P



On Mon, May 14, 2012 at 7:11 PM, Michiel de Jong <michiel@unhosted.org>wrote:

> The webcredits spec was meant to be expanded, and i am now at a point
> where it is not expressive enough for opentabs. Also I think its
> variable naming could be improved using Hungarian prefixes like the
> ones I posted to the rww cg list on Saturday.
>
> So here is a draft version of the concepts i am currently thinking of
> introducing for Opentabs.
>
> https://github.com/unhosted/website/wiki/opentabs-data-format
>
> It's also an experiment about how Hungarian linked data could look,
> and it's also still very much subject to bugs and changes. This may
> change in the future, but i wanted to share it with this cg in case
> anyone has comments at this point.
>
>
> cheers!
> Michiel
>
>


-- 
-- 
http://picomoney.com - A whole new kind of money
http://payglo.be - Blog about payments from a global perspective