For the 'Riverside' project we have:
TOPIC_TYPE [ TYPE_ID, TYPE_NAME ]
('w3-9019278812766-uid-tm-type-194', 'Project-Member')
('w3-9019278376364-uid-tm-type-528', 'Project')
OCC_TYPE [ OCC_TYPE_ID, OCC_TYPE_NAME ]
('w3-9019278362488-uid-tm-occurrencetype-476', 'Entry Date')
('w3-9019277760105-uid-tm-occurrencetype-205', 'Location')
ROLE_TYPE [ ROLE_TYPE_ID, ASSOC_TYPE_ID, ROLE_TYPE_NAME ]
('w3-9019278613016-uid-tm-roletype-124',
'w3-9019282528789-uid-tm-associationtype-121', 'supports')
('w3-9019278366406-uid-tm-roletype-298',
'w3-9019282528789-uid-tm-associationtype-121', 'member')
ASSOC_TYPE [ ASSOC_TYPE_ID, ASSOC_TYPE_NAME ]
('w3-9019282528789-uid-tm-associationtype-121', 'member - supports')
TOPIC [ TOPIC_ID, TOPIC_NAME, TYPE_ID ]
('w3-9098507651161-uid-tm-topic-227', 'Scott',
'w3-9019278812766-uid-tm-type-194')
('w3-9019278607914-uid-tm-topic-258', 'Riverside',
'w3-9019278376364-uid-tm-type-528')
OCC [ OCC_ID, OCC_TYPE_ID, OCC_VALUE, TOPIC_ID ]
('w3-9098507651161-uid-tm-occurrence-304',
'w3-9019278362488-uid-tm-occurrencetype-476',
'9098507651161', 'w3-9098507651161-uid-tm-topic-227')
('w3-9019278930434-uid-tm-occurrence-102',
'w3-9019277760105-uid-tm-occurrencetype-205',
'IOWA', 'w3-9019278607914-uid-tm-topic-258')
ASSOC_ROLE [ ASSOC_ID, TOPIC_ID, ROLE_TYPE_ID ]
('w3-9098507651161-uid-tm-associationrole-405',
'w3-9098507651161-uid-tm-topic-227',
'w3-9019278366406-uid-tm-roletype-298')
('w3-9098507651161-uid-tm-associationrole-405',
'w3-9019278607914-uid-tm-topic-258',
'w3-9019278613016-uid-tm-roletype-124')
Using this schema the entity-relationship model can be extended over the network to other (mobile) devices by a contact lookup method.
TOPIC_TYPE [TYPE_ID, TYPE_NAME]
('w3-1340739761173-uid-tm-type-122', 'Topic Map Contact')
OCC_TYPE [ OCC_TYPE_ID, OCC_TYPE_NAME ]
('w3-1340739762171-uid-tm-occurrencetype-607', 'Access Point')
OCC [ OCC_ID, OCC_TYPE_ID, OCC_VALUE, TOPIC_ID ]
('w3-1340739714632-uid-tm-occurrence-172',
'w3-1340739762171-uid-tm-occurrencetype-607',
'http://project_host.com:1701', 'w3-1340739606989-uid-tm-topic-561')
TOPIC [ TOPIC_ID, TOPIC_NAME, TYPE_ID ]
('w3-1340739606989-uid-tm-topic-561', 'Project Map',
'w3-1340739761173-uid-tm-type-122')
Changing the association to
ASSOC_ROLE [ ASSOC_ID, TOPIC_ID, ROLE_TYPE_ID ]
('w3-9098507651161-uid-tm-associationrole-405',
'w3-9098507651161-uid-tm-topic-227',
'w3-9019278366406-uid-tm-roletype-298')
('w3-9098507651161-uid-tm-associationrole-405',
'/w3-1340739606989-uid-tm-topic-561/w3-9019278607914-uid-tm-topic-258',
'w3-9019278613016-uid-tm-roletype-124')
allows the implementation to follow the federated path expression
(Scott)[Project-Member]<supports>()[Project]
over the network to the 'http://project_host.com:1701' interface using the abbreviations
(Scott):w3-9098507651161-uid-tm-topic-227
[Project-Member]:w3-9019278812766-uid-tm-type-194
<supports>:w3-9019278613016-uid-tm-roletype-124
[Project]:w3-9019278376364-uid-tm-type-528
and delivers all projects Scott supports.
(1NF is violated for ease of use, but the referential integrity is given after synchronizing the contacts on http link change.)