[OASIS Issue Tracker] (OBIX-223) Section 5 versioning requirements violate SHOULD rules about Extent in Section 9.3

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

    [ https://issues.oasis-open.org/browse/OBIX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59607#comment-59607 ] 

Craig Gemmill  commented on OBIX-223:
-------------------------------------

Upon re-reading Sections 5 and 9, I think the existing language is acceptable.  Other opinions?

> Section 5 versioning requirements violate SHOULD rules about Extent in Section 9.3
> ----------------------------------------------------------------------------------
>
>                 Key: OBIX-223
>                 URL: https://issues.oasis-open.org/browse/OBIX-223
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Bug
>          Components: OBIX 1.1 Specification
>    Affects Versions: OBIX 1.1 WD39
>            Reporter: Craig Gemmill 
>            Assignee: Craig Gemmill 
>
> The requirement to put the version and/or retrieval time in as a child element sort of violates the rule about Extent in 9.3, which is that you only use non-refs for primitive children with no further extent; complex children should generally be represented with refs.  Conceptually I think it’s helpful not to have to ask again for these additional details, but it is the first place a client looks, and it violates the rule.  The ‘rule’ is a should, not a must, so it’s not a definite problem, but still worth noting and considering.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)