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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-if message

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

Subject: [OASIS Issue Tracker] Commented: (EMFW-18) DE 2.0 Cleanup of How Defaults are Explained in the Spec

    [ http://tools.oasis-open.org/issues/browse/EMFW-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29689#action_29689 ] 

Martena Gooch commented on EMFW-18:

Should the DE 2.0 data dictionary in the specification be revised to clarify the use of defaults?  

 Yes. First, StatusKindDefault and StatusKindValueList were left out of the data dictionary unintentionally, so those should be added. Second, to better explain defaults, a section 1.3.4 "Value Lists and Defaults" will be added to the specification with two paragraphs, one explaining Value Lists and their benefits and the other explaining how defaults work. 

Reference: 02-28-12-Minutes-IF-Subcommittee Meeting Notes 

Action Items for the IF Subcommittee. 

We need to modify the specification section 1.3.4 "Value Lists and Defaults" by add two paragraphs, one explaining value lists and how they provide flexibility and avoid the problems with hard-coded enumerated lists, and then a paragraph 2 explaining how defaults work. 
Provide examples of both these elements.

> DE 2.0 Cleanup of How Defaults are Explained in the Spec
> --------------------------------------------------------
>                 Key: EMFW-18
>                 URL: http://tools.oasis-open.org/issues/browse/EMFW-18
>             Project: OASIS EDXL Distribution Element
>          Issue Type: Improvement
>          Components: Specification
>    Affects Versions: csprd01 - Public Review Draft #1
>         Environment: Glenn Pearson
>            Reporter: Jeff Waters
>            Priority: Minor
>             Fix For: csprd01 - Public Review Draft #1
> How to use the default list mechanism was not indicated in the DOM diagram, nor described generally, nor easily discerned from the Data Dictionary elements.  I was wondering if the default list element is (a) an interposed level around the standard list element, (b) a replacement for the standard list element, or merely (c) an example of a standard list element.  It was only by looking at the example schema that I could see that the general pattern is that of (a):
> <someElement>
>   <ct:ValueListURL>myUNI</ctValueListURL>
>   <ct:Value>aValue</ct:Value>
> </someElement>
> Or
> <someElement>
>   <someElementDefault>
>     <ct:valueListURL>someElement'sDefaultUNI</ctValueListURL>
>     <ct:Value>aValueFromDefaults</ct:Value>
>   </someElementDefault>
> </someElement>
> The descriptions of the defaulting mechanism is not handled in a uniform manner.  So for example, DistributionStatus is a single entry in the Data Dictionary, whereas DistributionKind also has DistributionKindDefault and DistributionKindValueList defined.  I could be wrong, but I don't think you're trying to make a distinction here.

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]