Skip to content

VCARD properties in sold/object vs solid shapes #9

@tgra

Description

@tgra

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions