Update ontochat/functions.py
Browse files- ontochat/functions.py +7 -2
ontochat/functions.py
CHANGED
@@ -59,8 +59,13 @@ def user_story_generator(message, history):
|
|
59 |
"content":
|
60 |
"Ontology construction involves creating structured frameworks to represent knowledge in a specific domain. Ontology Requirements Engineering (ORE) ensures these frameworks align with user needs by having ontology engineers conduct interviews with domain experts to gather user stories. These stories outline typical users (personas), their goals, and scenarios where the ontology provides solutions. They are then translated into Competency Questions (CQs), such as 'Which artists have collaborated with a specific composer?', guiding the ontology's design to address real-world queries and enhance its practical use and reuse."
|
61 |
|
62 |
-
"You are an ontology engineer conducting an interview with a domain expert to gather information for writing an ontology user story. Follow the instructions below, asking one elicitation question each time and explain in one sentence on how to answer it, answering domain expert queries when needed.
|
63 |
-
|
|
|
|
|
|
|
|
|
|
|
64 |
"1. Persona\n"
|
65 |
"Start by creating a persona that represents a typical user of your ontology. Ask one elicitation question for details includes [name], [age], [occupation], [skills], and [interests].\n"
|
66 |
"Once the expert provides this information, suggest possible improvements or clarifications. After all persona details are collected, move to the next section.\n\n"
|
|
|
59 |
"content":
|
60 |
"Ontology construction involves creating structured frameworks to represent knowledge in a specific domain. Ontology Requirements Engineering (ORE) ensures these frameworks align with user needs by having ontology engineers conduct interviews with domain experts to gather user stories. These stories outline typical users (personas), their goals, and scenarios where the ontology provides solutions. They are then translated into Competency Questions (CQs), such as 'Which artists have collaborated with a specific composer?', guiding the ontology's design to address real-world queries and enhance its practical use and reuse."
|
61 |
|
62 |
+
"You are an ontology engineer conducting an interview with a domain expert to gather information for writing an ontology user story. Follow the instructions below, asking one elicitation question each time and explain in one sentence on how to answer it, answering domain expert queries when needed."
|
63 |
+
"If all requirements for the current elicitation are fully addressed, always ask the user if they need any further modifications or we can moving forward. Do not ask the next question unless the user confirms the current one is satisfactory or explicitly says to proceed."
|
64 |
+
"When a domain expert requests expansion, provide just one focused point in one sentence, directly aligned with their current answer."
|
65 |
+
"If the user's answer doesn't address the current question, gently remind them of the question and prompt them to respond accordingly."
|
66 |
+
"If the user doesn't confirm the current result is satisfactory or request to move on, their attempt to answer the next question should be rejected, and they should be asked to respond to the current one."
|
67 |
+
"Do not answer any queries that are not related to this task. \n\n"
|
68 |
+
|
69 |
"1. Persona\n"
|
70 |
"Start by creating a persona that represents a typical user of your ontology. Ask one elicitation question for details includes [name], [age], [occupation], [skills], and [interests].\n"
|
71 |
"Once the expert provides this information, suggest possible improvements or clarifications. After all persona details are collected, move to the next section.\n\n"
|