[X] I have searched both open and closed issues and found no similar reports.
Class and property
Class Agent
Issue description
Currently, there is inconsistency in how email addresses are handled within the SHACL schema:
For Agent (publisher/creator), the mbox property is used, and it does not require the mailto: prefix.
For contactPoint , the vcard:hasEmail property is used, where the mailto: prefix is mandatory.
This leads to inconsistency in data entry and validation across the schema
Proposed change
Update the SHACL schema for mbox to enforce the use of the mailto: prefix, aligning it with vcard:hasEmail.
Document this change clearly in the SHACL schema documentation, specifying that both mbox and vcard:hasEmail now require the mailto: prefix.
Version check
Duplicate check
Class and property
Class Agent
Issue description
Currently, there is inconsistency in how email addresses are handled within the SHACL schema:
For Agent (publisher/creator), the mbox property is used, and it does not require the mailto: prefix. For contactPoint , the vcard:hasEmail property is used, where the mailto: prefix is mandatory.
This leads to inconsistency in data entry and validation across the schema
Proposed change
Update the SHACL schema for mbox to enforce the use of the mailto: prefix, aligning it with vcard:hasEmail. Document this change clearly in the SHACL schema documentation, specifying that both mbox and vcard:hasEmail now require the mailto: prefix.
Priority
Nice to have