| DwebAPI: | Schema.org has a pending WebAPI type to describe a Web API as a service |
|---|---|
| Dcreaork: | For schema.org, a web api can have multiple documentations, both machine readable and human readable. The distinction is made by the encoding format. A documentation is attached to a WebAPI instance with the documentation property. A SmartAPI documentation consists of various objects. A Hydra ApiDocumentation can be connected to any resource with apiDocumentation property. |
| DenFor: | Schema.org allows multiple encoding formats to be used with the documentation. This way an API publisher can create reference documentations for both machines (e.g. JSON-LD) and humans (e.g HTML, Markdown). The property takes a MIME type as value. |
| Dname: | Name or title of the API. Takes string values. |
| Ddesc: | Description of the API. Takes string values. Example: An API for managing Eventbrite events. |
| Dtos: | Schema.org can have string or URL values for this property, smartAPI only accepts URL |
| Dcontact: | Schema.org provides several properties for different kinds of roles of persons or organizations involved with the API. SmartAPI uses the x-role and x-id properties to identify contacts and their roles. |
| Dlicense: | License of the described API. SmartAPI supports name and url properties. For the case schema.org, license is an instance of CreativeWork whose subject is identified with an IRI and has at least a name. |
| Dversion: | For smart API this means the version of the documentation. For schema.org actions, documentation is the interface of the API, therefore it is the version of both. |
| DAction: | schema.org Action type allows the definition of high level operations and consists of HTTP method, target URL, request and response descriptions, as well as media types. SmartAPI does not annotate high-level operations semantically, only allows http methods |
| DurlTemplate: | The resource identifier. |
| DhttpMethod: | HTTP methods according to RFC 7231 |
| Dobject: | The properties for defining the request body |
| Dresult: | The properties for defining the response body |
| DcontentType: | Consumed media type by the API. Hydra allows only JSON-LD |
| DencodingType: | Response media type of the API. Hydra allows only JSON-LD |
Descriptions of the comparison between Schema.org Actions, Hydra and SmartAPI Concepts