[[BackLinksMenu]]

[[TicketQuery(summary=GROUP_RESOURCE_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]

= Analysis =
^(Give as much as possible of the needed information for designing and implementing the task in the following sections.)^

== Overview ==
Define a stable resource design. Explain and document what is achieved.
Resource is an object that can exist by itself and can be persisted. Some of the resources can be used as frame content or a timeline. Resources can be nested in other resources (i.g. book can have nested another book (embedded book)).[[BR]]

Base resource model should have the following information
 * UUID
 * Content
  * Data
  * URL
 * MetaInfo (comments, versions, names, etc...)

Types of resources
 * Text
  * Plain
  * RTF
  * HTML
 * Image
 * Audio
 * Movie
 * Book
 * Templates
 * User
 * Group
 * Book
 * Page
 * Frame
 * Workspace
 * Server Root

MetaInfo of the resource is:
 * The name of the resource
 * The author of the resource
 * The date the resource was created
 * Version of the resource
 * The date the resource was last modified
 * Who was the last that modified the resource
 * The dimensions of the image (if the target of the resource is an image)
 * etc.

Operations over a resource:
 * The resource can be created.
 * The resource can be modified (in a separate window).
 * The resource can be deleted.
 * The resource can be persisted.
 * The resource can be uploaded (downloaded) to a server, which is the same thing as persisting but on the server.
 * The resource can be previewed (in a separate window).

== Task requirements ==
 * Define which properties should be immutable, default, list, etc.
 * Define a way to refer (access) resources
  * The resource reference should be like UID
  * The resource reference should allow finding the resource even if it is not loaded yet (location)
  * The reference mechanism should handle the case when the resource is not available (for example - server not available)
 * Define methods for
  * Checking if a resource is available (this should be different from get method)
   * This should update the status property
  * Getting resource location
  * Resource getting it's parent
  * Resource getting list of it's children
  * Attaching a resource to another resource
  * Detaching a resource from another resource
  * Renaming a resource (Ensure that the locations will be preserved and the new name doesn't collide with the names of the resources-siblings)
  * Cloning/Copying a resource
 * Explain annotations 
{{{
 * annotations related to Resources
  * explain ownership related with Resources and use of @Own
  * make a parallel with referencing Resources
  * An annotation that marks a property in a resource as metadata
}}}
 * Document the defined structure 
 * Apply the defined structure for the existing resources (this may be postponed)
== Task result ==
The result of this task is source code and wiki pages.

== Implementation idea ==
The reference id can be combination of unique id and path like in operating system. Refering children and other resources will be easy (./ ../ etc) 

== Related ==
[wiki:GROUP_CHANGE_R0]

== How to demo ==
Show source code, working current resource viewer (maybe a palette), unit tests.

= Design =
^(Describe your design here.)^

= Implementation =
^(Describe and link the implementation results here (from the wiki or the repository).)^

= Testing =
^(Place the testing results here.)^

= Comments =
^(Write comments for this or later revisions here.)