Changes

* ''role''<br>An integer which is a bit-wise ORed value of the following constants:

* ''role''<br>An integer which is a bit-wise ORed value of the following constants:

** ''0x1'', author is registered in the Sugar Network (and ''guid'' key is set);

** ''0x1'', author is registered in the Sugar Network (and ''guid'' key is set);

** ''0x10000'', author is the original author of the corresponding resource; if it is not set, user is only a maintainer, e.g., an uploader of a book which has its original authors.

** ''0x10000'', author is the original author of the corresponding resource; if it is not set, user is only a maintainer, e.g., an uploader of a book which has its original authors;

* ''avatar''<br>An url to author's avatar.

<div id="resource-status"></div>

<div id="resource-status"></div>

'''Context.type'''

'''Context.type'''

* ''activity'', Sugar activity;

* ''activity'', Sugar application;

* ''book'', books in various forms;

* ''book'', books in various forms;

* ''talks'', offline discussion groups;

* ''group'', a social group of related activities;

* ''project'', general purpose context to group related Post objects;

* ''talks'', sub-type to mix-in offline discussion forum;

* ''package'', GNU/Linux package metadata.

* ''project'', sub-type to mix-in issue tracker and polling functionality.

Context type specifies how context, and all related resources, can be used. For example, ''activity'' type assumes activity bundles uploaded to the ''Context.releases'' property, or, ''project'' contexts might have associated ''issue'' type Post objects.

Context type specifies how context, and all related resources, can be used. For example, ''activity'' type assumes activity bundles uploaded to the ''Context.releases'' property, or, [[#post-type|Post.type]] depends on Context type it was created for.

<div id="context-releases"></div>

<div id="context-releases"></div>

Contexts with ''activity'' or ''book'' types might have releases, i.e., activity or book versions that users can download. The ''releases'' property is aggregated where each item describes one particular version. There is no need in working with the ''releases'' property directly, there are high-level API commands to [[Sugar_Network/API#Upload_releases|upload]] and [[Sugar_Network/API#Retrieving_releases|download]] releases.

Contexts with ''activity'' or ''book'' types might have releases, i.e., activity or book versions that users can download. The ''releases'' property is aggregated where each item describes one particular version. There is no need in working with the ''releases'' property directly, there are high-level API commands to [[Sugar_Network/API#Upload_releases|upload]] and [[Sugar_Network/API#Retrieving_releases|download]] releases.

<div id="post-topic"></div>

<div id="post-topic"></div>

'''Post.topic'''

'''Post.topic'''

Post objects might belong to a topic post. The system design assumes only a two-level Posts hierarchy.

Only ''post'' type Post objects belong to a parent Post which guid should be specified in the ''topic'' property. The system design assumes only a two-level Posts hierarchy.

<div id="post-type"></div>

<div id="post-topic"></div>

 

 

'''Post.type'''

Resolutions for ''issue'' Post objects:

* ''duplicate'', the issue is a duplicate, closed.

* ''topic'', general purpose top-level Post;

Resolutions for ''poll'' Post objects:

* ''open'', the poll is open for votes;

* ''closed'', the poll is closed for votes.

* ''question'', Q&A request (topic);

* ''issue'', problem with the Context (topic);

* ''idea'', an idea for the Context (topic);

* ''notice'', auto-generated Post for updates within the Context (topic);

* ''solution'', solution for question, issue, or, idea (post).