663 |
Instead of focusing on unifying the internal data |
Instead of focusing on unifying the internal data |
664 |
model and views and avoiding different "applications", |
model and views and avoiding different "applications", |
665 |
OHM focuses on hyperlink interoperability between existing |
OHM focuses on hyperlink interoperability between existing |
666 |
applications (`Pearl 1989`). |
applications (`Pearl 1989`_). |
667 |
|
|
668 |
However, the OHM field |
However, the FOHM model (`Millard et al 2000`_) is an interesting |
669 |
|
step towards a similar approach: the FOHM model combines the different |
670 |
FOHM (Millard et al 2000) |
hypertext domains into a single conceptual structure. |
|
|
|
|
XXX Should we just not mention open hypermedia? |
|
|
|
|
|
- Focus: interoperability, existing apps. |
|
|
|
|
|
- Nelson (XXX) says "An application is a prison" -- |
|
|
an Open Hypermedia -enabled |
|
|
application is a prison where you can get visitors and |
|
|
send and receive mail - MUCH MUCH better but still... |
|
|
REF: Task-oriented MIT project tuukkah discussed |
|
|
|
|
|
- This is not meant to underestimate the work - OHM people have |
|
|
done a lot of interesting, difficult work |
|
|
in connecting monolithic, closed applications. |
|
|
|
|
|
FOHM: step towards hyperstructure: different domains |
|
|
unified into a single conceptual structure. |
|
671 |
|
|
672 |
|
|
673 |
5.5 Fluid Links and Transpointing Windows |
5.5 Fluid Links and Transpointing Windows |