Systems that use mobile, transient, or unreliable resources typically use descriptive names (also known as intentional or data-centric names) to specify those resources. Such names identify what data is needed rather than where that data is to be found. The Context Weaver middleware for collecting and composing data from pervasive networked data providers uses a descriptive naming system that is easily extended to handle the wide variety of data sources that exist today, as well as future data sources still unimagined. The system is based on a hierarchy of “provider kinds” and exploits emerging XML standards so that arbitrarily complex constraints can be specified.
By: Norman H. Cohen, Paul Castro, Archan Misra
Published in: RC23245 in 2004
LIMITED DISTRIBUTION NOTICE:
This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.
Questions about this service can be mailed to reports@us.ibm.com .