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


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

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

Subject: [OASIS Issue Tracker] (CAMP-193) handling of 'sensor_type' attribute of 'sensor resource' is vague

Gilbert Pilz created CAMP-193:

             Summary: handling of 'sensor_type' attribute of 'sensor resource' is vague
                 Key: CAMP-193
                 URL: https://issues.oasis-open.org/browse/CAMP-193
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Spec
    Affects Versions: 1.2
         Environment: Section numbers as per WD 04 of CAMP 1.2.
            Reporter: Gilbert Pilz
            Assignee: Gilbert Pilz
            Priority: Minor
             Fix For: 1.2

The section that describes the 'sensor_type' attribute of the 'sensor resource' (section 5.26.3 in WD 04) reads:
This attribute specifies the type of the data that this sensor resource collects. For example, "String", "Timestamp". Attribute types are defined in Section 5.2, “Attribute Types”. type_definitions may also be used to specify types. See Section 5.18, “type_definitions Resource”.
When we say 'type_definitions may also be used' it's not clear what Consumers should expect the value of this attribute to be. One could guess that the value is supposed to be the name of the type, but that would only be a guess. An equally valid guess might be the URI of the 'type_definition resource' that defines the type of the sensor. In any case there is an interoperability problem here in that independent implementations might make different, but equally valid, guesses.

This message was sent by Atlassian JIRA

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