GithubHelp home page GithubHelp logo

iotdatamodels's People

Contributors

codey-insightdesigns avatar dalexj avatar darshakthakore avatar dongjoo7-kim avatar hongkicha avatar joochlee avatar jrover avatar marktrayer avatar namyeongkim avatar oicadmin avatar qiang0428 avatar raintamer avatar rsbells avatar sungdongkim9 avatar sunheebaek avatar toppaste avatar upnp avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

iotdatamodels's Issues

Inconsistency in the id name selection of json schema files.

Out of the 64 json-schema files, 22 have an id termination in ‘.json’ but the remaining don't have it.

http://openinterconnect.org/schemas/oic.create.json#",
http://openinterconnect.org/schemas/oic.r.button.json#",
http://openinterconnect.org/schemas/oic.r.energy.overload.json#",
http://openinterconnect.org/schemas/oic.r.mediaSource.json#",
http://openinterconnect.org/schemas/oic.r.mediaSourceList.json#",
http://openinterconnect.org/schemas/oic.r.nightMode.json#",
http://openinterconnect.org/schemas/oic.r.sensor.activity.count.json#",
http://openinterconnect.org/schemas/oic.r.sensor.atmosphericPressure.json#",
http://openinterconnect.org/schemas/oic.r.sensor.carbonDioxide.json#",
http://openinterconnect.org/schemas/oic.r.sensor.carbonMonoxide.json#",
http://openinterconnect.org/schemas/oic.r.sensor.contact.json#",
http://openinterconnect.org/schemas/oic.r.sensor.glassBreak.json#",
http://openinterconnect.org/schemas/oic.r.sensor.heart.zone.json#",
http://openinterconnect.org/schemas/oic.r.sensor.illuminance.json#",
http://openinterconnect.org/schemas/oic.r.sensor.json#",
http://openinterconnect.org/schemas/oic.r.sensor.magneticFieldDirection.json#",
http://openinterconnect.org/schemas/oic.r.sensor.motion.json#",
http://openinterconnect.org/schemas/oic.r.sensor.presence.json#",
http://openinterconnect.org/schemas/oic.r.sensor.touch.json#",
http://openinterconnect.org/schemas/oic.r.sensor.water.json#",
http://openinterconnect.org/schemas/oic.r.signalStrength.json#",
http://openinterconnect.org/schemas/oic.r.speech.tts.json#",

Question about the circuit diagram of a software thermostat

I've studied the documentation, but I still have difficulty understanding the approach.
Could you explain the principle using the example of a thermostat?

I want to make a software thermostat that switches the actuator depending on the temperature.

I got acquainted with the design of the thermostat device on the page
https://openconnectivityfoundation.github.io/devicemodels/docs/index.html
I understand correctly that the standard requires you to place two resources with the type "oic.r.temperature" and preset names "Temperature (Sensor)", "Temperature (Actuator)", the "href" to the resource can be anything. Those. other devices that want to get the temperature of the sensors of all thermostats should look for devices with the type "oic.d.thermostat" and they have resources with the rt include "oic.r.temperature" and name="Temperature (Sensor)"

Should I create my own resource type to configure my software thermostat? can I place my resource type with settings in existing resources (for example oik.con)?

How would you suggest placing the properties:

  • link to oсf device actuator
  • link to oсf device sensor
  • operating mode - heating / cooling
  • current status of the thermostat - on / off
  • current state of the actuator - on / off
  • current sensor temperature
  • desired temperature

oic.r.body.metrics.json references non existing json files

oic.r.body.metrics.json references oic.r.bodyweight.json#/definitions/oic.r.weight.fitness and oic.r.bodyheight.json#/definitions/oic.r.height.fitness. Both references are not found in repository.

  • It looks that oic.r.bodyweight.json and oic.r.bodyheight.json file names are incorrect, because we have oic.r.body.weight.json and oic.r.body.height.json commited in the repository.
  • oic.r.weight.fitness and oic.r.height.fitness are not defined in any files in repository.

duplicate id usage across different json-schema files

duplicate id usage
oic.r.airflowControl-Batch.json: "id": "http://openinterconnect.org/schemas/oic.r.airFlowControl#",
oic.r.airflowControl.json: "id": "http://openinterconnect.org/schemas/oic.r.airFlowControl#",
duplicate id usage
oic.r.door.json: "id": "http://openinterconnect.org/schemas/oic.r.door#",
oic.r.door-Update.json: "id": "http://openinterconnect.org/schemas/oic.r.door#",
duplicate id usage
oic.r.humidity.json: "id": "http://openinterconnect.org/schemas/oic.r.humidity#",
oic.r.humidity-Update.json: "id": "http://openinterconnect.org/schemas/oic.r.humidity#",
duplicate id usage
oic.r.iceMaker.json: "id": "http://openinterconnect.org/schemas/oic.r.iceMaker#",
oic.r.iceMaker-Update.json: "id": "http://openinterconnect.org/schemas/oic.r.iceMaker#",
duplicate id usage
oic.r.mode.json: "id": "http://openinterconnect.org/schemas/oic.r.mode#",
oic.r.mode-Update.json: "id": "http://openinterconnect.org/schemas/oic.r.mode#",
duplicate id usage
oic.r.operational.state.json: "id": "http://openinterconnect.org/schemas/oic.r.operational.state#",
oic.r.operational.state-Update.json: "id": "http://openinterconnect.org/schemas/oic.r.operational.state#",
duplicate id usage
oic.r.refrigeration.json: "id": "http://openinterconnect.org/schemas/oic.r.refrigeration#",
oic.r.refrigeration-Update.json: "id": "http://openinterconnect.org/schemas/oic.r.refrigeration#",
duplicate id usage
oic.r.temperature-Error.json: "id": "http://openinterconnect.org/schemas/oic.r.temperature#",
oic.r.temperature.json: "id": "http://openinterconnect.org/schemas/oic.r.temperature#",

This is on both OIC-Release-1.0.0 and master

How do you actuate a oic.r.door ?

There is no public discussion group or forum. so this place seems best to ask this question.

I want to create a oic.d.garagedoor device which must have a oic.r.door resource. But I can not actuate the door as the openState property on the oic.r.door resource is readOnly.

Is this an oversight? How can I request a garage door to be explicitly open or closed?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.