Re: [Taler] ToS rendering (was: Re: Taler Android UX)

[Christian Grothoff]

On 4/30/20 8:50 PM, Torsten Grote wrote:
> On 2020-04-05 06:45, belen barros pena wrote:
>>> TOS: I very much like how you show the TOS here with the 
>>> progressive-disclosure section-structure. This _will_, however,
>>> require the wallet to do quite a bit of extra work to _parse_ the
>>> RST/markup/TXT it currently receives to turn the TOS-Text it into
>>> this, but I do think it is a great idea.  But at least I would
>>> estimate that this will be more work to implement than most of the
>>> other changes combined ;-).
>>
>> that’s fair enough. I guess I was hoping that all TOSs would have a
>> similar structure, or at least a set of compulsory, common sections 
>> that would be marked up somehow by the exchanges and could be used
>> by the application to break down the content. I guess that’s not the
>> case.
> 
> Florian made a design document about ToS rendering:
> 
>     https://docs.taler.net/design-documents/003-tos-rendering.html
> 
> The goal is to have exchanges provide their ToS in markdown format, so
> we have a common format that we can render according to Belen's suggestion.
> 
> I have implemented this now in the Android Wallet. Here's a video of how
> it looks like:
> 
> https://devtube.dev-wiki.de/videos/watch/083194f6-8b70-4673-8b9f-3eb0de23f1a7

Looks great to me. Could you please add the markdown to the exchange.git
as contrib/tos/tos.md?

> Note that with the expandable sections in mind, the example ToS should
> probably use less sections.

I'll take that up with our lawyer.

-Christian

signature.asc
Description: OpenPGP digital signature