Loose TypingLoose Typing
Concept Consequences - Loose Typing
Home > Books > Architect's Guide to NetKernel > Concepts > Concept Consequences > Loose Typing

Rate this page:
Really useful
Satisfactory
Not helpful
Confusing
Incorrect
Unsure
Extra comments:


Loose Typing

The URI interface of a resource describes its location, not its type.

Since all resources are identified by their URI address, the lack of a type designator means there is no tight dependence between the client and provider of a resource. Loose typing allows for generational independence between resource clients and providers - they may evolve independently within the context of the software development lifecycle. In addition, transreption provides impedance matching which means that resource clients do not have to be written to support all possible resource representation forms (data types).

© 2003-2007, 1060 Research Limited. 1060 registered trademark, NetKernel trademark of 1060 Research Limited.