Changes between Version 51 and Version 52 of S3/S3XML


Ignore:
Timestamp:
07/20/11 11:28:33 (11 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3/S3XML

    v51 v52  
    364364MCI handling is optional for non-synchronizing interfaces.
    365365==== data ====
     366
     367Represents the value of a single field in the record.
     368
     369{{{
     370<s3xml>
     371  <resource>
     372    <data>...</data>
     373  </resource>
     374</s3xml>
     375}}}
     376
    366377||'''Parent elements'''||[#resource resource]||
    367378||'''Child elements'''||''none (leaf element)''||
    368379||'''Contents'''||Text||
    369 
    370 Represents the value of a single field in the record.
    371380
    372381**Attributes:
     
    378387
    379388The text node in the {{{data}}} element provides a human-readable representation of the field value. If this representation is different from the original value in the database, then the original value must be provided by the ''value'' attribute.
     389
     390The ''value'' attribute contains a JSON representation of the field value, retaining the original data type (i.e. strings must be double-quoted) except for ''date'', ''time'' and ''datetime'' values, which are to be represented as simple strings in the respective standard format (no double quotes). The standard format for ''datetime'' values is ''YYYY-MM-ddTHH:mm:ssZ'' (ISO format, UTC), ''date'' shall be represented as ''YYYY-MM-dd'', and ''time'' as ''HH:mm:ss''.
     391
     392''data'' elements representing passwords can contain the clear text password in the ''value'' attribute, or the encrypted password in the text node. Where a clear text password is given as ''value'' attribute, it will be stored encrypted, otherwise the password will be stored as-is. Note that clear-text representation of passwords will be accepted by the interface, but never exported.
    380393
    381394(*) If the field is for file upload, a {{{url}}} attribute should be provided to specify the location of the file. The importer will try to download and store the file (file transfer) from that URL (''pull''). It is also possible to send the file with the HTTP request - in this case the {{{filename}}} must be specified instead of {{{url}}} (''push''). The ''push'' variant for uploads is meant for peers which do not support pulling for some reason (e.g. mobile phones). Normal servers would always provide a URL for download in order to allow the consuming site decide which files to download and when (saves bandwidth).