Over the last several years, my responsibilities within Enterprise Architecture may be categorized into three broad categories: Data Integration and API Design, Conceptual, Logical and Physical Data Modeling, and Enterprise-level consulting across product teams in the first two categories.In the first category of Integration and API Design my focus has been on defining and managing a Data Standards Practice that supports Application-to-Application and Business-to-Business integration initiatives comprised of developing a standard message library supporting different message exchange patterns on messaging and web service communication protocols. Key components managed as part of the practice included: an enterprise conceptual schema and data representation standards, based on the ISO 11179 metadata model and UN/CEFACT Core Components, a canonical interchange language (i.e. standard messages) based on XML and JSON Schema, membership and leadership roles in industry consortia standards (including OAGIS (Open Application Group Integration Specification) Platform and HR-Open), message library development process definition from data requirements and systems interaction analysis to message design and release, supporting development and operational standards. Recently, my attention has been focused on developing RESTful Web API Design standards.In the second category of Conceptual, Logical and Physical Data Modeling my focus has been on developing an ANSI-SPARC Conceptual Schema for the canonical interchange language (above), to logical model development for a strategic Enterprise-level Reference Data Model, and physical model development for strategic system and components in the Enterprise. Modeling techniques applied include UML class modeling and IDEF1X entity-relationship modeling.