[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OBIX-241) Definition of Contract List and place in the type system
[ https://issues.oasis-open.org/browse/OBIX-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Cox updated OBIX-241: ----------------------------- Resolution: Editor review and correct as needed. > Definition of Contract List and place in the type system > -------------------------------------------------------- > > Key: OBIX-241 > URL: https://issues.oasis-open.org/browse/OBIX-241 > Project: OASIS Open Building Information Exchange (oBIX) TC > Issue Type: Bug > Components: OBIX 1.1 Specification > Affects Versions: OBIX 1.1 WD39 > Environment: William Cox (edited by moving typo to OBIX-245 ) > Reporter: William Cox > Assignee: William Cox > Priority: Minor > Fix For: OBIX 1.1 WD43 > > > Contract List is defined at Line 1132 "An Object's Contract List may specify multiple Contract URIs to implement". Suggests that there are 1..* Contract URIs in a list. > Can there be zero? Is an empty string (Nil or Null) OK? > Line 1027 (Section 7.2): a list of URI references... > Suggests again that a Contract a single URI reference,and a Contract list has 1..* Contracts. > Is a Nil list (as in the initialization for Op::in Figure 4-1 that empty list? So a Contract List can have 0..* elements? > Contract seems conflated with Contract List in Figure 4-1. -- 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]