Summary
Interfaces, contracts, methods, operations, entities, objects, and tables, oh my! The OSID Specification defines its own language solely in reference to itself. The vocabulary is defined and built upon without importing words from outside the OSIDs.
...
The term contract is often used in service designs to distinguish an interface from a message structure or DTO. The message structure and DTO are considered data while the contract defines the operations on that data. OSIDs define the agreement between service consumers and service providers. In the OSID world, most everything in the specification can be considered a contract, i.e. "The AgentList is a contract."
DTO (DAO, Bean, Domain Object)
A Data Transfer Object is used to transfer bags of data values. However, OSIDs are interfaces into OSID Providers. OSID Providers may be dynamic and DTOs are static.
...
About OSIDsAnchor About OSIDs About OSIDs
OOSID Specification FrameworkStructure & Definitions of OSIDs (S-OSID)Anchor OSID Specification Framework OSID Specification Framework
OSID SpecificationsAnchor OSID Specifications OSID Specifications - OSID Language Binding
OSID Java BindingAnchor OSID Java Binding OSID Java Binding - osid.OsidObjects