[OASIS Issue Tracker] Commented: (ENERGYINTEROP-215) Remove 0-* asoptional requirements/services/elements as it creates interoperabilitychallenges (WD15, ln 643-649)

[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23624#action_23624 ] 

Girish Ghatikar  commented on ENERGYINTEROP-215:
------------------------------------------------

Bill: 
The 0..* cardinality also exists in Figure 10. In general, it's not a good idea as this parent/child relationship exposes to orphans. This will create issues later with conformance and testing and interoperability requirements. We should try to address "optionality." If we want a relationship/attribute, let's have it. Otherwise, exclude it.


> Remove 0-* as optional requirements/services/elements as it creates interoperability challenges (WD15, ln 643-649)
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-215
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-215
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 line 643 wd16 line 643
>            Reporter: Girish Ghatikar 
>            Assignee: Girish Ghatikar 
>             Fix For: wd17
>
>
> Remove 0-* as optional requirements/services/elements as it creates interoperability challenges (WD15, ln 643-649).

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