[iot.schema.org] questions regarding the current schema design.

[Jason Koh]

Hi all, (probably to Darko and Michael)

This is Jason Koh, a PhD student, a Brick (brickschema.org) developer. 

I am trying to align Brick to iot,schema.org as we discussed last time, and have some questions in the schema design.

In this example: 

1. In this example, is otTemperature a class or instance? Or, do we even distinguish them? In my understanding, iot.Temperature would be an instance, but predefined vocabulary to annotate some "things". Is this right?

2. iot.Temperature here has "isPropertyOf {"@type": "iot:Room"}".

    2.1. Here, is the instance or iot:Room an instance of Room, right?

    2.2. Is it allowed to associate an instance (a room) with a class (Temperature) in this way?

    2.3. What is the difference between "{@type: iot:Room} in the second entity and the third entity?

3. Capability providesInteractionPattern Something sounds weird to me. Maybe I misunderstood what Capability is. For example, does "SoundPressureCapability" mean something that is capable of measuring/actuating SounePressure?

4. (probably to Darko) In the previous Haystack alignment, I see that equip is aligned to Capability. It confuses me based on its definition (Capability := A property that relates an interaction pattern with its capability.). How can equip be a property? Sorry if I missed the explanation in the previous presentation.

The underlying questions behind the above questions are

1. Do we want to distinguish A-Box and T-Box clearly? (The trade-off between the easiness and the correctness, I'd say)

2. What is the clear definition of Capability? 

Sorry if I missed things already well presented before, but it'd help me to correctly design anything further.

Thanks!

With regards,

Jason Koh

cseweb.ucsd.edu/~jbkoh