Raised by Boris Zbarsky:
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.
Remove issue marker: we decided to use Futures
This addresses #240.
RESOLVED: Address ISSUE-125 by adopting a Futures-based approach for the JSON-LD API.
Closing this issue as it is being tracked in the RDF issue tracker: http://www.w3.org/2011/rdf-wg/track/issues/124