Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
hekate:hekate_process [2009/11/08 13:03] esimon Callbacks |
hekate:hekate_process [2019/06/27 15:49] (current) |
* types' names should be meaningful! | * types' names should be meaningful! |
| |
FIXME provide xslt for wiki export (WTF!) | BETA version of XSLT translator from HML 2 wiki table is provided in CVS - [[hekate:cases:howto#attribute_specification|HOWTO description]] |
| |
===== Prototyping ===== | ===== Prototyping ===== |
* Output: reports? | * Output: reports? |
* Remarks: | * Remarks: |
| |
===== Physical Design ===== | ===== Physical Design ===== |
The executable design generation. | The executable design generation. |
* Files: | * Files: |
* FIXME, at least basic input callbacks | * FIXME, at least basic input callbacks |
* Output: reports? trajectories | * To launch: <code>gox(<state>, [<tables>], <inference process>).</code> e.g. <code>gox(init, ['Table2', 'Table3'], ddi).</code> |
| * Output: Trajectories projections. Trajectory is the system inference path. After every inference process invocation new trajectory is generated. The trajectory can be identified by ID, to obtain ID of recently generated trajectory use //traj_id(ID)// predicate. The ID variable will be unified with an ID of the last trajectory. To save trajectory projection to a file use //io_export_trajectory(Filename, TrajID)// predicate. If you want to save most recent trajectory type this in Prolog console: <code> traj_id(ID),io_export_trajectory('file.txt', ID).</code> |
* Remarks: FIXME | * Remarks: FIXME |
* different inference modes? | * different inference modes? |
| |
| |
| ===== Integration ===== |
| This stage involves integrating the XTT logic with the environment with: |
| * callbacks |
| * knowledge encodings, translations |
| * UML representation |
| * Java serialization |
| * other? |
| |
| FIXME |
| |
| ==== Callbacks ==== |
| A minimal step here is to write callback for HeaRT in Prolog, XPCE, Java, Python. |
| |
| |
* LLK: Drools | * LLK: Drools |
| |
====== Integration ====== | ==== Encoding ==== |
The stages are integrated with: | |
* knowledge encodings | |
* transformations | |
* other? | |
| |
FIXME | |
This needs filling! | |
| |
===== Encoding ===== | |
Currently XML encodings to be used: | Currently XML encodings to be used: |
* ATTML | * ATTML |
The are now integrated into //HML// the [[Hekate Markup Language]]. | The are now integrated into //HML// the [[Hekate Markup Language]]. |
| |
===== Knowledge Markups ===== | ==== Knowledge Markups ==== |
Aspects: | Aspects: |
* ATTML <-> RDF | * ATTML <-> RDF |
* ontologies <-> ARDML | * ontologies <-> ARDML |
| |
===== Transformations ===== | |
FIXME | FIXME |
HatHoR | HatHoR |
| |
| ===== Summary ===== |
| In this stage designer experiences and observations should be captured. |
| |
| Some of the questions to be answered might be: |
| * was the case easy to model, if not, why |
| * was the HeKatE methodology helpfull, how, if not, why |
| * is it possible to suggest some improvements to the methodology |
| * was the HeKatE designed simplified compared to the original one |
| * what are the benefits of the HeKatE approach in this case |
| |
====== Tools ====== | ====== Tools ====== |
====== Case Template ====== | ====== Case Template ====== |
See [[:hekates:cases:hekate_case_skel:start|skeleton case]] | See [[:hekates:cases:hekate_case_skel:start|skeleton case]] |
| |