Schema Limitations

Standard JSON

• Standard JSON is not namespace-aware. All the elements, types, and attributes must be in a single namespace. No foreign namespace elements or attributes are supported.
• Global attributes are not supported in the schema, for a REST service with Standard JSON as the media type.
• For Standard JSON, the elementFormDefault attribute must always be set to qualified.
• To pass an attribute using JSON, you must represent it as "@Key": "Value". That is, prefix the key with "@". For example, the following payload works:

  {
  "PersonDetailsInputNestedElements": {
  "PersonDetailsInputElementComplexType":
  { "@PersonDOB": "2001-10-26T21:32:52", "@PersonName": "Mr Person" }
  ,
  "FriendDetailsInputElementComplexType":
  { "@PersonDOB": "2001-10-26T21:32:52", "@PersonName": "Mr Friend" }
  }
  }

  This convention is not specified by Standard JSON; it is specific to the TIBCO implementation.