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

Timestamp:

Jan 16, 2011, 4:00:00 PM (14 years ago)

Author:

djay

Comment:

Small fixes

ZooWebSite/ZooServices/ZCFGReference

@@ -80 +80 @@
 == Type Of Data Nodes ==
 
-From the begining we spoke about Type Of Data Nodes to describe data type of inputs and outputs.
+From the begining of this ZCFG presentation, we spoke about "Type Of Data Nodes" to describe data type of inputs and outputs.
 
 You can define your data as:
@@ -87 +87 @@
   * [#ComplexDatanode ComplexData]
 
-Each Type Of Data node have at least one {{{<Default>}}} and one {{{<Supported>}}} node. Even if one of those are empty it has to be present as an opening and closing tag.
+Except for {{{LiteralData}}}, Each Type Of Data node have at least one {{{<Default>}}} and one {{{<Supported>}}} node. Even if one of those are empty it has to be present as an opening and closing tag.
 
 === !LiteralData node ===
 
-A {{{<LiteralData>}}} node get one {{{<Default>}}}, one or more {{{<Supported>}}} node depending on the number of Unity Of Mesures (UOM) and a {{{dataType}}} property. The {{{dataType}}} property define the type of literal data, a string, an interger and so on ([http://www.w3.org/TR/xmlschema-2/#built-in-datatypes complete list] of supported data types).
+A {{{<LiteralData>}}} node get one {{{<Default>}}}, zero or more {{{<Supported>}}} node depending on the existence or the number of Unity Of Mesures (UOM) and a {{{dataType}}} property. The {{{dataType}}} property define the type of literal data, a string, an interger and so on ([http://www.w3.org/TR/xmlschema-2/#built-in-datatypes complete list] of supported data types). {{{<Default>}}} and {{{<Supported>}}} nodes can get the following property : {{{uom}}} to define which UOM hav to be used for this input value.
 
-For input {{{<LiteralData>}}} nodes, you can add value to the {{{<Default>}}} properties to define a default value for this input. This means that when your Service will be run even if the input wasn't defined, this default value will be set as the current value for this input.
+For input {{{<LiteralData>}}} nodes, you can add the {{{value}}} property to the {{{<Default>}}} node to define a default value for this input. This means that, when your Service will be run, even if the input wasn't defined, this default value will be set as the current value for this input.
 
-A typical {{{<LiteralData>}}} node look like the following:
+A typical {{{<LiteralData>}}} node, defining a {{{float}}} data type using meters or degree UOM, look like the following:
 {{{
 #!Lineno
@@ -134 +134 @@
 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}}} property to each supported format (    {{{<Default>}}} and {{{<Supported>}}} nodes). You can also add the {{{asReference}}} property to the {{{<Default>}}} node to define if the output should be stored on server side per default. Note, that the client can always modify this behavior by setting {{{asReference}}} attribute to {{{true}}} or {{{false}}} for this output in the request {{{ResponseDocument}}} parameter.
 
-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}}} (encoded in UTF-8 or base64) mimeTypes support:
 {{{
 #!Lineno