|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Steve Vinoski, "It's Just a Mapping Problem," IEEE Internet Computing, vol. 7, no. 3, pp. 88-90, May/June, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MIC.2003.1200306, author = {Steve Vinoski}, title = {It's Just a Mapping Problem}, journal ={IEEE Internet Computing}, volume = {7}, number = {3}, issn = {1089-7801}, year = {2003}, pages = {88-90}, doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2003.1200306}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Internet Computing TI - It's Just a Mapping Problem IS - 3 SN - 1089-7801 SP88 EP90 EPD - 88-90 A1 - Steve Vinoski, PY - 2003 VL - 7 JA - IEEE Internet Computing ER - | |||
Adapting applications to each other requires mapping between the concepts, functions, or data native to each application, and identifying the abstractions under which each application can perform correctly and efficiently. Determining appropriate abstractions at any level is never easy, but doing so is critical to an application?s utility and success.
Citation:
Steve Vinoski, "It's Just a Mapping Problem," IEEE Internet Computing, vol. 7, no. 3, pp. 88-90, May-June 2003, doi:10.1109/MIC.2003.1200306
Usage of this product signifies your acceptance of the Terms of Use.

