You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clearly the app is expecting the hasEmail property to have an email address as it object.
The method of using rdf:type to label the email as a work or home is terrible.
What to do? use vcard:hasEmail_work ? or use as in the contacts ontology
which is cleaner but more of a diversion from the spec http://www.w3.org/TR/vcard-rdf/
Note that spec allows both the bnode form AND the direct form.
So this app should probably accept both, and preserve them.
The text was updated successfully, but these errors were encountered:
I think the app should be more flexible in allowing both direct values as well as bnode references. Actually, having looked again at the vcard ontology it seems that hasEmail has rdfs:range :Email, so it can't be a direct property of a VCard.
My index file people.ttl (from https://github.com/linkeddata/swap/blob/master/pim/readMacAddressBook.py ) has
<Person/DEC7671A6C5E.ttl#this> vcard:inAddressBook <book.ttl#this>;
a vcard:Individual; vcard:fn "Yosi Scharf";
vcard:hasEmail [ a vcard:Work; vcard:value mailto:[email protected]].
The contacts app, when pointed at that file, lists contacts but gives his email as the internal ID of the bode, bnode not the email:
https://timbl.com/timbl/Automation/addressBook/Person/DEC7671A6C5E.ttl#this
Full name: Yosi Scharf
Email: https://timbl.com/timbl/Automation/addressBook/people.ttl*#_g_L14214C503909
Clearly the app is expecting the hasEmail property to have an email address as it object.
The method of using rdf:type to label the email as a work or home is terrible.
What to do? use vcard:hasEmail_work ? or use as in the contacts ontology
<#yosi> work [ email mailto:[email protected]] ]
which is cleaner but more of a diversion from the spec
http://www.w3.org/TR/vcard-rdf/
Note that spec allows both the bnode form AND the direct form.
So this app should probably accept both, and preserve them.
The text was updated successfully, but these errors were encountered: