You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a way to enable the social layer on top of the document layer on the web - unlocking the potential of decentralised annotations and activities for contextual interactions, either natively in the user agent or through user agent add-ons.
As an end user, Jadzia wants to use a user agent add-on (or user agent, user agent) to view contextual interactions related to an article she is reading, so that she can be informed of interactions - such as comments, reactions, annotations, and bookmarks - shared by her contacts, provided she has the necessary permissions, alongside her own.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
Actors can choose to identify themselves with the user agent or user agent add-on by using their personal online identities.
Actors maintain their contacts in their storage.
Storage and hosting are configured to manage interactions related to articles on the web.
Articles can reside anywhere on the web under any authority and be accessible from any web server.
Actors are authorized to access both public and private interactions.
Actors can configure their add-on to check additional sources for interactions, e.g., public annotation service for fact-checking.
Actors' interactions can be discovered through follow-your-nose exploration methods.
Trigger:
What (user or system) event or action initiates this use case?
To view her own interactions and those of her contacts on an article she is reading, Jadzia activates the user agent add-on and triggers the "Notifications" feature.
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
Primary actor: Jadzia can follow instructions to install a user agent add-on in her user agent. She understands that the add-on includes a feature to view interactions relevant to an article she is reading. She knows how to authenticate herself with the user agent add-on (or the user agent) and can locate and trigger the "Notifications" feature to view the interactions.
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
The user agent add-on must correctly interpret and render interactions from multiple sources while maintaining performance and avoiding latency, even for storage containing many interactions.
There may be different types of interactions, e.g., annotations and activities, with varying levels of descriptiveness.
Access control must ensure that private interactions are visible only to authorized actors, while public interactions remain accessible.
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
After her investigations into ancient Bajoran artifacts, Jadzia revisits an article written by Guinan (see #7 ) using her user agent. She recalls annotating a sentence in the article (motivated by "replying") but cannot quite remember what she noted. She wants to use her user agent add-on to help render content related to the article. She takes a deep breath, activates the user agent, and with another click, triggers the "Notifications" feature to view all interactions about the article that she has access to. Within a quantum second, Jadzia sees her own annotation in the sidebar, the one she was looking for. She also notices Deanna's review (see #22 ), Janeway's bookmark, Torres' like activity on the article, and a comment made by T'Pol, who performed fact-checking on the article and shared it via a public annotation service. The add-on provides additional affordances for some of the interactions, such as allowing her to delete her own annotation or reply to Deanna's review.
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
Jadzia chooses not to authenticate herself and uses the user agent add-on in guest (or anonymous) mode. In this case, only public interactions on the article are displayed.
Some of Jadzia's contacts have not granted her permission to view certain interactions. The add-on displays only the interactions she is authorized to access while notifying her of restricted items, e.g., "4 private interactions not visible".
The add-on renders previously cached interactions she had access to, marking them as potentially outdated because the article was updated after the interactions were created.
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
If Jadzia can't authenticate due to network issues or incorrect credentials, the system notifies her with an error message and suggests troubleshooting steps ( [UC] Error Messages #34 ) while still allowing access to public interactions.
If the system times out while retrieving interactions due to server issues with some of Jadzia's contacts, the add-on informs her of the delay and retries fetching data in the background, displaying partial results if available.
If the interaction data retrieved from storage contains errors or inconsistencies, the add-on flags these interactions with a warning while displaying unaffected data.
If the interactions are in a format (or data model) incompatible with the add-on, a fallback option renders the available human-readable text while alerting Jadzia that certain features may not function fully.
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
The user agent or add-on must allow the primary actor to verify their identities and securely access private interactions.
The add-on successfully renders both public and private interactions for authorized users within a reasonable timeframe, e.g., under 3 seconds.
The add-on continuously discovers new interactions in real time as they become available.
Private interactions are visible only to authorized users.
Interactions include a reference to their source, along with a complete description presented in a human-readable interface.
The system provides meaningful feedback or alternatives when errors occur, e.g., offline mode or incomplete data.
The add-on allows users to request access to interactions that the primary actor does not currently have permission to view.
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.
This is a way to enable the social layer on top of the document layer on the web - unlocking the potential of decentralised annotations and activities for contextual interactions, either natively in the user agent or through user agent add-ons.
As an end user,
Jadzia wants to use a user agent add-on (or user agent, user agent) to view contextual interactions related to an article she is reading,
so that she can be informed of interactions - such as comments, reactions, annotations, and bookmarks - shared by her contacts, provided she has the necessary permissions, alongside her own.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
Trigger:
What (user or system) event or action initiates this use case?
To view her own interactions and those of her contacts on an article she is reading, Jadzia activates the user agent add-on and triggers the "Notifications" feature.
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
After her investigations into ancient Bajoran artifacts, Jadzia revisits an article written by Guinan (see #7 ) using her user agent. She recalls annotating a sentence in the article (motivated by "replying") but cannot quite remember what she noted. She wants to use her user agent add-on to help render content related to the article. She takes a deep breath, activates the user agent, and with another click, triggers the "Notifications" feature to view all interactions about the article that she has access to. Within a quantum second, Jadzia sees her own annotation in the sidebar, the one she was looking for. She also notices Deanna's review (see #22 ), Janeway's bookmark, Torres' like activity on the article, and a comment made by T'Pol, who performed fact-checking on the article and shared it via a public annotation service. The add-on provides additional affordances for some of the interactions, such as allowing her to delete her own annotation or reply to Deanna's review.
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.
The text was updated successfully, but these errors were encountered: