Difference between revisions of "Uno/Meta/Organization"

From Apache OpenOffice Wiki
< Uno
Jump to: navigation, search
m (Improved layout.)
(Added Claims and States.)
Line 1: Line 1:
==Naming==
+
==Types==
 
* [[Uno/Meta/Specification|Spec]] - Specifications.
 
* [[Uno/Meta/Specification|Spec]] - Specifications.
 
* [[Uno/Meta/Implementation|Impl]] - Implementation Descriptions.
 
* [[Uno/Meta/Implementation|Impl]] - Implementation Descriptions.
Line 6: Line 6:
 
* [[Uno/Meta/Article|Article]] - An informative article about a particular topic.
 
* [[Uno/Meta/Article|Article]] - An informative article about a particular topic.
 
* <name != above> - (A sub) module or leave(of a particular module).
 
* <name != above> - (A sub) module or leave(of a particular module).
 +
 +
==States==
 +
Possible values for states:
 +
* draft - Not finished yet.
 +
* preliminary - Basically finished, no further changes expected.
 +
* final - Can be expected not to be changed.
 +
 +
==Claims==
 +
Especially needed for abstract specifications possibility implemented in various concrete [[Uno]] implementations.
 +
* required - Must be implemented by all Uno implementations.
 +
* recommended - Is recommended to be implemented.
 +
* optional - May be implemented.
  
 
==Structural Grammar==
 
==Structural Grammar==

Revision as of 16:16, 29 September 2006

Types

  • Spec - Specifications.
  • Impl - Implementation Descriptions.
  • Test - Tests against particular Specifications.
  • Effort - Something which is in the works.
  • Article - An informative article about a particular topic.
  • <name != above> - (A sub) module or leave(of a particular module).

States

Possible values for states:

  • draft - Not finished yet.
  • preliminary - Basically finished, no further changes expected.
  • final - Can be expected not to be changed.

Claims

Especially needed for abstract specifications possibility implemented in various concrete Uno implementations.

  • required - Must be implemented by all Uno implementations.
  • recommended - Is recommended to be implemented.
  • optional - May be implemented.

Structural Grammar

  • Description = ("Spec"|"Impl"|"Test")/<text>
  • Effort = "Effort"/(<submodule>/)*<text>
  • Article = "Article"/<text>
  • start = <module>/((<submodule>/)*Description|Effort|Article|"Todo")

Categories

  • Each subpage gets categorized by the category of the parent page. E.g.: Uno/Spec -category-> Uno
  • Each parent page (a page with children) forwards to its direct category page. E.g: Uno/Spec -forwards-> Category:Uno:Spec

Examples

  • Uno Specifications
Page: Uno/Spec
Purpose: Parent page for Uno specifications
Category: Uno
Content: forwards to Category:Uno
  • Binary Uno Module
Page: Uno/Binary
Purpose: Parent page for Binary Uno
Category: Uno
Content: forwards to Category Uno:Binary
  • Binary Uno specifications
Page: Uno/Binary/Spec
Purpose: Parent page for Binary Uno Specifications
Category: Uno/Binary
Content: forwards to Category Uno:Binary:Spec
  • Specifications of the Binary Uno Component Loader
Page: Uno/Binary/Component Loader/Spec
Purpose: Parent page for the Binary Uno Component Loader Specifications
Content: forwards to Category Uno:Binary:Component Loader:Spec
Personal tools