Software Reuse through Resource Registries

Software engineering has always had software reuse as one of its key tenets. In both service-oriented and resource-oriented architectures visibility is a prerequisite for fulfilling their respective promises, namely easier reuse of services and resources. Resource registries are a way to achieve such visibility. We argue that resource registries must separate technical, semantic and organizational aspects and leverage popular existing standards. This way they are able to adapt to domain specific requirements and a multitude of categorizations of and associations between resources. These arguments are backed up by examples primarily from the nascent pan-European eGovernment resource network.

[1]  Ann Thomas Manes.  Web Services: A Manager's Guide , 2003 .

[2]  M.W. Kuster,et al.  TextGrid as a Digital Ecosystem , 2007, 2007 Inaugural IEEE-IES Digital EcoSystems and Technologies Conference.

[3]  M.W. Kuster,et al.  Digital ecosystems of eHumanities resources and services , 2008, 2008 2nd IEEE International Conference on Digital Ecosystems and Technologies.

[4]  G. Lakoff,et al.  Women, Fire, and Dangerous Things: What Categories Reveal about the Mind , 1988 .

[5]  Tharam S. Dillon,et al.  Reference Architectural Styles for Service-Oriented Computing , 2007, NPC.

[6]  P. Kay,et al.  Basic Color Terms: Their Universality and Evolution , 1973 .

[7]  Jeremy J. Carroll,et al.  Resource description framework (rdf) concepts and abstract syntax , 2003 .