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


Ignore:
Timestamp:
Jan 16, 2011, 4:00:00 PM (10 years ago)
Author:
djay
Comment:

Small fixes

Legend:

Unmodified
Added
Removed
Modified
  • ZooWebSite/ZooServices/ZCFGReference

    v9 v10  
    8080== Type Of Data Nodes ==
    8181
    82 From the begining we spoke about Type Of Data Nodes to describe data type of inputs and outputs.
     82From the begining of this ZCFG presentation, we spoke about "Type Of Data Nodes" to describe data type of inputs and outputs.
    8383
    8484You can define your data as:
     
    8787  * [#ComplexDatanode ComplexData]
    8888
    89 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.
     89Except 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.
    9090
    9191=== !LiteralData node ===
    9292
    93 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).
     93A {{{<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.
    9494
    95 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.
     95For 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.
    9696
    97 A typical {{{<LiteralData>}}} node look like the following:
     97A typical {{{<LiteralData>}}} node, defining a {{{float}}} data type using meters or degree UOM, look like the following:
    9898{{{
    9999#!Lineno
     
    134134A !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}}}.
    135135
    136 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}}}.
     136For 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.
    137137
    138 You can see above a sample !ComplexData node for default {{{application/json}}} and {{{text/xml}}} mimeTypes support:
     138You can see above a sample !ComplexData node for default {{{application/json}}} and {{{text/xml}}} (encoded in UTF-8 or base64) mimeTypes support:
    139139{{{
    140140#!Lineno

Search

Context Navigation

ZOO Sponsors

http://www.zoo-project.org/trac/chrome/site/img/geolabs-logo.pnghttp://www.zoo-project.org/trac/chrome/site/img/neogeo-logo.png http://www.zoo-project.org/trac/chrome/site/img/apptech-logo.png http://www.zoo-project.org/trac/chrome/site/img/3liz-logo.png http://www.zoo-project.org/trac/chrome/site/img/gateway-logo.png

Become a sponsor !

Knowledge partners

http://www.zoo-project.org/trac/chrome/site/img/ocu-logo.png http://www.zoo-project.org/trac/chrome/site/img/gucas-logo.png http://www.zoo-project.org/trac/chrome/site/img/polimi-logo.png http://www.zoo-project.org/trac/chrome/site/img/fem-logo.png http://www.zoo-project.org/trac/chrome/site/img/supsi-logo.png http://www.zoo-project.org/trac/chrome/site/img/cumtb-logo.png

Become a knowledge partner

Related links

http://zoo-project.org/img/ogclogo.png http://zoo-project.org/img/osgeologo.png