OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (COEL-188) Default issue in Reliability

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

David Snelling commented on COEL-188:

We agree that we don't intend to require a default value always exist, i.e. missing reliability is acceptable.
We agree that 100% should be used as the mechanism for correcting a error, with additional errors require reloading of atoms.
We agree that Reliability is not some kind of global standard.

> Default issue in Reliability
> ----------------------------
>                 Key: COEL-188
>                 URL: https://issues.oasis-open.org/browse/COEL-188
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>            Reporter: David Snelling
> In Section 5.2.7 on the Reliability field we say 'The Default shall be 50' and I was left wondering what this means to an implementer. This is an optional field so if an Atom submitter omits the field but then later issues a query for all atoms with Reliabilty = 50% should they expect to see that Atom returned? I don't think so: we don't want to create an implicit requirement on a data engine to store a value of 50. 
> I think what we mean here is to guide users to what this value means so perhaps we soften the statement to say that a value of 50% is regaded as typical. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]