The demo starts with the principal establishing operating identity, then adds preferences as behavioral context, then invokes the A2A client skill to discover and select capabilities from the chosen endpoint.
The final cut should follow the simple story: principal identity, agent relationship, preferences, A2A invocation, endpoint skill discovery, and selected skill. The MP4 includes embedded English captions; the page also supplies the VTT track for browser caption controls.
The interaction opens with whoami?. That establishes the operating identity for the session and makes the relationship explicit: Kingsley is the principal, and Codex is the agent acting in the session on his behalf.
The second opening interaction is What are my preferences?. Those preferences add session context that guides agent behavior: memory use, endpoint-aware workflows, Linked Data handling, and compact hyperlink-first presentation.
| # | Category | Steps | Primary HowTo Files |
|---|---|---|---|
| 1 | Identity, WebID & Delegation | 14 | agent-identity.ttl, verified-identity.ttl |
| 2 | Memory Management & Session Governance | 20 | session-governance.ttl, memory-protocol-gate.ttl |
| 3 | Artifact Output Routing | 11 | artifact-routing.ttl, model-identity-resolution.ttl |
| 4 | RDF Authoring & Entity Resolution | 21 | canonical-entity-iri-denotation.ttl, entity-link-placement.ttl |
| 5 | HTML Infographic & KG Explorer | 49 | infographic-authoring.ttl, kg-explorer-d3-patterns.ttl |
| 6 | Skill Chain & Workflows | 7 | skill-invocation.ttl, uriburner-oauth-authcode-flow.ttl |
| 7 | Resolvable IRI Payload Presentation | 1 | resolvable-iri-payload-presentation.ttl |
Session-relevant preference: when a payload includes a label and a resolvable IRI, present the label as the hyperlink and omit the redundant raw IRI column by default.
Once identity and preferences are established, the user invokes the A2A client skill. Its job is to discover endpoint capabilities and help choose the skill of interest.
The A2A skill discovers capabilities from endpoint Agent Cards. Endpoint choices remain user-controlled; the client does not hardcode a CNAME as the default.
| Endpoint | Agent Card | A2A URL | Auth | Streaming | Skills | Notes |
|---|---|---|---|---|---|---|
https://netid-qa.openlinksw.com | 404 | N/A | N/A | N/A | N/A | No card at /.well-known/agent.json |
https://netid-qa.openlinksw.com:8443 | OK | https://netid-qa.openlinksw.com:8443/chat/api/a2a | OAuth2 | true | 9 | Working NetID QA base |
https://linkeddata.uriburner.com | OK | https://linkeddata.uriburner.com/chat/api/a2a | OAuth2 | true | 13 | URIBurner endpoint |
https://demo.openlinksw.com | OK | https://demo.openlinksw.com/chat/api/a2a | OAuth2 | true | 37 | Demo endpoint |
The crux of the demo is discovery of skills and selection of a skill of interest on the chosen endpoint. Data Twingler on URIBurner is highlighted because that is the selected skill for the session.
| Endpoint | Skill ID | Skill Name |
|---|---|---|
NetID QA :8443 | system-data-twingler-config | OpenLink Data Twingler v2.0.4 |
| URIBurner | system-data-twingler-config | OpenLink Data Twingler v2.0.4 |
| URIBurner | system-virtuoso-support-assistant-config | Virtuoso Support Agent v1.1.71 |
| URIBurner | system-opml-rss-news-reader | OPML and RSS News Reader Assistant v1.0.40 |
| URIBurner | system-md~linked-data-agent-2 | linked-data-agent-2 |
| Demo | system-data-twingler-config | OpenLink Data Twingler v2.0.64 |
| Demo | system-virtuoso-support-agent-canonical | Virtuoso Support Agent v1.2.09 |
| Demo | system-fint-assistant-sparql | Fint Demo Agent (SPARQL) v1.0.1 |
The guide version should render the complete skills-by-endpoint table as an expandable section. The screencast can pause on the highlighted URIBurner Data Twingler row.
After skill selection, the workflow can continue into authorization and task execution. These details are useful QA evidence, but they support the story rather than define it.
Discovery OAuth Token capture Authenticated reach
The Data Twingler backend route returned a missing-parameter error after authentication. The screencast should present this as a QA finding, not as a failure of the discovery/auth workflow.
The DBpedia result remains useful as supporting evidence for the presentation preference: when a payload includes a title and a resolvable IRI, the title should be the hyperlink and the redundant IRI column should be omitted.
| Result | Status | Meaning |
|---|---|---|
| Principal identity established | Done | The session knows who the agent is working for. |
| Agent relationship established | Done | The agent role is explicit in the session context. |
| Preferences loaded | Done | Behavioral context guides the work. |
| A2A skill invoked | Done | The skill discovers capabilities from endpoint Agent Cards. |
| Skill of interest selected | Done | URIBurner Data Twingler v2.0.4 is the selected skill. |
| Task execution evidence | Supporting QA | OAuth worked; backend route exposed a parameter issue for follow-up. |