UBF vs JSON

UBF(B) is the contract, it's almost erlang code:

java 代码

+TYPES
  person() = {person,
              firstname(),
              lastname(),
              sex(),
              age()};
  firstname() = string();
  lastname() = string();
  age() = int();
  sex() = male | female;
  people() = [person()].

UBF(A) is the binary encoding.
In UBF(A), spaces are optional. Example for type people():

java 代码

’person’ >p
# {p "jim" "smith" ’male’ 10} &
  {p "susan" "jones" ’female’ 14} & $

In UBF(A), the order of data makes sense,  thus, UBF is not data order free.

In JSON, it will be:

js 代码

{"person": [{"firstname":"jim","lastname":"smith","sex":"male","age":"10"},
            {"firstname":"susan","lastname":"jones","sex":"female","age":"14"}]}

In JSON, the order of data is free.

In XML, it will be:

xml 代码

<people>
  <person>
    <firstname>jim<!---->firstname>
    <lastname>smith<!---->lastname>
    <sex>male<!---->sex>
    <age>10<!---->age>
  <!---->person>
  <person>
    <firstname>susan<!---->firstname>
    <lastname>jones<!---->lastname>
    <sex>female<!---->sex>
    <age>14<!---->age>
  <!---->person>
<!---->people>