I wonder if we should also include more complex scenarios that involve converters and emulators:

Indicative scenario:

Suppose one has also an old source file in Pascal programming language, say game.pas, and he has found a converter from Pascal to C++, say p2c++. Further suppose that he has just bought a smart phone running Android OS and he has found an emulator of WinOS over Android OS. It should follow that James can run game.pas on his mobile phone (by first converting it in C++, then compiling the outcome, and finally by running over the emulator the executable yielded by the compilation).

In other words, a sequence of conversions and emulations can be enough for vanishing an intelligibility gap, or for allowing performing a task. Since there is a plethora of emulation and migration approaches that concern various layers of a computer system (from hardware to software) or various source/target formats it is beneficial to use advanced knowledge management techniques for aiding the exploitation of all possibilities that the existing and emerging emulators/converters enable, and assist preservation planning.

NOTE: FORTH is currently doing research for supporting the aforementioned scenario (also related to WP25 ApanWp25).

-- YannisTzitzikas - 2011-08-29

Just to keep our terminology in sync with our common glossary of terms, is a converter the same as a transformer i.e. a process or tool that transforms digital objects from one form to another? This would suggest that your usage scenario is actually a composite function of both a transformation followed by an emulation in order to provide access to the digital object of interest (the game).

-- AshHunter - 2011-10-13

Yes. What I call converter is a transformer in your vocabulary (feel free to use your own terminology).

Indeed this what this scenario wants to stress: composite functions.


Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r4 - 2011-10-26 - DavidGiaretta
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback