Re: Clarify objections to JSON [was Re: Getting the group back on track]

Interesting idea, if there is support for specifying the mediaType of 
Content, that might be a useful addition to the vocab. Though I don't 
think diaspora* would implement it, at least currently posts are "put in 
what you want and mix'n'match different formats". I'm quite sure that 
kind of freedom will be wanted to be kept. Having to choose a type of 
post and then be constrained to that sounds limiting.

But, looking at the Content object purely from what could be done with 
the AS2 vocab, it might make sense to allow specifying mediaType to Content.

Br,
Jason

On 25.10.2015 17:53, James M Snell wrote:
>
> Would it then make sense for the mediaType property to be defined for 
> Content objects?
>
> On Oct 25, 2015 8:49 AM, "Jason Robinson" <mail@jasonrobinson.me 
> <mailto:mail@jasonrobinson.me>> wrote:
>
>     On 25.10.2015 10:11, elf Pavlik wrote:
>
>         On 10/25/2015 12:09 AM, Jason Robinson wrote:
>
>             Hi James,
>
>             Yes, I meant the vocab. For object types, diaspora*
>             currently supports,
>             from the AS2 vocab, Image, Question, Place, Mention,
>             Profile. Events
>             support will come at some point. For actual status
>             messages, I'm
>             hesitant to say which object would be used. Note, Article
>             and Content
>             seem very similar - and in diaspora* everything is just a
>             status
>             message, whether short one liner or a 30K char markdown
>             formatted blog
>             post. I guess Note might still be the right one. Likely
>             incoming parsing
>             would squash all three as the same. I guess a comment
>             would just be
>             Content|Note|Article with an "inReplyTo" attribute.
>
>         You mentioned markdown, I remember that Amy also uses it. Does
>         diaspora
>         send textual content as plain text, makrdown, html or allows
>         specifying
>         syntax used in the content?
>
>
>     Everything is stored "as is", so markdown is stored as markdown,
>     html (the limited tags that are supported) as html. There is only
>     one type of status message to choose from and one can format it as
>     one likes. Various formats (markdown, html, special stuff like
>     mentions, tags) are then rendered to html in the UI.
>
>     -- 
>     -----
>     Br,
>     Jason Robinson
>     https://jasonrobinson.me
>
>
>

-- 
-----
Br,
Jason Robinson
https://jasonrobinson.me