OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sdd message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (SDD-25) v1.1 Primer Update



     [ http://tools.oasis-open.org/issues/browse/SDD-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brent Miller  updated SDD-25:
-----------------------------

    Description: 
Placeholder for all updates to the Primer to accompany specification version 1.1. Many Primer updates will correspond to Examples updates.

Planned updates:
1. Any updates necessary in response to updates made to SDD examples.
2. Describe uniqueness requirements/recommendations for RequirementType id property (MUST be unique within a deployment descriptor; SHOULD be unique across aggregated deployment descriptors if possible; MAY use, e.g., deploymentDescriptor id.RequirementType id (that is, use deploymentDescriptor id as a "namespace") as one method of distinguishing ids that might not be unique across aggregated deployment descriptors. See 02/04/2010 meeting minutes.

  was:Placeholder for all updates to the Primer to accompany specification version 1.1. Many Primer updates will correspond to Examples updates.


> v1.1 Primer Update
> ------------------
>
>                 Key: SDD-25
>                 URL: http://tools.oasis-open.org/issues/browse/SDD-25
>             Project: OASIS Solution Deployment Descriptor (SDD) TC
>          Issue Type: Improvement
>         Environment: Non-normative documentation.
>            Reporter: Brent Miller 
>            Assignee: Brent Miller 
>            Priority: Minor
>
> Placeholder for all updates to the Primer to accompany specification version 1.1. Many Primer updates will correspond to Examples updates.
> Planned updates:
> 1. Any updates necessary in response to updates made to SDD examples.
> 2. Describe uniqueness requirements/recommendations for RequirementType id property (MUST be unique within a deployment descriptor; SHOULD be unique across aggregated deployment descriptors if possible; MAY use, e.g., deploymentDescriptor id.RequirementType id (that is, use deploymentDescriptor id as a "namespace") as one method of distinguishing ids that might not be unique across aggregated deployment descriptors. See 02/04/2010 meeting minutes.

-- 
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]