Use Case - Descriptive Name
Use Case Number |
Init4hm1.SD210 |
Brief Description |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->This Use case describes the functional usage of mapped LexRDF in a semantic web scenario |
Actor(s) for this particular use case |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->Application developers |
Pre-condition |
1. Their exists a mapping between LexGrid and RDF in the form of LexRDF2. The LexEVS API can query using SPARQL |
Post condition |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->Developer gets the entire information associated with the data element if it is available in LexRDF in triple constructs |
Steps to take |
User queries using LexEVS API |
Alternate Flow |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->A corresponding mapping does not exist between Lexgrid and RDF |
Priority |
Medium |
Associated Links |
|
Fit criterion/Acceptance Criterion |
Actor can look up data using a semantic search rather than a keyword search. |
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
1. |
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|