VCARD properties in sold/object vs solid shapes

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript

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.

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'.

Dominant language
TypeScript
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from solid/object

All issues in solid/object

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.