Design Alternatives
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Compiling here a list of alternatives one should consider / compare and contrast.
@michael-n-cooper did a really good job comparing some serialization formats here:
I'm starting to compile different architectures here:
https://github.com/w3c/personalization-semantics/issues/76
https://github.com/w3c/personalization-semantics/issues/73
As well as taxonomy alternatives here (if you go with @michael-n-cooper 's current architecture model):
https://github.com/w3c/personalization-semantics/issues/74
Feel free to add your alternatives here as you think them through.
Contributor guide
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
Start by reading the linked wiki comparison and issues #73, #74, and #76 to understand the serialization, architecture, and taxonomy alternatives already discussed. Add further alternatives and comparisons to this issue’s collection, with enough context for the project to evaluate them; completion is a useful, maintained list rather than a code change.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100