[OASIS Issue Tracker] Updated: (EMFW-4) DE 2.0 Schema Cleanup Issues

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Martena Gooch updated EMFW-4:
-----------------------------

        Summary: DE 2.0 Schema Cleanup Issues  (was: DE 2.0 Schema Cleanup Issue- Line 111 in DE Schema is not needed)
    Description: 
Misc issues related to schema cleanup are captured in this ticket

Line 111 in DE schema is not needed:
<xs:anyAttribute namespace="##other" processContents="lax"/>

  was:
Line 111 in DE schema is not needed:
<xs:anyAttribute namespace="##other" processContents="lax"/>


Special Meeting  June 4, 2012

EMFW-4 TOPIC 8: Change IncidentID to ContentID, then require ContentID, and Remove Incident Description

The suggestion is that a ContentID is important and useful and so should be required. At the same time, the IncidentID field is not widely used and could be renamed ContentID.
 (The ContentID could still be set to the id of the incident if desired) Then the Incident Description could also be removed, since there is already a ContentDescription element. There are perhaps better places to id and describe incidents.  On the other hand, the members previously discussed the IncidentID issues and determined that it was important to some members of the community and should be preserved for that reason. Is that still an overriding issue?

Potential Resolution: The IncidentID and IncidentDescription elements are a bit of an anachronism, so change the name of IncidentID to ContentID and remove the ContentDescription element.


EMFW-4 TOPIC 9: Version Attribute

The suggestion initially was that perhaps we need a "version" attribute to identify which version of the DE we are using; however, upon reflection, it appears the use of the namespace is unique and serves as an appropriate way to identify the version.

Potential Resolution: No change required.

EMFW-4 TOPIC 10: Non-XML - Require URI, ContentData, or both

Currently, "OtherContent" is specified using a "Uri" element or "ContentData" but neither is required. The suggestion is that either one or both should be required.

Potential Resolution: Modify the schema to ensure that either one or both of "Uri" or "ContentData" is required for "OtherContent"


> DE 2.0 Schema Cleanup Issues
> ----------------------------
>
>                 Key: EMFW-4
>                 URL: http://tools.oasis-open.org/issues/browse/EMFW-4
>             Project: OASIS EDXL Distribution Element
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: csprd01 - Public Review Draft #1
>         Environment: Mitre-Don McGarry
>            Reporter: Martena Gooch
>            Priority: Minor
>             Fix For: csprd01 - Public Review Draft #1
>
>
> Misc issues related to schema cleanup are captured in this ticket
> Line 111 in DE schema is not needed:
> <xs:anyAttribute namespace="##other" processContents="lax"/>

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