Glossary of "Web Services Glossary"

Term entries in the "Web Services Glossary" glossary

W3C Glossaries

Showing results 1 - 20 of 116


From Web Services Glossary (2004-02-11)

To interact with a system entity in order to manipulate, use, gain knowledge of, and/or obtain a representation of some or all of a system entity's resources. [RFC 2828]

access control

From Web Services Glossary (2004-02-11)

Protection of resources against unauthorized access; a process by which use of resources is regulated according to a security policy and is permitted by only authorized system entities according to that policy. [RFC 2828]

access control information

From Web Services Glossary (2004-02-11)

  1. Any information used for access control purposes, including contextual information. [X.812]

  2. Contextual information might include source IP address, encryption strength, the type of operation being requested, time of day, etc. Portions of access control information may be specific to the request itself, some may be associated with the connection via which the request is transmitted, and others (for example, time of day) may be "environmental". [RFC 2829]

access rights

From Web Services Glossary (2004-02-11)

A description of the type of authorized interactions a subject can have with a resource. Examples include read, write, execute, add, modify, and delete. [WSIA Glossary]


From Web Services Glossary (2004-02-11)

  1. A person or organization that may be the owner of agents that either seek to use Web services or provide Web services.

  2. A physical or conceptual entity that can perform actions. Examples: people; companies; machines; running software. An actor can take on (or implement) one or more roles. An actor at one level of abstraction may be viewed as a role at a lower level of abstraction.


From Web Services Glossary (2004-02-11)

An agent is a program acting on behalf of a person or organization. (This definition is a specialization of the definition in [Web Arch]. It corresponds to the notion of software agent in [Web Arch].)


From Web Services Glossary (2004-02-11)

The quality or state of being anonymous, which is the condition of having a name or identity that is unknown or concealed. [RFC 2828]


From Web Services Glossary (2004-02-11)

  1. The software architecture of a program or computing system is the structure or structures of the system. This structure includes software components, the externally visible properties of those components, the relationships among them and the constraints on their use. (based on the definition of architecture in [Soft Arch Pract])

  2. A software architecture is an abstraction of the run-time elements of a software system during some phase of its operation. A system may be composed of many levels of abstraction and many phases of operation, each with its own software architecture. [Fielding]


From Web Services Glossary (2004-02-11)

A piece of digital information. An artifact may be any size, and may be composed of other artifacts. Examples of artifacts: a message; a URI; an XML document; a PNG image; a bit stream.


From Web Services Glossary (2004-02-11)

An interaction is said to be asynchronous when the associated messages are chronologically and procedurally decoupled. For example, in a request-response interaction, the client agent can process the response at some indeterminate point in the future when its existence is discovered. Mechanisms to do this include polling, notification by receipt of another message, etc.


From Web Services Glossary (2004-02-11)

A distinct characteristic of an object. An object's attributes are said to describe the object. Objects' attributes are often specified in terms of their physical traits, such as size, shape, weight, and color, etc., for real-world objects. Objects in cyberspace might have attributes describing size, type of encoding, network address, etc. [WSIA Glossary]

audit guard

From Web Services Glossary (2004-02-11)

An audit guard is a mechanism used on behalf of an owner that monitors actions and agents to verify the satisfaction of obligations.


From Web Services Glossary (2004-02-11)

Authentication is the process of verifying that a potential partner in a conversation is capable of representing a person or organization.


From Web Services Glossary (2004-02-11)

The process of determining, by evaluating applicable access control information, whether a subject is allowed to have the specified types of access to a particular resource. Usually, authorization is in the context of authentication. Once a subject is authenticated, it may be authorized to perform different types of access. [STG]


From Web Services Glossary (2004-02-11)

  1. An association between an interface, a concrete protocol and a data format. A binding specifies the protocol and data format to be used in transmitting messages defined by the associated interface. [WSD Reqs]

  2. The mapping of an interface and its associated operations to a particular concrete message format and transmission protocol.

  3. See also SOAP binding.


From Web Services Glossary (2004-02-11)

A capability is a named piece of functionality (or feature) that is declared as supported or requested by an agent.


From Web Services Glossary (2004-02-11)

  1. A choreography defines the sequence and conditions under which multiple cooperating independent agents exchange messages in order to perform a task to achieve a goal state.

  2. Web Services Choreography concerns the interactions of services with their users. Any user of a Web service, automated or otherwise, is a client of that service. These users may, in turn, be other Web Services, applications or human beings. Transactions among Web Services and their clients must clearly be well defined at the time of their execution, and may consist of multiple separate interactions whose composition constitutes a complete transaction. This composition, its message protocols, interfaces, sequencing, and associated logic, is considered to be a choreography. [WSC Reqs]


From Web Services Glossary (2004-02-11)

  1. A component is a software object, meant to interact with other components, encapsulating certain functionality or a set of functionalities. A component has a clearly defined interface and conforms to a prescribed behavior common to all components within an architecture. [CCA T&D]

  2. A component is an abstract unit of software instructions and internal state that provides a transformation of data via its interface. [Fielding]

  3. A component is a unit of architecture with defined boundaries.


From Web Services Glossary (2004-02-11)

Assuring information will be kept secret, with access limited to appropriate persons. [NSA Glossary]


From Web Services Glossary (2004-02-11)

A collection of properties which may be changed. A property may influence the behavior of an entity.

The Glossary System has been built by Pierre Candela during an internship in W3C; it's now maintained by Dominique Hazael-Massieux

Copyright © 2000-2003W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.