RDF vs JSON: Which format to use in POD apps
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 10
- Forks
- 7
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
RDF:
- Pros: Good for sharing data as terms / concepts are defined in some ontology.
- Cons: The app developper has to create their own ontology and make it public if they want to use custom concepts.
JSON:
- Pros: Native support in most widely used languages.
- Cons: Need a "schema" for terms / concepts used when sharing files to others.
For example, in the keypod app, it seems clear to use JSON and store something like below usually won't cause any problem.
{[{"key": "ACT", "value": "Canberra"}, {"key": "NSW", "value": "Sydney"}]}
In other words, some trade-off between being more precise (RDF) versus being more convenient and efficient (JSON).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Compare RDF and JSON for POD applications, using the keypod example and the stated precision-versus-convenience trade-off, then document a decided format and the conditions for using it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, json
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100