Comments (4)
@bblfish maybe we could discuss it during next Social IG: Vocabulary TF meeting? I see many similarities between schema.org and microformats.org and pattern you propose here could help with aligning with both.
from solid-spec.
I think this is always going to be app dependent, whether that's on the server (a customized version of Solid lets say) or client side, and so no need to have specific expectations - "hardcoding". I would suggest that apps take some caution to do their own mapping (if not already part of the vocab) between some well-known/popular vocabs in order to handle the data as best as they can.
from solid-spec.
The question is wether we can come to some agreement ourselves when building apps to use similar vocabularies. I think at least having a table somewhere of vocabs used, and intentions to move would be good.
from solid-spec.
Some interesting thoughts: http://blog.sgo.to/2015/09/vocabulary-negotiation.html
Also materialized inference IMO could also work pretty well in many cases. If human will not read the data, even repeating different predicates with same value shouldn't consume to much of a bandwidth.
Last but not least I would happily see more attention on basic inference futures in http://rdfjs.org
from solid-spec.
Related Issues (20)
- When deleting a resource, should the corresponding ACL document also be deleted? HOT 7
- How to identify/represent federated containers of things? HOT 9
- Security/provenance issue with Extended Profile HOT 4
- How should we handle metadata of non-RDF sources (was Treatment of .meta files) HOT 22
- Is PUT a standard? HOT 5
- PUT should not switch resources between container and non-container HOT 19
- redirect from example.com/foo to example.com/foo/ where appropriate HOT 5
- Ambiguity around the Type Registry HOT 1
- Clients are allowed to traverse ACLs HOT 1
- What is the spec of an identity provider HOT 1
- Can Updates-Via is also sent on 404 and can listen for creation HOT 2
- Websocket protocol - think about allow back compatibility. HOT 6
- Identify Solid Server and Spec Version HOT 2
- Takedown requests / account deletion / privacy in a distributed and interactive web HOT 1
- Objection to Archiving the Solid Spec HOT 14
- Proposal: add issue templates to this repo HOT 20
- Update the README HOT 1
- Solid sends WS messages on private resources without authentication HOT 3
- Idea: Expanding the pubsub system to support webhooks
- api-websocket, nature of change and resource changed
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 solid-spec.