Implementation Advice: When Intelligent Agents Meet RDF

1. Implementation Advice:When Intelligent Agents Meet RDF 2004년 1학기 - 인간과 컴퓨터 상호작용 인공지능연구실, 부산대학교 최성자

2. CONTENTS 1. Introduction 2. Preserving Structure at the Cost of the Software 3. User Requirements for System Distribution 4. The FIPA Reference Architecture 5. Modeling Your Application: Using UML 6. Using a Search Robot to Find RDF Files

3. Introduction • Two ways to implement a system using RDF (In principle) This model is more likely in an agent system where there is not a central authority.

4. 2. Preserving Structure at the Cost of the Software • Reason of Preserving Structure • As long as you do not change the interface, your implementation should be interoperable with other implementations. ( black box approach)

5. 2. Preserving Structure at the Cost of the Software • This design principle ensures that you can meet a number of quality criteria for good software design. • The reusability of code. • Maintainability and adaptability. • Explanation.

6. 2. Preserving Structure at the Cost of the Software • To create the structure of facts - Formalize the descriptions; - Create a schema for the vocabulary we are going to use; • Apply the vocabulary to create the assertions • We can see which rules we need to apply to the facts to create the desired output. • To combine the facts and rules with interface agents and inference engines.

7. 3. User Requirements for System Distribution • Why must the systems be distributed? • The privacy of information • One of information sharing • In the architecture, you have three types of components: • Inference engines • Interface agents • handling agents

8. 3. User Requirements for System Distribution • Some general pieces of advice that apply to sound software design anywhere are as follows: • Make the code reusable. • Build in maintainability and adaptability from the start. • Explain and document what you do. • Let users extend the knowledge.

9. 4. FIPA Reference Architecture • FIPA - Foundation for Intelligent Physical Agents • Started in December 1996 • Currently 50+ member organizations from 11 countries • members include: IBM, Siemens, Hitachi, Lucent, CSELT, France Télécom, BT, Nortel Networks, Sun, Fujitsu, Imperial College, UMBC, NTT, Alcatel, Motorola, NHK, HP, Nokia, Sonera plus many others

10. 4. FIPA Reference Architecture • The FIPA reference architecture document describes an abstract architecture for creating intentional multi-agent systems. • The idea is • to use it to ensure interoperability between different agent implementations • to achieve that

11. 4. FIPA Reference Architecture • Two Goals • Interoperability • The FIPA architecture specifies a minimum set of functions, but does not prohibit those that extend it. • Reusability of agents • Not all features can be described in the abstract, and some must remain implementation-dependent.

12. 4. FIPA Reference Architecture • How can two agents locate and communicate? • The messages are encoded in an agent communication language (such as KQML) • A set of support services for the agents is required • Directory services • Message-transport services • The agent must advertise itself

13. 5. Modeling Your Application: Using UML • There are six levels of models in UML • Use case model • Class model • State model • Activity implementation model • Interaction model • Deployment model

14. 5. Modeling Your Application: Using UML • UML class models describe the static information sturcture of objects, the mps well into the static information stuctures of RDF • RDF Schema does not have any counterparts to the other UML modeling areas, but would have to be extended.

15. 5. Modeling Your Application: Using UML • The model has three subsystems: • The application model • The views • The controller

16. 6. Using a Search Robots to Find RDF Files • The W3C Webbot does not have an option to only look for certain file types • Yu would have to use those to include only files that contain configurations