- From: Andrew Bransford Brown <andrewbb@gmail.com>
- Date: Thu, 25 Oct 2018 14:52:33 +0700
- To: Michele Meloni <cleaversdev@gmail.com>
- Cc: Richard Wallis <richard.wallis@dataliberate.com>, public-fibo@w3.org
- Message-ID: <CAPS+YFKy_qh0N+5fZahCG3aeTEs=kWk5k0=UXbN=jaGNTXvnOw@mail.gmail.com>
These 6 fields describe a contract 'event'. Payment example:
{
EventID: 123,
TransactionID: someGUID,
CommerceID: BankOfAmerica,
EventType: "Deliver-Payment",
Description: "$500",
EventDateTime: 2018-10-25 14:50:01
}
Possible EventTypes are: Offer, Terms, CounterOffer, Agree, Deliver,
Complete, Notice.
On Thu, Oct 25, 2018 at 2:42 PM Michele Meloni <cleaversdev@gmail.com>
wrote:
> Sounds good to use a collection of moneyTransfer for serviceOutput. Money
> Transfer inherit from transferAction that has fromLocation to location. I
> think that I can replace (extending schema) these properties with
> fromAccount, toAccount. Use other properties it seems like a stretch.
> As @richard said schema.org is a bit immature to manage this flow.
>
> Il mer 24 ott 2018, 16:04 Richard Wallis <richard.wallis@dataliberate.com>
> ha scritto:
>
>> OK - quick question before going deeper.
>>
>> Where are you planning to share this data? The target audience for
>> Schema.org being websites openly sharing data for search engine crawlers
>> and others to harvest, and potentially within emails.
>>
>> As a bit of background, the FIBO-Schema.org work has not yet gone as far
>> as detailing contracts etc. At the moment it has paused at the point of
>> structures mostly useful for marketing what a bank or similar offers to
>> potential clients.
>>
>> Having said that, there is a way forward using the current structures
>> towards your needs, by defining a *LoanOrCredit* that has *MoneyTransfer*(s)
>> as its *serviceOutput*:
>>
>> {
>> "@context": "http://schema.org",
>> "@type": "LoanOrCredit",
>> "name": "Sample credit payments",
>> "serviceOutput": [
>> {
>> "@type": "MoneyTransfer",
>> "name": "Sample credit payments",
>> "amount": {
>> "@type": "MonetaryAmount",
>> "name": "Payment No 1",
>> "currency": "GBP",
>> "value": "100.00",
>> "validThrough": "2018-11-01"
>> },
>> "agent": {
>> "@type": "BankOrCreditUnion",
>> "name": "The Rilthy Rich Bank"
>> },
>> "object": {
>> "@type": "Person",
>> "name": "Mr Joe Soap"
>> },
>> "beneficiaryBank": {
>> "@type": "BankOrCreditUnion",
>> "name": "Joe's Personal Bank"
>> }
>> },
>> {
>> "@type": "MoneyTransfer",
>> "name": "Sample credit payments",
>> "amount": {
>> "@type": "MonetaryAmount",
>> "name": "Payment No 2",
>> "currency": "GBP",
>> "value": "100.00",
>> "validThrough": "2018-12-01"
>> },
>> "agent": {
>> "@type": "BankOrCreditUnion",
>> "name": "The Rilthy Rich Bank"
>> },
>> "object": {
>> "@type": "Person",
>> "name": "Mr Joe Soap"
>> },
>> "beneficiaryBank": {
>> "@type": "BankOrCreditUnion",
>> "name": "Joe's Personal Bank"
>> }
>> }
>> ]
>> }
>>
>>
>> ~Richard
>> Richard Wallis
>> Founder, Data Liberate
>> http://dataliberate.com
>> Linkedin: http://www.linkedin.com/in/richardwallis
>> Twitter: @rjw
>>
>>
>>
>> On Wed, 24 Oct 2018 at 14:35, Andrew Bransford Brown <andrewbb@gmail.com>
>> wrote:
>>
>>> That works to describe the payment, but is insufficient to describe the
>>> contract. Use this as your base data structure:
>>>
>>> CommerceID EventType Description EventDateTime
>>> MyBankIDNumber Offer-Loan $10,000 2018-10-24 09:00:00
>>> MyBankIDNumber Terms-Rate 10% 2018-10-24 09:00:00
>>> MyBankIDNumber Terms-Length 60 months 2018-10-24 09:00:00
>>> BorrowerIDNumber Agree 2018-10-25 09:00:00
>>> //this becomes a legal contract here.
>>> MyBankIDNumber Deliver-Loan $10,000 2018-11-01 09:00:00
>>> BorrowerIDNumber Deliver-Payment $500 2019-01-01 09:00:00
>>> BorrowerIDNumber Deliver-Payment $500 2019-02-01 09:00:00
>>> ....
>>> //after all payments are made, both parties would issue "Complete"
>>> events to end the contract.
>>> MyBankIDNumber Complete 2024-12-01 11:00:00
>>> BorrowerIDNumber Complete 2024-12-01 12:00:00
>>>
>>>
>>> The above 'transaction stack' has sufficient granularity for any legal
>>> contract.
>>>
>>>
>>> On Wed, Oct 24, 2018 at 8:30 PM Richard Wallis <
>>> richard.wallis@dataliberate.com> wrote:
>>>
>>>> OK - I got the wrong end of your question.
>>>>
>>>> The properties (of *MoneyTransfer*) you are looking for are *agent* (*The
>>>> direct performer or driver of the action*) and *object* (*The object
>>>> upon which the action is carried out*... ) which could be
>>>> considered as the *Thing* (*Person*) that benefitted from the action
>>>> (received the funds).
>>>>
>>>> Something like this:
>>>>
>>>> {
>>>> "@context": "http://schema.org",
>>>> "@type": "MoneyTransfer",
>>>> "name": "Sample credit payments",
>>>> "amount": [
>>>> {
>>>> "@type": "MonetaryAmount",
>>>> "name": "Payment No 1",
>>>> "currency": "GBP",
>>>> "value": "100.00",
>>>> "validThrough": "2018-11-01"
>>>> },
>>>> {
>>>> "@type": "MonetaryAmount",
>>>> "name": "Payment No 2",
>>>> "currency": "GBP",
>>>> "value": "100.00",
>>>> "validThrough": "2018-12-01"
>>>> }
>>>> ],
>>>> "agent": {
>>>> "@type": "BankOrCreditUnion",
>>>> "name": "The Rilthy Rich Bank"
>>>> },
>>>> "object": {
>>>> "@type": "Person",
>>>> "name": "Mr Joe Soap"
>>>> },
>>>> "beneficiaryBank": {
>>>> "@type": "BankOrCreditUnion",
>>>> "name": "Joe's Personal Bank"
>>>> }
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>> Richard Wallis
>>>> Founder, Data Liberate
>>>> http://dataliberate.com
>>>> Linkedin: http://www.linkedin.com/in/richardwallis
>>>> Twitter: @rjw
>>>>
>>>>
>>>>
>>>> On Wed, 24 Oct 2018 at 14:12, Michele Meloni <cleaversdev@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Richard,
>>>>> MonetaryAmount has no source or destination properties for the
>>>>> transaction and I think that are mandatory.
>>>>>
>>>>> Il giorno mer 24 ott 2018 alle ore 14:31 Richard Wallis <
>>>>> richard.wallis@dataliberate.com> ha scritto:
>>>>>
>>>>>> I would suggest the most appropriate route would be to use multiple
>>>>>> amounts thus:
>>>>>>
>>>>>>
>>>>>> {
>>>>>> "@context": "http://schema.org",
>>>>>> "@type": "LoanOrCredit",
>>>>>> "name": "Sample credit payments",
>>>>>> "amount": [
>>>>>> {
>>>>>> "@type": "MonetaryAmount",
>>>>>> "name": "Payment No 1",
>>>>>> "currency": "GBP",
>>>>>> "value": "100.00",
>>>>>> "validThrough": "2018-11-01"
>>>>>> },
>>>>>> {
>>>>>> "@type": "MonetaryAmount",
>>>>>> "name": "Payment No 2",
>>>>>> "currency": "GBP",
>>>>>> "value": "100.00",
>>>>>> "validThrough": "2018-12-01"
>>>>>> }
>>>>>> ]
>>>>>> }
>>>>>>
>>>>>>
>>>>>> Hope that helps,
>>>>>> ~Richard
>>>>>>
>>>>>> Richard Wallis
>>>>>> Founder, Data Liberate
>>>>>> http://dataliberate.com
>>>>>> Linkedin: http://www.linkedin.com/in/richardwallis
>>>>>> Twitter: @rjw
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, 19 Oct 2018 at 13:43, Michele Meloni <cleaversdev@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> what is the correct way to rapresents a transaction of money between
>>>>>>> two bank account?
>>>>>>> In ours case a loan can be made by multiple money transactions.
>>>>>>> How can make a connection between a series of money transfer and a
>>>>>>> loan.
>>>>>>>
>>>>>>> I'm triing to use MoneyTransfer for the transaction and LoanOrCredit
>>>>>>> for the loan.
>>>>>>>
>>>>>>> What do you think about that?
>>>>>>>
>>>>>>> Thanks in advance
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Michele Meloni*
>>>>>>>
>>>>>>> *Php Senior Software Developer*
>>>>>>>
>>>>>>> *http://www.linkedin.com/pub/michele-meloni/27/109/789
>>>>>>> <http://www.linkedin.com/pub/michele-meloni/27/109/789>*
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> *Michele Meloni*
>>>>>
>>>>> *Php Senior Software Developer*
>>>>>
>>>>> *http://www.linkedin.com/pub/michele-meloni/27/109/789
>>>>> <http://www.linkedin.com/pub/michele-meloni/27/109/789>*
>>>>>
>>>>
Received on Thursday, 25 October 2018 07:53:24 UTC