In the general business sense of the word "user," implementing any spatial web services application involves the following kinds of people:
Administrators set up the web services infrastructure. Administrators might create database users, grant privileges and access rights to new and existing database users, and do other operations that affect multiple database users. For web feature services, administrators register feature tables, publish feature types, and unlock certain accounts.
For example, an administrator might set up the infrastructure to enable access to spatial features, such as roads and rivers.
Application developers create and manage the spatial data and metadata. They create spatial data tables, create spatial indexes, insert rows into the USER_SDO_GEOM_METADATA view, and use spatial functions and procedures to implement the application logic.
For example, an application developer might create tables of roads and rivers, and implement application logic that enables end users to find roads and rivers based on spatial query criteria.
End users access the services through their web browsers.
For example, an end user might ask for all roads that are within one mile of a specific river or that intersect (cross) that river.
From the perspective of an administrator, application developers and end users are all "users" because database users must be created to accommodate their needs. Application developers will connect to the database as users with sufficient privileges to create and manage spatial tables and to use Oracle Spatial and Graph functions and procedures. End users will access the database through a database user with limited access privileges, typically read-only access to data or limited write access.
The chapters about Spatial and Graph web services are written for administrators and application developers, not for end users.