[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-147) Psuedo schema in section 1.7 is not sufficient
[ http://tools.oasis-open.org/issues/browse/CAMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35885#action_35885 ] Martin Chapman commented on CAMP-147: -------------------------------------- should we need to do this, suggest: Add a new rule in our pseudo-schema for non terminals and go through the document to change all non-terminals to this notation e.g. Plan, ArtifactSpecification, ServiceSpecification, and ContentSpecification in 4.3. The propsoed new rule is: . • An expression surrounded in dollar signs, "$" and "$", indicates a non-terminal symbol which must be replaced with values according to the pseudo-schema defined for the expression. For example if the the pseudo-schema for "digit" is "0|1|2|3|4|5|6|7|8|9" then $digit$" can be used in other places rather than repeating the pseudo-schema "0|1|2|3|4|5|6|7|8|9". > Psuedo schema in section 1.7 is not sufficient > ---------------------------------------------- > > Key: CAMP-147 > URL: http://tools.oasis-open.org/issues/browse/CAMP-147 > Project: OASIS Cloud Application Management for Platforms (CAMP) TC > Issue Type: Bug > Components: Spec > Reporter: Anish Karmarkar > > Psuedo schema in section 1.7 is not sufficient for describing the YAML and JSON that we need in the spec. Specifically it does not allow one to specify non-terminal symbols. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]