Most extended context describes some property about the search result subject. It may be a triple directly off the subject, or it may require a more complex ldpath description to get to the value.
There is an additional use case where the extended context is about an entity in the extended context. For example, a search is performed which returns subjects for works. There is an agent for a work. The agent is a piece of extended context about the work. The agent itself can have an agent-role. This agent-role is related to the agent and not to the work itself.
How can we configure and normalize output to indicate the agent-role is connected to the agent?
Proposed Solution
Related subgraphs will be gathered in the context as context sets. A context set will include the following information.
an ldpath that defines the base path for the subgraph
properties to pull from the subgraph that are related to each other
Description:
Most extended context describes some property about the search result subject. It may be a triple directly off the subject, or it may require a more complex ldpath description to get to the value.
There is an additional use case where the extended context is about an entity in the extended context. For example, a search is performed which returns subjects for works. There is an
agent
for awork
. Theagent
is a piece of extended context about thework
. Theagent
itself can have anagent-role
. Thisagent-role
is related to theagent
and not to thework
itself.How can we configure and normalize output to indicate the
agent-role
is connected to theagent
?Proposed Solution
Related subgraphs will be gathered in the context as context sets. A context set will include the following information.
Example Context Set for Agent
bf:contribution / bf:agent
bf:contribution / bf:agent / rdfs:label
bf:contribution / bf:agent / bf:role / rdfs:label
NOTE: Above ldpaths start from the search result URI.
Snippet of Context Set Configuration in QA Authority:
Snippet of Normalized QA Output:
Full QA Output example