Dear Desperado PEREZ,
OT ignores most of the tags in those contracts. Only a few tags are actually used.
You can basically add any tags that you want, and the contract will still work.
:-)
-Fellow Traveler
On 5/21/13 6:35 AM, Desperado PEREZ wrote:> Dear fellow-traveler
>
> In your GitHub you offer some sample-contracts at
> . You say with the purpose to get feedback of tags needed.
>
> I miss two tags:
>
> <*Definitions* name=" "> </*Definitions*>
>
> The definitions tags would describe the legal terms used in the
> <conditions> tag. It could eventually refer to published, agreed, legal
> definitions available on the web. If law changes the definition of
> "son", or "wife", the contract would automatically change. It would also
> be a tool for localisation. You could have a list of definitions valid
> for each country.
>
> <*Merchandise* included="*true/false*"pictureURL=" "></*Merchandise*>
>
> Many community currencies will follow Paul Grignon approach, that is,
> they are currencies to be redeemed against a concrete subset of goods or
> services. You may always include the descriptions of the goods in the
> <conditions> tag. However it would be much more handy to have a separate
> tag. A pictureURL attribute or the URL attribute would mean a link
> towards the shop where this merchandise is sold, directly from the currency.
>
> Here some examples of what I mean:
>
>
>
> The schema:
>
>
> Sample XML:
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "agile-banking" group.
> To unsubscribe from this group and stop receiving emails from it, send
>
>