## Please put instances of this task in the subfolder Tasks/ with name for the number, and subfolders as approproate, e.g. Tasks/X/Y
## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting
## as they may become relevant later on.
## Headline like "Task Implement Backup"
= Task Review Interface =

## Task title
 Title:: Review Interface

## Valid states: "Not started", "In progress" and "Finished"
 State:: Not started

## The time used is measured in man days and does not include the time spent on any sub-tasks. As a rule of thumb, time should always be allocated to subtasks, rather than parent tasks. Format: Xmd
 Time used:: 

##  As time used
 Time estimated:: 5md

== Description ==

## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions.
## Any available (technical) details goes into the below documentation pages.

Review and approve the interface for the charac service. This include the soap interface, the java interface, the possible rest interface and the return values. These must all be of such a nature that this interface can be used to wrap many different tools. Look at the planets interfaces for this.
## == Sub tasks ==
## [[PageDicts(Tasks/6/1/\d+$, Title, State, Time used, Time estimated)]]

== Documentation ==

## The documentation section links to the documentation relevant to this task and its sub-tasks (if any).
##
## The below links will automatically be expanded to page names like "Tasks/X/Y/AnalysisDocument" in your created page.
## This should be a proper default.
##
## DO NOT comment out these links.
 * [[Tasks/6/1/AnalysisDocument|Analysis Document]]
 * [[Tasks/6/1/DesignDocument|Design Document]]
 * [[Tasks/6/1/SystemMaintenanceDocument|System Set-up and Maintenance Document]]

== Progress history ==
<<PageDicts(Actions/,Iteration,Time used,Status,Notes,Tasks adressed,Tasks adressed ~= Tasks/6/1)>>

## Add information about about the current state of the task here. That is, information about what has been completed so far and
## what outstanding issues are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.