s1) (EISPP_directional_graph_2fresnel_gss_vrm) (combine 1 and 2 .wav into one file)

We can select the VRM button for Vendor Relationship Management. According to Wikipedia, it is a concept that was developed in a conversation between Mike Vizard, Gilmor Gang, and Doc Searls, a fellow at Harvard University. A menu comes up with items I hope to fit with Doc Searl's ProjectVRM definition.

These principles are:

1. Customers must enter relationships with vendors as independent actors.

2. Customers must be points of integration for their own data.

3. Customers must have control of the data they generate and gather. This means
they must be able to share data selectively and voluntarily.

4. Customers must be able to assert their own terms of engagement

5. Customers must be free to express their demands and intentions outside of any one company's control.

s2) (EISPP_directional_graph_2fresnel_gss_vrm2bookmark)

When I click the first button titled Bookmark Triples / Save Cache I get several additional buttons with different options including:
Save Query Result as RDF File, Save SPARQL Query Input, Save Query Output to LDP Container or Collection, and List Saved Items.

Clicking Save Query Result as RDF file saves the directed graphs as a collection of triples using the RDF Schema. This will save on a local filesystem or standard webserver with no additional complexity.

s4) (EISPP_directional_graph_2fresnel_gss_vrm3bookmark)

Clicking Save SPARQL Query Input saves the SPARQL syntax that was the input to the SPARQL endpoint in a text format

s5) (EISPP_directional_graph_2fresnel_gss_vrm4bookmark)

Clicking Save Query to LDP Container or Collection allows one to choose to save the query results as a resource in a linked 
data platform container or save the query results in a collection of RDF resources.

s6) (EISPP_directional_graph_2fresnel_gss_vrm5bookmark)

Clicking list saved items gives a list of all things saved previously.

s7) (EISPP_directional_graph_2fresnel_gss_vrm2federate)

Clicking on Federate Graphs brings up a menu that allows one to merge two or more RDF graphs. Here I have two RDF graphs in the file menu, Graph_A.rdf and Graph_B.rdf.

s8)  (EISPP_directional_graph_2fresnel_gss_vrm2federate2)

After clicking Load File(s), I now have the two graphs loaded.

s9) (EISPP_directional_graph_2fresnel_gss_vrm2federate2_2)

I can select the checkbox, "Apply owl:sameAs links for equivalent URIs" and click Federate to perform the action in the checkbox.

s10) (EISPP_directional_graph_2fresnel_gss_vrm2federate3)

We can check Apply Algorithm in Edit: NLP/* to bring up the edit triples panel, which gives us a list of algorithms. Shown here are Christian Bizer et al.'s ActiveGenLink and Kathrin Dentler et al.'s Reasoning by Swarm Intelligence.

s11)  (EISPP_directional_graph_2fresnel_gss_vrm2federate4)

I can click start to execute the highlighted algorithm, ActiveGenLink. Please note that in addition, that federate can apply to any loaded file. So I could for example compare the skills of two people, or how my own skills apply to a particular project by loading the respective graphs.

s12)  (EISPP_directional_graph_2fresnel_gss_vrm2loadbadge)

Clicking load badge brings up the loading badges window. These badges, based on Mozilla's Open Badges, are a record of a particular skill or accomplishment. On the right is a badge assertion in JSON-LD showing a record of a particular accomplishment.
This was inspired by Nate Otto's work with JSON-LD for the Badge Alliance. Clicking load file will load the file as a directed graph by default, and save file will save any changes made with edit triples.

s13)  (EISPP_directional_graph_2fresnel_gss_vrm2loadprofilegroups)

Clicking Load Profile / Groups brings up all Linked Data Platform Containers, personal profiles (such as foaf profiles), and Collections of resources.

s14) (EISPP_directional_graph_2fresnel_gss_vrm2loadprofilegroups2)

Clicking load file will load the file as a directed graph by default. The button add to PDS, or personal data store, will save the file to personal and local storage (or perhaps a trusted location). The NL Query button will search for additional files locally.

s15) (EISPP_directional_graph_2fresnel_gss_vrm2accesscontrol)

Clicking the Access Control button brings up the access control menu. On the left side is a menu that is modelled off of a paper by Hollenbach et al. titled, "Using RDF Metadata To Enable Access Control on the Social Semantic Web". 
R, W, and C come from the access control ontology. R is for acl:Read, W is for acl:Write, and C is for acl:Control. To the right of R is a column for Agent. This lists all agents, each which have permissions set by checkboxes in the R, W, and C columns, that have access to the highlighted file on the right. In this case, bshambaugh.org/foaf.rdf#me and example.org/person/foaf.rdf#me both have read (R) and write (W) access to the resource example.org/projects/Car_Project. In addition, bshambaugh.org/foaf.rdf#me also has  control access to example.org/projects/Car_Project, which means that it has the authority to change any access control permissions for any agent, through the checkboxes or otherwise, by changing the access control file for example.org/projects/Car_Project.

We can also add agents that have access to example.org/projects/Car_Project or any other item selected in the right pane by clicking the Add Agent button. We can also perform a natural language query to find additional agents to add with the NLQ for Agent button. Clicking Save changes saves any modifications to the checkboxes and thus access control file for the selected item.

On the right the NL Query button allows more items to be found, ideally locally and on the web. The Add to PDS button allows the saving of a copy of any item found through a NL Query or loaded through the Load File button. The listed items are all items in the PDS.

Additional information is also available in Andrei Vlad Sambra's Dissertation.

Access control can be also based on rules. See, for example, SWRL (Semantic Web Rule Language), and the more complex RIF (Rule Interchange Format). References describing both SWRL and RIF, their comparison, as well as their use for access control are provided at the end of the video.

s16) (EISPP_directional_graph_2fresnel_gss_vrm2transact)

Clicking the Transact button allows one to search for and load wallets, use them, and view information pertaining to them.
In this case we have a Bitmark wallet, based off of Bitcoin, with the URI http://example.bitmark.com/user/person#persona.
For this we can show related linked data for the wallet URI with the Show LD on the Right checkbox using the Web Payments 
Community Group Web Commerce 1.0 Specification.

With linked data we can show transaction history for a particular wallet. This is all Payswarm reciepts for this wallet. We can also click on an asset in the displayed directed graph, to show all the related asset info (like we saw with the Ripple purchase in another video). We can also purchase the asset, which is at a URI or click the negotiate/barter button to see if we can come up with a better price or trade something that we have. This negotiate/barter button should be integrated with something like cimba, so that the seller can be contacted.

In addition, the balance button shows the amount of funds in the wallet, the find wallet button allows other wallets to be found that are authorized by the agent using EISPP, and load wallet allows a wallet to be loaded.

I click the load wallet button to load the wallet.

s17) (EISPP_directional_graph_2fresnel_gss_vrm2transact2)

I select the :wheel_of_car node.

s18) (EISPP_directional_graph_2fresnel_gss_vrm2transact3)  (combine 18 and 19 into one file)

If I click Show Asset Info, I get a JSON-LD representation for the :wheel_of_car asset like Example 1 in section 4.1 in the Web Commerce 1.0 Specification.

s19) (EISPP_directional_graph_2fresnel_gss_vrm2powder)

When I press POWDER Preferences, I get a menu for POWDER or Protocol for Web Description Resources, which is a W3C recommendation.
The name of the resource, resources, or regular expression matching the resources, are highlighted at the top left of the window, the name of the powder document referring to this resource or resources is below on the left, and the contents of the powder document are on the right.

In this case, I have the example.org/projects/Car_Projects resource selected, which if you remember is really a linked data platform container. Then, what I am really refering to is a collection of resources, or a single resource in a container. I am not certain whether it is correct to call example.org/projects/Car_Projects a resource for POWDER, although it might be safe to treat it that way.

The NL Query button allows me to search for additional resources. The Load File button allows me to load additional resources, or a POWDER file, perhaps a template, that I wish to apply to a given resource, and Save As allows me to save changes to the file if I am authorized to do so. Perhaps, it might be useful to provide a functionality like a pull request from Git to the Save As button so that even if I am not authorized I can submit my changes to someone who is.

The apply to access control checkbox applies the POWDER document to a grouping of resources described by POWDER.

s20) (EISPP_directional_graph_2fresnel_gss_vrm2powder2)

I can load a profile template with the Load File button.

s21) (EISPP_directional_graph_2fresnel_gss_vrm2powder3)

I can make changes to the template with the Add Tag Button. The Add Tag Button provides a visual way 
to edit the profile document. When I click on it I get a menu which is oriented as a tree, like the xml structure of POWDER. 
I select the <issued> tag, which is embedded in the <attribution> and <powder> tags.

s22) (EISPP_directional_graph_2fresnel_gss_vrm2powder4)

I can type in the date and time in the <issued> tag with computer assisted completion.

References Include:

(1) Project VRM, Wiki, Modified, 13 October 2014, http://cyber.law.harvard.edu/projectvrm/Main_Page

(2) Manu Sporny, Ed., Web Commerce 1.0, Product Offers and Digital Receipts for the Web, 
Draft Community Group Specification 10 April 2014,
https://web-payments.org/specs/source/web-commerce/

(3) Nate Otto, We're adapting Open Badges to JSON-LD,
https://lists.w3.org/Archives/Public/public-linked-json/2014Oct/0021.html

(4) Open Badges, http://openbadges.org/

(5) Badge Alliance, http://www.badgealliance.org/

(6) James Hollenbach et al., Using RDF Metadata To Enable Access Control
on the Social Semantic Web, http://ceur-ws.org/Vol-514/paper3.pdf

(7) Basic Access Control Ontology, http://www.w3.org/ns/auth/acl 

(8) Andrei Vlad Sambra, Data Ownership and Interoperability for a Decentralized Social Web, Dissertation, TELECOM SUDPARIS et L’UNIVERSITE PIERRE ET MARIE CURIE, November 19, 2013, http://myprofile-project.org/thesis/manuscript_en.pdf

(9) Protocol for Web Description Resources (POWDER) Working Group, Phil Archer, 2009/11/24, http://www.w3.org/2007/powder/

(10) Phil Archer et al., W3C Protocol for Web Description Resources (POWDER): Web Description Resources (WDR) Vocabulary, W3C Working Draft 25 September 2007, http://www.w3.org/TR/powder-voc/

(11)    
SWRL: A Semantic Web Rule Language Combining OWL and RuleML, W3C Member Submission 21 May 2004, http://www.w3.org/Submission/SWRL/

(12)
Dizza Beimel, Mor Peleg, Using OWL and SWRL to represent and reason with situation-based access control policies, Data & Knowledge Engineering, 2011, Volume 70, Issue 6, June 2011, Pages 596–615, http://www.sciencedirect.com/science/article/pii/S0169023X11000334

(13)
RIF Overview (Second Edition), W3C Working Group Note 5 February 2013, http://www.w3.org/TR/rif-overview/

(14)
Policy-Based Transaction Authorization and Access Control, W3C RIF-WG Wiki, 
http://www.w3.org/2005/rules/wg/wiki/Policy-Based_Transaction_Authorization_and_Access_Control.html

(15)
RIF FAQ, W3C Wiki, February 4th, 2013,
http://www.w3.org/2005/rules/wiki/RIF_FAQ#How_does_RIF_differ_from_SWRL.3F