Comments (6)
@LeonanCarvalho and @jmcanterafonseca ,
It really makes sense a DataModel Schema. In some way, this remembers me the Web Services Description Language (WSDL) - https://www.w3.org/TR/wsdl - WSDL is used to describe an Web Service in a machine readable format.
We are open to contribute to this initiative!
I would suggest follow guidelines defined under IETF to the schema (https://tools.ietf.org/id/draft-zyp-json-schema-04.html). There are related initiatives regarding JSON Schema (http://json-schema.org/). There is also a tool that can help the JSON Schema creation (http://jsonschema.net/)
from data-models.
thanks for this input. I think it would be great to have a JSON, machine readable description of each of the data models. That would eventually allow us to automatically generate the markdown documentation file associated to each data model.
Any contribution would be very welcome. For instance, you can start by contributing the example you have described in this issue.
from data-models.
Thank your for the appreciation.
I'll send a pull request and I'm open to discus this model with you. I'll include Professor @flaviosilva on this conversation, may he could help us to improve and review this schemas.
On this pull I'll send the schemas for Device, DeviceModel, WaterQualityObserved, Vehicle, VehicleModel.
from data-models.
thanks Leonan, but please use one pull request per entity type, that would
make it easier the review process
best
2016-10-31 14:21 GMT+01:00 José Leonan S. Carvalho <[email protected]
:
Thank your for the appreciation.
I'll send a pull request and I'm open to discus this model with you. I'll
include Professor @flaviosilva https://github.com/flaviosilva on this
conversation, may he could help us to improve and review this schemas.
On this pull I'll send the schemas for Device, DeviceModel,
WaterQualityObserved, Vehicle, VehicleModel.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#76 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqZ_lJulfMaebdXK8vHtY1EX_h_onHXks5q5es9gaJpZM4KgE9O
.
from data-models.
That's the point! Thanks!
The guidelines defined under IETF should be enough to clarify some questions, like how to represent normative references of attributes.
I would like to read it deep this requirements to better understand and then adjust the models suggested on #81 , #82 , #83 , #84 and #85 pull requests.
On a second moment it will be great develop a tool to generate the structure and the docs based on this schema.
from data-models.
closed as dup of #151
from data-models.
Related Issues (20)
- In the Agri Data Models align Relationship names to be always verbs HOT 3
- [Agri] Ensure documentation of extended Attributes (non present in GSMA) is added at least to JSON Schema HOT 3
- [Agri] Swap AgriProduct and AgriProductType HOT 2
- [Agri] All the timestamp metadata in NGSIv2 examples is wrong HOT 5
- ensure Relationship "agriProduct" is renamed to "hasAgriProductType" HOT 4
- Reusing existing Linked Data vocabularies HOT 9
- Transmodel and Mobivoc vocabularies HOT 1
- [Roadmap] Generate Data Model documentation from JSON Schema
- [Roadmap] Generate FIWARE Data Models Schema in *JSON-LD* as it happens with schema.org HOT 1
- [Roadmap] Add NGSI-LD examples validation to CI HOT 2
- [Roadmap] Full documentation of Smart Agri Data Models HOT 1
- [Roadmap] Move more data models to the smart-data-models initiative or future initiatives HOT 1
- [Roadmap] Consider renaming https://uri.fiware.org/ns/data-models# to https://vocab.fiware.org/terms# and setting up all the infrastructure DNS resolution, etc. HOT 1
- Dead link HOT 2
- [WeatherObserved] windDirection attribute in Data model, schema doesn't match definition HOT 2
- Schema url is not precise
- [WeatherObserved] Creation of attribute uVIndex HOT 4
- [Vehicle] Update the enum list of vehicleType attribute HOT 1
- Location type used in WeatherObserved data model cause error or StructuredValues HOT 5
- Error Json-Ld parse context HOT 2
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.
from data-models.