[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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:all-tabpanel ]
Martena Gooch updated EMFW-17:
------------------------------
Special Meeting June 4, 2012
EMFW 17 TOPIC 7: Link should be inside content object
Currently, multiple "Link" elements can exist after all the ContentObject elements, at the end of the "Content" element. The advantage of this solution is that all the links are together and they can support linking content objects or global elements of the DE (or potentially other xml). The suggestion is to allow the "Link" element to occur within each ContentObject element. This may have an advantage in that it can allow links to appear more locally to their respective content object; however, it may have some disadvantages, distributing links across the schema and enabling unrelated links inside a content object. We might have to play with some examples to explore this.
Potential Resolution: Unclear without some exploration.
> 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]