Changes between Version 8 and Version 9 of ZooWebSite/ZooServices/ZCFGReference

Timestamp:

Jan 16, 2011, 6:06:18 AM (14 years ago)

Author:

djay

Comment:

--

ZooWebSite/ZooServices/ZCFGReference

@@ -12 +12 @@
 
 '''The ZOO Service Configuration File is case sensitive.'''
+
 == Main metadata informations ==
 
-The fist part in a ZOO Configuration contains the metadata informations relatives to the service. Note that the "name of your service", between bracket on the first line, have to be the exact same name as the function you defined in you service code.
+The fist part in a ZOO Configuration contains the metadata informations relatives to the service. Note that the "name of your service", between bracket on the first line, have to be the exact same name as the function you defined in your services provider code.
 
 You can see bellow a description of the main metadata informations:
@@ -34 +35 @@
 == List of Inputs ==
 
-The list of inputs contains metadata information of each defined input and it is a {{{<DataInputs>}}} node.
+The list of inputs contains metadata information of each supported input and they are grouped using a {{{<DataInputs>}}} node.
+
+Each input is defined as :
+  * a name (between brackets as for the name of the service before)
+  * various medata properties ({{{Title}}}, {{{Abstract}}}, {{{minOccurs}}} and {{{maxOccurs}}})
+  * a Type Of Data node ([#TypeOfDataNodes description])
 
 A typical list of inputs ({{{<DataInputs>}}}) look like the following:
@@ -59 +65 @@
 == List of Outputs ==
 
-The list of outputs is similar to a list of inputs except it is designed as a {{{<DataOutputs>}}} node.
+The list of outputs is very similar to a list of inputs except it is designed as a {{{<DataOutputs>}}} node.
 
 A typical {{{<DataOutputs>}}} node look like the following:
@@ -126 +132 @@
 === !ComplexData node ===
 
-A ComplexData node get a {{{<Default>}}} and one or more {{{<Supported>}}} nodes depending on the number of supported format. A format is this set of properties : {{{mimeType}}}, {{{encoding}}} and optionaly {{{schema}}}.
+A !ComplexData node get a {{{<Default>}}} and one or more {{{<Supported>}}} nodes depending on the number of supported format. A format is this set of properties : {{{mimeType}}}, {{{encoding}}} and optionaly {{{schema}}}.
 
-For output ComplexData nodes, you can add the {{{extension}}} property to define what extension to use to name the file when storing the result is required. Obviously, you'll have to add the extension to each supported format. You can also add the {{{asReference}}} property for each input to define if the output should be stored on server side per default. Note, that the client can always modify this behavior setting {{{asReference}}} attribute to {{{true}}} or {{{false}}} for this output in the {{{ResponseDocument}}}.
+For output !ComplexData nodes, you can add the {{{extension}}} property to define what extension to use to name the file when storing the result is required. Obviously, you'll have to add the extension to each supported format. You can also add the {{{asReference}}} property for each input to define if the output should be stored on server side per default. Note, that the client can always modify this behavior setting {{{asReference}}} attribute to {{{true}}} or {{{false}}} for this output in the {{{ResponseDocument}}}.
 
-You can see above a sample ComplexData node for default {{{application/json}}} and {{{text/xml}}} mimeTypes support:
+You can see above a sample !ComplexData node for default {{{application/json}}} and {{{text/xml}}} mimeTypes support:
 {{{
 #!Lineno