- From: James M Snell <jasnell@gmail.com>
- Date: Tue, 21 Apr 2015 07:59:26 -0700
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Cc: Robert Sanderson <azaroth42@gmail.com>, "public-socialweb@w3.org" <public-socialweb@w3.org>, Evan Prodromou <evan@e14n.com>
On Tue, Apr 21, 2015 at 12:00 AM, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote: [snip] > Thanks for this example James! > > >> Which is clearly not what was intended. It's a simple and somewhat >> contrived example but it illustrates the point that when a single >> Activity Streams document includes aggregated content, relying solely >> on JSON-LD embedding can lead to unexpected and often incorrect >> results. > What do you see 'incorrect' in this example? I understand that one might > expect displayName with just default language, still I don't understand > how do we get from 'possibly unexpected' to 'incorrect'? > It's incorrect in the sense that it's not what the user would likely expect or intend and it could have fairly serious impact when dealing with aggregated content from potentially untrusted sources. [snip] > >> Use of as:Link resolves these kinds of issues. Is it perfect? >> No. Is it useful. Yes. Can the examples in the spec be improved? >> Absolutely. But as I've said before, I'm absolutely -1 on removing >> as:Link. > > I don't see anywhere in 'Link' section of a spec, explanation that it > helps with addressing possibly little unexpected behavior of displayName > / displayNameMap in case of applying JSON-LD processing. I wonder if you > can provide some more examples of 'these kinds of issues'? Especially > ones which don't occur after processing with JSON-LD algorithms. > > Cheers! >
Received on Tuesday, 21 April 2015 15:00:14 UTC