- From: Harry Halpin <hhalpin@w3.org>
- Date: Thu, 23 Apr 2015 23:01:24 +0200
- To: James M Snell <jasnell@gmail.com>
- CC: Renato Iannella <ri@semanticidentity.com>, public-socialweb@w3.org
On 04/23/2015 06:45 PM, James M Snell wrote: > Yes that's exactly the plan. The jsonld context would do the heavy lifting > here. OK, then I can see no problem. As for elf's comments, note that vCard, unlike the rest, is a W3C Note and IETF standard that is exceedingly widely implemented, and maps to microformat and RDF vocabs - so if we have to chose one, my preference chose vCard. If the Vocab TF wants to work on those mappings, we'd all appreciate it. > On Apr 23, 2015 9:44 AM, "hhalpin" <hhalpin@w3.org> wrote: > >> On 2015-04-23 06:53, Renato Iannella wrote: >> >>> On 23 Apr 2015, at 1:41 am, James M Snell <jasnell@gmail.com> wrote: >>>> >>>> While this is helpful, the use of the namespace prefix is irritating. >>>> >>> >>> Why is it irritating? >>> >> >> My guess is some developers - particularly those who aren't using RDF >> somewhere mentally - don't like using namespaces, and often accidently >> leave them out. I know I've seen that in some usages of FOAF by non-RDF >> aware developers in the past. >> >> Would there be a way of sorting this out in the JSON-LD context, so that >> RDF-aware processors could properly namespace the vCard vocabulary usage >> while your ordinary JSON developer on the street would just process without >> namespaces (since they wouldn't be resolving them to begin with)? >> >> >>> Cheers... >>> Renato Iannella >>> Semantic Identity >>> http://semanticidentity.com >>> Mobile: +61 4 1313 2206 >>> >> >> -- >> >> Harry Halpin (W3C/MIT) harry@w3.org >> >
Received on Thursday, 23 April 2015 21:01:27 UTC