Re: [foaf-dev] FOAF 1.0 Planning Doc
Henry Story <[email protected]> Thu, 14 Jun 2012 10:16:30 +0200
| Newsgroups | gmane.comp.web.rdfweb |
|---|---|
| Message-ID | <[email protected]> |
On 13 Jun 2012, at 18:34, Dominique Guardiola wrote: > = > Le 13 juin 2012 =E0 15:44, Dan Brickley a =E9crit : > = >>>> Current notes are at >>>> https://docs.google.com/document/d/18sktpEWqREts-IjtrWU6eFXiR_VR3GVX9H= PdlazOC0o/edit >>> = >>> I had no feedback at all about this foaf:Contact idea >>> in a word : a Class that could act as a superclass for any "mean of con= tact" RDF class, supposing the need I exposed (linking metadata to a phone = number or an email address without using blank nodes) is shared by others. >> = > = >> It makes perfect sense and has been proposed in various guises over the = years. There is something similar in schema.org/ContactPoint ... > = > yes, I looked at schema's ContactPoint before, but it represents rather a= n Agent than a pure single "Contact information" thing. = > We have enough classes for Agent (foaf:Agent, foaf:Person, foaf:Organizat= ion, org:Organization...) > = > The name "Contact" is too ambiguous. > More explicit description of the concept : Communication Medium, Communic= ation Channel > If we look at it from the economic view (your phone number depends also o= n a service provider) view, it could just be named "foaf:Account". > = > In fact it's described in Semantic desktop ontology [1] as nco:ContactMed= ium, but with a restricted domain, nco:Role, not easily re-usable as FOAF i= s... > = > The goal would be to have a class working for a fax number AND for an onl= ine account, to be able to add metadata and privacy options along with the = number or account ID itself (rdf:value is used in vcard just for this goal) > = > <http://example.org/cid/34> a foaf:ContactMedium, v:Cell ; > rdf:value <tel:+3361513227>; # using a tel URI[2] > rdfs:comment "Do not call after 8PM"@en > rdfs:comment "Ne pas d=E9ranger apr=E8s 20h"@fr > dct:modified "2012-05-23"^^xsd:date I don't really see the need for this. Just write <tel:+3361513227> rdfs:comment "Do not call after 8PM"@en . > . > = > <http://www.example.org/pp2> a ppo:PrivacyPreference; > ppo:appliesToResource <http://example.org/cid/34>; > . > = > foaf:OnlineAccount permits this needed class wrapping, it only suffers fr= om a "geeky" bias : why should Online Accounts have classes while phone num= bers are "just" properties ? > = > = >> I think for this rev we should focus on convergence with other vocabs, e= ven if some duplication; which means looking at poco, vcard, hcard etc as w= ell. I like idea of representing contact points explicitly - once we figure= out the interplay with OnlineAccount etc. > = > = > = > Yes, nothing prevents us from already using some vcard classes with FOAF = properties : > = > <http://example.org/#me> foaf:mbox <http://example.org/cid/44> . > <http://example.org/cid/44> a v:Email; > rdf:value <mailto:[email protected]>; > . > = > Vcard "parameters types" approach [3] is to define several types to descr= ibe your resource, so regarding Kjetl's "foaf:personal_phone" property, thi= s can be done by combining two classes (v:Home and v:Tel in the vcard examp= le). = > Supporting this logic, classes such as foaf:Personal or foaf:Private coul= d be added to avoid creating countless personal_skypeID, personal_mbox , etc > = > Regarding all the protocol/brand specific properties ("skypeID", "openID"= , "jabberID"), one should be able to re-use another RDF Class, and just add= it to its "foaf:OnlineAccount" or "foaf:ContactMedium" resource to describ= e it more precisely. > = > = > Finally... > This superclass could also be the superclass of foaf:OnlineAccount, like = vcard:Tel is the superclass of vcard:Cell. > = > ---------------- > Other comments : > = > +1 on simplifying accountServiceHomepage + accountName =3D accountURL > Furthermore with decentralized/self-hosted microblog services like Status= Net, an accountURL (or just rdf:value ...) would be sufficient. > = > +1 for updating "member" to "hasMember" > = > = > [1] http://www.semanticdesktop.org/ontologies/2007/03/22/nco/#ContactMedi= um > [2] http://www.ietf.org/rfc/rfc3966.txt > [3] http://www.w3.org/TR/vcard-rdf/#Param > = > -- > Dominique Guardiola, QUINODE > =95 http://www.quinode.fr/ > =95 Tel : 04.27.86.84.37 > =95 Mob : 06.15.13.22.27 > = > = > = > = > = > _______________________________________________ > foaf-dev mailing list > foaf-dev-RyYwo1q5J+qsOXdr9/[email protected] > http://lists.foaf-project.org/mailman/listinfo/foaf-dev Social Web Architect http://bblfish.net/