1. 1. Relating Human Markup Language to the Web Services Component Model 1.0 The Human Markup Language-HumanML Codifying Human Characteristics  Basic XML Schema, RDF Schema  Designed for Many Uses Foundation for Consistent Interpretation  Person-to-Person  Person-to-Computer Framework for Modular Development  Working with Standards Bodies and Organizations  Designed to Work with Web Services

2. 1.1 HumanML Personalization and Web Services Preferential Personalization  Targets Preferences  Maintains Preferences Across Platforms Habitual Personalization  Tracks Behavior  Allows Adaptation to Behavior 1. Relating Human Markup Language to the Web Services Component Model

4. 1.2 Integrating HumanML with Web Component Architectures WSXL, WSUI Designing Standard Web Components  Designing Standards for Distributed Apps  Using SOAP and HTTP Deck Logic Follows this Model  State Mechanism  XForms, WML Exemplify Deck Entities

5. 1. Relating Human Markup Language to the Web Services Component Model

6. 1.2 Integrating HumanML with Web Component Architectures HumanML in Standard Web Components  Avatars and Agents  Consistent Set of Programmatic Interfaces Web Components Using HumanML Poised to  Change How People Work with Computers  Change How People Relate to Content and Content Providers, Businesses and Services

7. 1. Relating Human Markup Language to the Web Services Component Model

8. 1.3 The Role of Human Markup in the Semantic Web HumanML Aimed to Work with Semantic Web XML-Oriented Specifications  HumanML Developing Taxonomies of Human Characteristics  HumanML Integrating XML Topic Maps, RDF HumanML Designed for Modular Extensibility  Ensures Adaptability  Allows Text and Text Collections to Yield Useful Data  Provides More Flexibility Retrieving Data

9. 1. Relating Human Markup Language to the Web Services Component Model

10. 1.4 Goals and Intentions HumanML is Long Term  HumanML Meant to Continue Evolving  HumanML Aimed to Improve Communication HumanML Integration with Web Services Component Architecture Needs  Support from WSCM  Transaction Authentication  Error Handling  Semantic and Syntactic Validation/Invalidation

11. 1. Relating Human Markup Language to the Web Services Component Model 1.5 Conclusion and Summary HumanML Provides Mechanism for Personalization  Content  Interface HumanML Provides Common Standard for Human-Centric Information  Dynamic State Information for Avatars, Agents  Dynamic Interfaces for Services HumanML a Good Fit with WSCM