- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Tue, 16 Apr 2013 17:08:00 +0200
- To: "'Boris Zbarsky'" <bzbarsky@mit.edu>
- Cc: "'public-rdf-comments'" <public-rdf-comments@w3.org>
Boris, FYI, we discussed this today on our telecon and opened an issue tracking it: http://www.w3.org/2011/rdf-wg/track/issues/124 We will soon get back to you with an official reply. Cheers, Markus -- Markus Lanthaler @markuslanthaler -----Original Message----- From: RDF Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] Sent: Tuesday, April 16, 2013 4:17 PM To: public-rdf-wg@w3.org Subject: RDF-ISSUE-124 (order-of-parameters): Order of parameters (options or callback last) - by Boris Zbarsky [JSON-LD Last Call 1] RDF-ISSUE-124 (order-of-parameters): Order of parameters (options or callback last) - by Boris Zbarsky [JSON-LD Last Call 1] http://www.w3.org/2011/rdf-wg/track/issues/124 Raised by: Markus Lanthaler On product: JSON-LD Last Call 1 Raised by Boris Zbarsky (http://lists.w3.org/Archives/Public/public-rdf-comments/2013Apr/0022.html): In "web" specs and libraries it seems to be the common style to put options objects as the last argument of a method. I am given to understand that "Node" style is to put the callback, if any, as the last argument, and that json-ld is following that style here. But it's not obvious why that's preferable to following "web" style for this particular specification. -Boris
Received on Tuesday, 16 April 2013 15:08:41 UTC