Changes between Initial Version and Version 3 of Ticket #636


Ignore:
Timestamp:
21.02.2015 18:46:57 (10 years ago)
Author:
jri
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #636

    • Property Status changed from new to accepted
    • Property Cc JuergeN added
    • Property Milestone changed from Release 4.3 to Release 4.6

  • Ticket #636 – Description

    initial v3  
    55{ 
    66    type_uri: "my.parent.type" 
    7     composite: { 
     7    childs: { 
    88        "my.child.type": { 
    99            uri: "child.topic.uri", 
    … …  
    1515}}} 
    1616 
    17 Note: in this example the child topic is supposed to get an explicit URI, that's why the ''canonic topic format'' (`id`, `uri`, `type_uri`, `value`, `composite`) must be used here. This ticket refers to the canonic topic format only. 
     17Note: in this example the child topic is supposed to get an explicit URI, that's why the ''canonic topic format'' (`id`, `uri`, `type_uri`, `value`, `childs`) must be used here. This ticket refers to the canonic topic format only. 
    1818 
    19 Just to remember: if your application does not rely on specific topic URIs, the ''compact topic format'' could be used anyway. In this case there is no redundant `type_uri`: 
     19Just to remember: if your application does not rely on specific topic URIs, the ''simplified topic format'' could be used anyway. In this case there is no redundant `type_uri`: 
    2020{{{ 
    2121{ 
    2222    type_uri: "my.parent.type" 
    23     composite: { 
     23    childs: { 
    2424        "my.child.type": "Hi!" 
    2525    } 
    … …  
    3131{ 
    3232    type_uri: "dm4.contacts.person" 
    33     composite: { 
     33    childs: { 
    3434        "dm4.contacts.person_name": { 
    3535            "dm4.contacts.first_name": "Paul",