IETF, Web protocols, existing or coming, Internet culture
Scaling from 40 workstations to 40 million
Composition and Architecture
ISIG Working Group
Change in OMG process
reference implementations needed - borrow process from
others regarding reference implementations - The Open Group and IETF.
OMA Architecture
an optional uses specification to support plug
and play (Composition RFP?)
Composition of Basic Object Services
OODB Facility - the OODB specification should be a composition
of Basic Object Services
OODBMS-RDBMS Facility - add Collections and the Query
Service into the OODB
Active DBMS or KBMS Facility - add a Rules Service into
an OODBMS-RDBMS
Workflow Facility
Upper Middleware for Collaboration and Groupware - what
additional services are needed
deconstruct existing systems into Basic Object Components
and subsystems with IDL interfaces.
Web Servers/Peers - what is the OMG interface for "plug
ins"? Should we replace HTTP messaging with IDL? What is the migration
path?
Web Search Engines
Better Emailers
Multiplicity and Federation of Service and Facility
Federated Basic Object Services - federated namespaces,
nested transactions, distributed queries, traders talking to other traders,
and federation of caches and indices.
Federated Common Facilities - federated repositories,
federated DBMS systems, federated KBMS systems, federated workflow systems,
and federation of web search engines.
Theory needed
binding time
can we prove that if a component has a desirable property
like safety and that a composition rule preserves that property, then the
resulting system will preserve that property? That might allow secure systems
to federate with other secure systems into larger wholes.
can we protect against situations where an undesirable
property infects a whole federation?
can we specialize components or select differing policies
that govern their behavior and then still compose them
can we evolve systems and track the changes; can we rapidly
assemble applications from component pieces
can we solve problems ignoring distribution, persistence,
security, versioning, and other services and then later add them in via
X-unaware wrappers?
can we throttle systems so they become more or less distributed
dynamically?
Recommendations to OMG ORBOS
Object Model and Mapping Challenges
what is the right type model for the Internet/Web
Mappings
Converge OMG IDL and Java via bi-directional mapping
map all OMG specs to Java
Converge OMG IDL and MIME via MIME - IDL mapping
Converge OMG IDL and ODMG/SQL"3" (related to
persistence)
via an IDL to SQL ADT mapping
Relations to IDL mapping
learn from Microsoft OLE DB
HTML to IDL Mapping
typed links so web objects can be strongly typed
Naming issues
interoperability of OMG and web naming (e.g., OIDs and
URLs)
federation of namespaces when IDL names in one environment
clash with the same names in another.
ORB capabilities needed
call by value or the ability to move state around
asynchronous dispatch or deferred synchronous
isochronous delivery
programmable dispatch
separate specifications for IDL and CORBA distribution
service - ISO 14750
modular quality of service, determine bandwidth availability
migration management - for controlling and load balancing
media streams for varying media types, not just audio
and video but radar data, etc
compiling down to an IP + byte-coded methods level
mechanisms for handling firewalls
New Object Services needed
Caching Service
Replication Service
Generalized Indexing Service
Parsing Service
Translation Service - for converting one representation
to another. Is this the same as the Data Interchange Service?
Change Management Services
Event-Condition-Action Rules Service
Event Logging Service - today done differently by every
event management tool ORB
Licensing charging - monitoring usage
Recommendations to OMG Common
Facilities
Add to charter: Internet protocols, services, and facilities,
collaboration,
Internet Services/Facilities
Common Internet Protocols #1 including:FTP
(File Transfer Protocol), Telnet, Email (SMTP - Simple Mail Transport Protocol),
POP3 (Post Office Protocol 3), WAIS, Finger, Gopher, WAIS
Common Internet Protocols #2 and beyond including:
Network News, Email, MAPI, SMI, JMAPI, …, other IETF protocols
Internet Information-based Facilities
Search Tools
Web servers, CGI "replacements"
DBMS, OODB, RDBMS, ODBC
Information Access Facility (OTAM)
Metadata Repositories
KBMS
Workflow
Coordination Technology, Groupware
Long term - Extend OMA toward
Global Organized Information Space
Uniform information space for file systems and DBMS systems
Situations, Virtual Rooms, Information Spaces, Security
Domains.