Differences between revisions 1 and 13 (spanning 12 versions)
Revision 1 as of 2009-12-18 13:56:15
Size: 158
Editor: eab
Comment:
Revision 13 as of 2010-03-17 13:12:29
Size: 1572
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
A collection template describes the used [:GuidelinesForNewDatamodel/PatternLanguage: Pattern language], i.e. the used patterns that make up the collection. = Collection Name =
The purpose of the collection document is two-fold it is a documentation of the

In general use references to patterns and other collections to allow new collection authors to be "standing on the shoulders of giants"~-[[http://en.wikipedia.org/wiki/Bernard_of_Chartres|[quote]]]-~.

=== Is part of collection ===

Default is:

isPartOfCollection doms:Root_Collection

=== Contains, sub collections and objects ===

This can be whatever is contained within.

== Pattern expression ==
Write your pattern expression here, it's the rationale behind the collections structure.

Let the expression be your dreams, ideas and thoughts for the collection.


== Collection description ==
Sum up the elements in the collection here, if you feel that you need to justify parts of your collection, and have asserted that your plan is sound. Include the rationale here, if possible back it up with new patterns describing your special collection.

== Workflow ==
This is the manual, if you want people to [[http://en.wikipedia.org/wiki/RTFM|RTFM]] make a [[http://en.wikipedia.org/wiki/Technical_writing#Example|FM]]

Describe the intended usage of and content addition to this collection, use all available measures that help clarify on the subject. Consider images in addition to text.

== Technical ==
Be concrete and go into detail of things that require it, especially parts of the collection that is complex or of a special nature.

Consider using a drawing to illustrate relations or for instance include code/XML snippets.

Collection Name

The purpose of the collection document is two-fold it is a documentation of the

In general use references to patterns and other collections to allow new collection authors to be "standing on the shoulders of giants"[quote].

Is part of collection

Default is:

isPartOfCollection doms:Root_Collection

Contains, sub collections and objects

This can be whatever is contained within.

Pattern expression

Write your pattern expression here, it's the rationale behind the collections structure.

Let the expression be your dreams, ideas and thoughts for the collection.

Collection description

Sum up the elements in the collection here, if you feel that you need to justify parts of your collection, and have asserted that your plan is sound. Include the rationale here, if possible back it up with new patterns describing your special collection.

Workflow

This is the manual, if you want people to RTFM make a FM

Describe the intended usage of and content addition to this collection, use all available measures that help clarify on the subject. Consider images in addition to text.

Technical

Be concrete and go into detail of things that require it, especially parts of the collection that is complex or of a special nature.

Consider using a drawing to illustrate relations or for instance include code/XML snippets.

CollectionTemplate (last edited 2010-03-17 13:12:29 by localhost)