[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (EMFW-17) DE 2.0 Isuspect the XLink feature will solve the problem about how to tie related content objects &descriptions together, but what we have here as description is both repetitive (almost-the-same paragraph many times in Data Dictionary Comments) & opaque.
[ http://tools.oasis-open.org/issues/browse/EMFW-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29745#action_29745 ]
Martena Gooch commented on EMFW-17:
-----------------------------------
Add to the specification a section 1.3.5 "Linking Content Objects and other DE Components" and provide a better explanation of the linking mechanism. Then provide a simple statement in the comments of each item with XLink attributes that "This element can be the source or destination for a link. See Section 1.3.5."
Reference: 02-28-12-Minutes-IF-Subcommittee Meeting Notes
----
Action Items for the IF Committee
We need to modify the specification section 1.3.5
> DE 2.0 Isuspect the XLink feature will solve the problem about how to tie related content objects &descriptions together, but what we have here as description is both repetitive (almost-the-same paragraph many times in Data Dictionary Comments) & opaque.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMFW-17
> URL: http://tools.oasis-open.org/issues/browse/EMFW-17
> 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
>
>
> I suspect the XLink feature will solve the problem about how to tie related content objects & descriptions together, but what we have here as description is both repetitive (almost-the-same paragraph many times in Data Dictionary Comments) and opaque. How about just having a separate section, that gives actual examples of how, say, 3 EDXL-embedded items can be grouped with this mechanism?
--
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]