Summary

Interfaces, contracts, methods, operations, entities, objects, and tables, oh my! The OSID Specification defines its own language solely in reference to itself. Developers will look at it from the OSID Language Binding perspective. Others will import concepts from what they have worked with in databases, web services, or MVC-based platforms. The result is a mash of terms that matters once in a while.

The OSID View

You can look at the OSID Specification schema for its specification terminology. It defines:

The Java View

The OSID Specification is transformed into the OSID Java Binding. The resulting merge creates the following OSID terminology in Java:

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.


The Web Services View

What's a 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.