[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OBIX-222) Inconsistencies in Section 5 contracts vs examples
[ https://issues.oasis-open.org/browse/OBIX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59376#comment-59376 ] Craig Gemmill commented on OBIX-222: ------------------------------------- This is now consistent as is. However, discussion on OBIX-223 may warrant changes. I think we could resolve this, and make any other changes as part of OBIX-223. > Inconsistencies in Section 5 contracts vs examples > -------------------------------------------------- > > Key: OBIX-222 > URL: https://issues.oasis-open.org/browse/OBIX-222 > Project: OASIS Open Building Information Exchange (oBIX) TC > Issue Type: Bug > Components: OBIX 1.1 Specification > Affects Versions: OBIX 1.1 WD38, OBIX 1.1 WD39 > Reporter: Craig Gemmill > Assignee: Craig Gemmill > > • Section 5 is somewhat inconsistent – the Lobby contract defines bindings as a list of str, but in the examples later in Sections 5.5.2 and 5.5.4 it describes the bindings as a list of uri. > Brian F made a comment in OBIX-212 about our original plan to use URIs for the encodings. We've changed those to str, but we need to revisit this section to make sure it is fully self-consistent. > Note the choice of of the of= value for the lists is somewhat dependent on issue OBIX-223 because, if we restrict ourselves from using complex structures according to the SHOULD rules in 9.3, then we'd have to use refs, or choose a different way to handle versioning. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]