In the abstract, relationships are connections between endpoints. The two extremes of this are two people talking in a cafe and two api's transferring data over the Internet. If that's the case, then the relationships are defined by out of band tacit or explicit understandings between the entities with agency that are responsible for controlling the endpoints of the connection(s). That gives us the following items:

Content
Connection
Endpoint 
Entity responsible for endpoint
Agreement/understanding between entities that defines allowable content, acceptable connections, endpoint definitions and mutual rights and responsibilities between entities.

JW




Sincerely,
John Wunderlich
@PrivacyCDN

Call: +1 (647) 669-4749
eMail: john@wunderlich.ca

On 30 November 2016 at 11:00, John Moehrke <johnmoehrke@gmail.com> wrote:
I think your assertion that we only care about the humans is wrong. The 'things' that these humans authorize to act on their behalf are very important identities with important relationships. It might be true that identifying these 'things' is easier, less fuzzy.  But they must be in the picture.

John

John Moehrke
Principal Engineering Architect: Standards - Interoperability, Privacy, and Security
CyberPrivacy – Enabling authorized communications while respecting Privacy
M +1 920-564-2067
JohnMoehrke@gmail.com
https://www.linkedin.com/in/johnmoehrke
https://healthcaresecprivacy.blogspot.com
"Quis custodiet ipsos custodes?" ("Who watches the watchers?")

On Wed, Nov 30, 2016 at 9:18 AM, James Hazard <james.g.hazard@gmail.com> wrote:
Roughing in this idea - testing my own thoughts. 

I think "devices" are at a different layer than identities, persons, meat.  They aren't part of the graph of relationships.  

Again, roughing it, there seem to be three layers that are relevant:
  1. "reality" - meat, things, stuff (things we don't treat as things), places, time, etc.
  2. devices - the infrastructure on which the data model is maintained.  Devices depend on further infrastructure, such as communication protocols, wires and power supplies. This is, I suppose, the "(sync" part.
  3. a graph of relationships - the subject of Eve's (relationship (identity (person (meat)))) and John's diagrams.
 The "internet of things" is of course transactions among devices and not the "things" themselves.  The devices support bookkeeping and control of the things. 

From my work, the graph of relationships seems to need objects (nodes) for:
  1. (relationship - this can be a combination of legal prose and code. The archetype of an increment in a relationship is signing a new agreement, but each notice or payment is also an increment.  Becoming a citizen of a country or member of a club are broad examples of incrementing relationships with many persons via an interaction with a single person.
  2. (identity - this is something like a role, or account.  A bank account is a good archetype. "Identities" can be nested, an identity can relate to identities.  E.g. I make a contribution from my account to a pool to make an investment or gift, or into an escrow to make a purchase, which may not have legal "personality." 
  3. (person - some relationships among humans are treated by legal systems as "persons"  Persons also have nested relationships, e.g. an agent, employee, subsidiary.
  4. (meat - humans.   The part we care about.
  5. places - addresses etc.
  6. properties - cars, houses, patent rights, money ...
  7. facts - my focus is the legal docs and I haven't broken down facts very much.
From my perspective, the graph of relationships is a different layer than the devices.  A bank statement does not mention the computer on which the bank generated the document. 
 


On Tue, Nov 29, 2016 at 12:14 PM, John Wunderlich <john@wunderlich.ca> wrote:
Tossed it together in a hurry. I used 'device' is a proxy for 'non-natural person'. Might have been better to put API there as a proxy for the endpoint of multiple types of transactions.


Sincerely,
John Wunderlich
@PrivacyCDN

Call: +1 (647) 669-4749
eMail: john@wunderlich.ca

On 29 November 2016 at 13:55, James Hazard <james.g.hazard@gmail.com> wrote:
I don't think of a device as being in a kind of person.  It's something like the place that information is stored.  Not even an identity.  I can change phones.  At a really technical (coding) level, this gets more complicated, but in the "graph" of relationships, it doesn't matter which computer I use to write this message. 

On Tue, Nov 29, 2016 at 9:26 AM, John Wunderlich <john@wunderlich.ca> wrote:
John M. pointed out that the non-natural person was missing, so I redid it as attached:




Sincerely,
John Wunderlich
@PrivacyCDN

Call: +1 (647) 669-4749
eMail: john@wunderlich.ca

On 29 November 2016 at 12:07, James Hazard <james.g.hazard@gmail.com> wrote:
This image is great!  I'll find a place for it along with this one by Thomas - http://www.commonaccord.org/index.php?action=doc&file=S/About/Conference/Flyer/0.md#Diagram 

(Separately, I'm asked Norton Rose for a copy of their report on enforceability of smart contracts, and permission to circulate on the mailing list.)

On Tue, Nov 29, 2016 at 8:12 AM, John Wunderlich <john@wunderlich.ca> wrote:

​Inline images 1​

Sincerely,
John Wunderlich
@PrivacyCDN

Call: +1 (647) 669-4749
eMail: john@wunderlich.ca


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

_______________________________________________
DG-BSC mailing list
DG-BSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-bsc




--
@commonaccord



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.



--
@commonaccord



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.



--
@commonaccord

_______________________________________________
DG-BSC mailing list
DG-BSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-bsc





This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.