VCARD properties in sold/object vs solid shapes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
@matthieubosquet @langsamu
I have noticed that the Solid shape for person uses vcard:email vcard:phone whereas @solid/object uses vcard:hasEmail and vcard:hasTelephone.
owl:equivalentProperty maps the properties in vcard, but do you want to choose one property in solid/object?
If standardise on vcard:hasEmail, then the Person shape will need to be changed in https://github.com/solid/shape-generation-artefacts/tree/main/shapes/Person and it will no longer be a shape 'as used in Solid OS'.
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
Review the property usage in solid/object alongside the Person shape in the linked shape-generation-artefacts repository. First determine whether vcard:email/vcard:phone or vcard:hasEmail/vcard:hasTelephone should be the canonical choice, then confirm that the selected convention is applied consistently and document the resulting decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100