This document occasionally uses terms that appear in capital letters. When the following terms appear capitalized, they are being used to indicate particular requirements of this specification.
APPLICATION
Any application (eg. App, portal, webserver) that uses the API for accessing UP (even only for an add-on functionality) is referred to as an APPLICATION.
CONSUMER
The ROLE of a USER when reading UNITs (via any APPLICATION). Only when protected data is requested the registration (at any WEBSERVER) is a precondition.
DEVELOPER
The ROLE of a Software Engineer/Company who develops any APPLICATION i.e. uses the API
PRODUCER
The ROLE of a USER when writing(create, update. delete) own UNITs (via any APPLICATION). As a precondition a PRODUCER has to register once at the WEBSERVER where his data shall be stored. If the PROVIDER is already the email-Provider of the PRODUCER another registration may be obsolete. Typically the owner of an email-address acts as a PRODUCER for his own account, but in principle it is possible to grant even write-access for other PRODUCERs.
PROSUMER
The ROLE of a USER that is acting as PRODUCER and CONSUMER. This word has been adopted by Web2.0.
PROVIDER
Internet-Provider that hosts a WEBSERVER under an owned domain. The WEBSERVER can be an in-house development or a standard product from another DEVELOPER.
TYPE
UP specifies different TYPEs for several domains e.g. contact/address, appointment/scheduling, weather, device/IOT, security. Each instance of a TYPE(~class) is called a UNIT(~object). Object-oriented concepts (inheritance, aggregation, visibility) are adopted. Nevertheless UP does not follow a strict object-oriented-design eg. there are only four fixed (webservice)methods(Get, Put, Post, Delete) for any UNIT.
UNIT
A UNIT is referenced via a UP-URI. The API specifies the data structure of each TYPE, the URI/URL address format for referencing a UNIT, the HTTP-methods to create, read, update and delete(crud) a UNIT and procedures to assure data privacy. The API specifies access methods and the format of transferred resources. Each instance of a specified resource is called a UNIT that is of a special TYPE. There are several TYPEs specified, each dedicated to a certain application domain.
UP
Abbreviation for UNITED-PAGES
USER
A USER acts in the role of a CONSUMER and/or SUPPLIER
WEBSERVER
The web-interface of a WEBSERVER has to be compliant with methods and TYPEs specified in the API. There is no demand to support every method and TYPE. Typically a WEBSERVER has a portal that allows configurations via Internet-Browser.