...
Concepts like classes and objects disappear. Others like parameter and primitive have a narrower connotation than what a Java developer would be accustomed. And the definition of "osid" gets fuzzier.
...
Terminology
...
Issues
Attributes 
Attributes & Data Fields
Service entities, such as OsidObjects, are expressed using interfaces. While a display name or description is generally treated as an attribute, this would only known to an OSID Provider. What is What is presented to an OSID Consumer is the means for accessing the value information at that point in time. Yes, OSID Providers can provide real time information through its methods and so OSIDs do not call these attributes or data fields.
...
.
An OSID Provider may likely employ data objects to satisfy the contract of an OsidObject. An OSID Consumer sees this through the window of the interface. The OSID Consumer may do whatever it likes with this information, including referring to them as simple data elements. However it can be an impediment when trying to understand the nature and applications of these interfaces whose implementation may require an underlying OSID Provider rather than a pull from a database table, for example.
Boundary
Contract
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 contractual agreement between service consumers and service providers. In the OSID world, everything in the specification is can be considered a contract. This term doesn't help qualify anything here but is often used to emphasize the nature of the interface.
DTO
DTO
A Data Transfer Object is used to transfer bags of data through system layers where, ideally, the DTO has some semantic meaning in an entity model. OSIDs do not have a concept of data, just method signatures . However, OSIDs are just piles of method signatures organized in interfaces.
Endpoint Endpoint
Entity Entity
Message Message Structure
Operations Operations
Relation Relation
Service Service
The term "service" doesn't have any formal definition in the OSID Specification. It's tossed around because this is a Service Design Methodology.
Standard Standard
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|