- From: Matthew Marum <vp-projects@opensocial.org>
- Date: Fri, 05 Dec 2014 09:50:11 -0500
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>, Ben Werdmüller <ben@withknown.com>, Dave Wilkinson <wilkie@xomb.org>
- CC: James M Snell <jasnell@gmail.com>, "public-socialweb@w3.org" <public-socialweb@w3.org>
Typically, I see very little custom markup in activity streams entries.
In a lot of applications, HTML gets stripped (or at least heavily
sanitized) out of entries that get pushed into an Activity Stream. This
is because allowing arbitrary markup can break the styling and UX
semantics of the page or even create security issues on the page. Not to
mention that if you support HTML in activities, you will be pressured to
add palettes to text inputs so your users can author HTML. Your UX team
will have a fit.
If you are looking to embed custom markup, then my preference would be to
consider the proposal for ActivityStreams Actions which addresses
Embedding use cases.
Matt Marum
On 12/5/14, 8:56 AM, "☮ elf Pavlik ☮" <perpetual-tripper@wwelves.org>
wrote:
>On 12/04/2014 01:21 PM, Ben Werdmüller wrote:
>>
>> We've been considering various options for this in Known. I strongly
>> disagree with using Markdown or similar syntax for human-readable
>> content, because that creates a burden to support a wholly different
>> notation in applications that are almost certainly web-based at some
>> level. I do think HTML with embedded microformats / microdata is the
>> most flexible option for this scenario. (It also doesn't tie
>> applications into Twitter-style @-syntax - there's no need to let them
>> dictate the convention.)
>I see no necessity to mandate details for the actual content, we can
>use different datatypes to provide multiple versions:
>
>{
> "@context": ...
> "@id": "/some-post",
> "@type": "BlogPosting",
> "text" [
> "i provide plain text, Markdown and HTML",
> { "@value": "i provide plain text,
>[Markdown](http://commonmark.org/) and
>[HTML](http://www.w3.org/TR/html5/)", "@type": "http://commonmark.org/" },
> { "@value": "i provide plain text, <a
>href='http://commonmark.org/'>Markdown</a> and <a
>href='http://www.w3.org/TR/html5/'>HTML</a>", "@type":
>"http://www.w3.org/TR/html5/"
> ]
>}
>
>I can see Markdown data type recommended by AKSW for site:content
>http://aksw.org/Projects/AKSWorg/Documentation.html
Received on Friday, 5 December 2014 14:50:51 UTC