Sugar Network/Resources: Difference between revisions

Line 57:

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

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.

Line 65:

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.

'''Post.type'''

~~'''~~Post.~~topic'''~~

Choose Post types according to Context [[#context-type|types]] the Post belongs to.

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

* ''topic'', general purpose discussion; ''talks'' Contexts;

* ''review'', review the Context; ''activity'' or ''book'' Contexts;

* ''artefact'', object generated by Context application; ''activity'' Contexts;

* ''question'', Q&A request; ''project'' Contexts;

* ''issue'', problem with the Context; ''project'' Contexts;

* ''poll'', a poll within the Context; ''project'' Contexts;

* ''notice'', auto-generated Post for updates within the Context; Context type independent;

* ''post'', a comment for a parent Post object; Context type independent.

'''Post.~~type~~'''

'''Post.topic'''

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

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.

* ''review'', review the Context (topic);

* ''artefact'', object generated by Context application (topic);

* ''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);~~

* ''post'', general purpose dependent Post;

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

@@ Line 57: / Line 57: @@
 * ''package'', GNU/Linux package metadata.
-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>
@@ Line 65: / Line 65: @@
 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-type"></div>
+'''Post.type'''
-'''Post.topic'''
+Choose Post types according to Context [[#context-type|types]] the Post belongs to.
-Post objects might belong to a topic post. The system design assumes only a two-level Posts hierarchy.
+* ''topic'', general purpose discussion; ''talks'' Contexts;
+* ''review'', review the Context; ''activity'' or ''book'' Contexts;
+* ''artefact'', object generated by Context application; ''activity'' Contexts;
+* ''question'', Q&A request; ''project'' Contexts;
+* ''issue'', problem with the Context; ''project'' Contexts;
+* ''poll'', a poll within the Context; ''project'' Contexts;
+* ''notice'', auto-generated Post for updates within the Context; Context type independent;
+* ''post'', a comment for a parent Post object; Context type independent.
-<div id="post-type"></div>
+<div id="post-topic"></div>
-'''Post.type'''
+'''Post.topic'''
-* ''topic'', general purpose top-level Post;
+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.
-* ''review'', review the Context (topic);
-* ''artefact'', object generated by Context application (topic);
-* ''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);
-* ''post'', general purpose dependent Post;
-* ''solution'', solution for question, issue, or, idea (post).