Comments (3)
make sense to me yep, +1.
I'm wondering how we will export these then? Should we include the linked resources?
some comments about that, though:
- should we include the complete uri of the resource instead of directly its id?
- Do we want to have a many-to-many, one-to-many etc? or is a simple "foreign key" enough?
from daybed.
- JSON schema seems to address this need with URI
"storage": {
"type": "object",
"oneOf": [
{ "$ref": "#/definitions/diskDevice" },
{ "$ref": "#/definitions/diskUUID" },
]
},
- We would just need
anyOf
(1-N, N-N) andoneOf
(1-1, N-1).
But we first must clarify the distinction between linking data (records URIs) and linking model definitions (validating duplicated data against shared schemas).
In the end forseen applications are fun ! daybed could be a data pad, where some common models are shared (cities, vegetables, units, currencies...) and linked together (ontologies). Dataset loaded from dbpedia :)
from daybed.
Merged.
from daybed.
Related Issues (20)
- Plug loads with Daybed functional tests
- Resolve relation fields
- Add definition PUT, that would create/update models HOT 4
- Plugin idea : Daybed history HOT 2
- Hide the system.Everyone and system.Authenticated pyramid paradigm from daybed users.
- Record validation error appears several times in response
- Sharing single records HOT 7
- GET model definition should return the required parameter for all fields. HOT 6
- Multiple time the same validation errors HOT 2
- Missing location header in PUT /models/:id
- PUT/POST /models/:modelid/records with an unknown field type in the model definition (stored in the database) raise a 500 HOT 4
- Mention appback among competitors
- Should store deserialized value of records HOT 1
- Revoke / update tokens
- Redis backend: colander.null is not JSON serializable
- ElasticSearch bottleneck for batch record creation HOT 1
- [CouchDB] Having a - in the model name breaks the server
- Include the list of plugins in the hello page.
- Document the Daybed search endpoint
- Let's define a model field as primaryKey that will be used on the POST /records and validated with the recordId on PUT HOT 6
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 daybed.