[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OBIX-98) Support for Encodings is optional in specification narrative, but seems always required for Servers
[ https://tools.oasis-open.org/issues/browse/OBIX-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Gemmill updated OBIX-98: ------------------------------- Summary: Support for Encodings is optional in specification narrative, but seems always required for Servers (was: Support for Encodings is optional in specification narrative, but seems always requried for Servers) > Support for Encodings is optional in specification narrative, but seems always required for Servers > --------------------------------------------------------------------------------------------------- > > Key: OBIX-98 > URL: https://tools.oasis-open.org/issues/browse/OBIX-98 > Project: OASIS Open Building Information Exchange (oBIX) TC > Issue Type: Improvement > Components: OBIX 1.1 Specification > Affects Versions: OBIX 1.1 PR02 > Environment: TAB Review > Reporter: Toby Considine > Assignee: Craig Gemmill > Priority: Minor > > "Section 5 Lobby says: > ""Servers SHOULD include the encodings supported in the encodings Lobby Object. "" > But conformance clause says: > ""5. The Lobby MUST provide a list of the encodings supported."" > Although technically it is OK for a conformance clause to strengthen a normative statement from the specification body, it is unclear why the Lobby section 5 from the start does not make the mandatory requirement itself. There does not seem to be another way to conform for Servers, that needs to keep that optionality." -- 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]