ngsild-api-data-models's Issues
Update agriMushroom context for adding type AgriCropRecord
As the title says ...
Add explanatory text
We are missing a 'Description property" to make clear what this property is. We should BTW make it for all the properties
Re-ordering Graced context
Temporary fix to avoid conflicts of terms defined in several smartData contexts, typically temperature.
NGSI-LD and JSON-LD improvements and cleanups
- Use core context 1.7 by default
- Reference contexts from their GitHub page link (which is served with a JSON-LD compliant
application/ld+json
content type, as opposed to the raw view where it is served with atext/plain
content type) - Remove references to https://fiware.github.io/data-models/context.jsonld (not JSON-LD compliant) and https://schema.lab.fiware.org/ld/context.jsonld (does include the former one)
- Remove unused and / or unmaintained files
-
Prepare a custom SQL script to update existing data (and comply with points 1 to 3)
Create ngsi-ld context for Graced-Pilze use case
Create ngsi-ld context to support Graced-Pilze data model
Missing unitcode for RSSI
RSSI is express in Decibel-milliwatts (dBm)
Unit code is DBM
This is one of the units we asked UN-CEFACT to add in the list last year ;)
Cleanup the MLaaS contexts
It is currently a mess:
- there are 3 or 4 files calling each other, with non meaningful names
- the MLaaS core context has terms related to water (it should only reference ML domain)
- some terms are not used and should be removed
Typo in agriMushroom ngsild-payloads deviceElsys.json
"controlledAssest" instead of "controlledAsset"
GRACED: addition of indoor (in-growing house) sensor for Pilze
To better monitor environmental conditions in the growing houses, sensors will be deployed in the growing houses (starting with one test growing house, where two sensors will be installed).
These sensor can measure:
- temperature
- relative humidity
- CO2 concentration
As a consequence, the data model for Pilze need to be updated to take into account these new measurements.
However, context does not need to be updated, as new entity type (AgriParcelRecord) and property (co2) are already part of the context (standard ETSI and FIWARE contexts).
Just updating payload examples, adding a payload for AgriParcelRecord.
Typo in device/jsonld-contexts/
loraSNR vs loraSnr ...
Bad unit code for atmospheric pressure
The unit code for Pascal is PAL
Make sure that the sensor are not reporting in hectopascal (widely used unit for atmospheric pressure). In that case the unitcode would be A97
Missing unitcode for SNR
SNR is express in decibel (dB)
Unit code is 2N
agriMushroom model need simplification
AgriParcel and AgriParcelRecord could be merged, same for AgriCrop and AgriCropRecord.
Is weather context missing in agrifood context ?
So we decide to create contexts for specific domain. We have now weather and agrifood contexts. Question is:
- Can we have a domain context that include another domain context, e.g. typically agrifood would include the weather context ?
- Or should we define context specific to use cases, where context file will be named after the use case, and would aggregate different "domain" contexts. E.g. for GRACED Pilze, create a context pilze.json which will contain at least agrifood and weather context files.
Typo in Device-BIOC.json
typo : "controlledAssest" instead of "controlledAsset" (an additional "s")
Delete specificAccessPolicy from the egm context
specificAccessPolicy is now defined in the authrization context here .
It have to be deleted from the egm context.
Actually, it is defined in both contexts. Before deleting it, we need to update services using this property.
agriMushroom: AgriParcel: Wrong Entity type
An AgriParcel models a field parcel, i.e. a parcel having its own soil.
agriMushroom context was defined for growing mushrooms, where the mushrooms actually grow on a substrate, i.e. off ground.
Another entity type must be used instead.
Cleanup and normalize files
- Remove useless files
- Reorder terms in alphabetical order in all JSON-LD context files
- Set appropriate file suffixes (e.g., .jsonld if it is a JSON-LD file)
- Remove duplicate JSON-LD context files
Add contaminants for GRACED project
Add all contaminants required for Graced in context. List of contaminants is:
- ecoli0157
- salmonella
- imidacloprid
- acrylamide
- ochratoxinA
- deoxynivalenol
- aflatoxinB2
Update AgriMushroom for Agriculture use cases of Graced
- Change name -> Agrifood
- must support terms for TCA, Pilze & PADV
- must make use of existing smartdata models, e.g. dataModel.Agrifood
Bad unit code for lumminance
The unitcode for illuminance should be LUX
(LX is for linear yard per pound)
Bad unit code for VOC
Isn't the mcf88 sensor reporting VOC in ppb (parties per billion ?). See here: https://www.mcf88.it/wp-content/uploads/2020/07/MCF-LW12CO2.pdf
The unit code for ppb is 61
batteryVoltage, lorasnr missing in Graced contexts
These two terms are needed for the two Elsys device for Pilze. These terms are not defined (yet) in dataModel.Device. To be updated temporarily in graced context.
Broken context link
Hi,
after using the context easy-global-market.github.io/ngsild-api-data-models/apic/jsonld-contexts/apic-compound.jsonld, I have come across a minor bug. After the changes made here 58d0e8d the link https://easy-global-market.github.io/ngsild-api-data-models/sharedJsonldContexts/egm.jsonld is not anylonger working. Reason is the change of the folder name from sharedJsonldContexts to shared-jsonld-contexts.
Adding a Weather contexts file
Adding a Weather contexts file, containing (obviously) all possible contexts for the weather domain.
Define context for water treatment (needed for Graced SLF use case)
Missing terms (from fiware smartWater models):
- WaterTreatmentTank (Type)
- hasWaterBeingTreated (relationship)
- WaterBeingTreated (Type)
- hasWaterTreatmentTank (relationship)
- waterIn (property)
- waterOut (property)
- tankCapacity (property ->wasteWater)
- ecoli (property -> waterQuality)
- treatmentCycle (property)
Create a Graced context
- Create a Graced context for GRACED project use cases
- First version for Pilze, TCA, for which domain contexts have already been defined.
- Follow-up version would be for SLF (water treatment domain)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.