Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Sat, 31 Aug 2013 17:42:51 +0000 (UTC)
From: "Shameera Rathnayaka (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12665068.1377189302493.65067.1377970971573@arcas>
In-Reply-To: <JIRA.12665068.1377189302493@arcas>
References: <JIRA.12665068.1377189302493@arcas>
Subject: [jira] [Updated] (AIRAVATA-906)  [GSoC-2013] Service and
 Applictation JSON Schemas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AIRAVATA-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shameera Rathnayaka updated AIRAVATA-906:
-----------------------------------------

    Attachment: JSONSchema_upadte.patch

Hi Suresh, 

All schemas should be under draft-04, I have updated the patch according to that. Thanks for pointing that out. we don't need to provide "required" parameter in every JSON property this is an improvement done by draft-04. we can define required property in outer object as an json array ( eg: "required": ["name" , "value"]  this means name and value properties are required for that particular object but other properties define it not required). 

Following is a simple unbounded array
"tags": {
            "type": "array",
            "items": {
                "type": "string"
            }
        }
 we can define min and max count using "minItems" and "maxItems" properties.  

Thanks,
Shameera.
                
>  [GSoC-2013] Service and Applictation JSON Schemas  
> ----------------------------------------------------
>
>                 Key: AIRAVATA-906
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-906
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Shameera Rathnayaka
>         Attachments: JSONSchema.patch, JSONSchema_upadte.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira