Misplaced Pages

#30969

46-740: Oracle Beehive includes a platform along with four main components: Oracle Beehive supports the following standards for greater interoperability and to allow the use of different communication and collaboration clients: In May 2009, Oracle released version 1.5 of Oracle Beehive with new capabilities including web-based team workspaces that include features such as file sharing, team wikis, team calendar, RSS support, and contextual search. Beehive 1.5 also includes added security and recording capabilities for audio and web conferencing and expanded integration with desktop productivity tools like Microsoft Outlook and Windows Explorer. In February 2010, Oracle released version 2.0 of Oracle Beehive. New capabilities include

92-501: A hyperlink . At the time, people referred to it as a "hypertext name" or "document name". Over the next three and a half years, as the World Wide Web's core technologies of HTML , HTTP , and web browsers developed, a need to distinguish a string that provided an address for a resource from a string that merely named a resource emerged. Although not yet formally defined, the term Uniform Resource Locator came to represent

138-465: A layered architecture to promote caching to reduce user-perceived latency , enforce security , and encapsulate legacy systems . REST has been employed throughout the software industry to create stateless , reliable web-based applications . An application that adheres to the REST architectural constraints may be informally described as RESTful , although this term is more commonly associated with

184-465: A namespace is an abstract domain to which a collection of element and attribute names can be assigned. The namespace name is a character string which must adhere to the generic URI syntax. However, the name is generally not considered to be a URI, because the URI specification bases the decision not only on lexical components, but also on their intended use. A namespace name does not necessarily imply any of

230-576: A minor update to RFC 2396, allowing URIs to accommodate IPv6 addresses. A number of shortcomings discovered in the two specifications led to a community effort, coordinated by RFC 2396 co-author Roy Fielding , that culminated in the publication of IETF RFC   3986 in January 2005. While obsoleting the prior standard, it did not render the details of existing URL schemes obsolete; RFC 1738 continues to govern such schemes except where otherwise superseded. IETF RFC   2616 for example, refines

276-516: A scheme component followed by a colon ( : ). A path segment that contains a colon character (e.g., foo:bar ) cannot be used as the first path segment of a relative reference if its path component does not begin with a slash ( / ), as it would be mistaken for a scheme component. Such a path segment must be preceded by a dot path segment (e.g., ./foo:bar ). Web document markup languages frequently use URI references to point to other resources, such as external documents or specific portions of

322-401: A server will respond with the representation of a resource (today, it will most often be an HTML , XML or JSON document) and that resource will contain hypermedia links that can be followed to make the state of the system change. Any such request will in turn receive the representation of a resource, and so on. An important consequence is that the only identifier that needs to be known is

368-441: A software development kit with REST APIs, coexistence support for Lotus Domino email systems, integration with Oracle Universal Content Management and Oracle Information Rights Management software, and team collaboration enhancements including a user directory, discussion forums, task assignments, tagging, and faceted search . REST This is an accepted version of this page REST ( Re presentational S tate T ransfer)

414-496: A specific edition of the William Shakespeare play Romeo and Juliet . The URN for that edition would be urn:isbn:0-486-27557-4 . However, it gives no information as to where to find a copy of that book. A Uniform Resource Locator (URL) is a URI that specifies the means of acting upon or obtaining the representation of a resource, i.e. specifying both its primary access mechanism and network location. For example,

460-405: A unique name, without a means of locating or retrieving the resource or information about it; these are Uniform Resource Names (URNs). The web technologies that use URIs are not limited to web browsers . URIs and URLs have a shared history. In 1990, Tim Berners-Lee's proposals for hypertext implicitly introduced the idea of a URL as a short string representing a resource that is the target of

506-463: Is undefined if it has an associated delimiter and the delimiter does not appear in the URI; the scheme and path components are always defined. A component is empty if it has no characters; the scheme component is always non-empty. The authority component consists of subcomponents : This is represented in a syntax diagram as: [REDACTED] The URI comprises: The scheme- or implementation-specific reserved character + may be used in

SECTION 10

#1732791173031

552-493: Is a software architectural style that was created to guide the design and development of the architecture for the World Wide Web . REST defines a set of constraints for how the architecture of a distributed, Internet -scale hypermedia system, such as the Web, should behave. The REST architectural style emphasises uniform interfaces , independent deployment of components , the scalability of interactions between them, and creating

598-662: Is a superset of the syntax of all URI schemes. It was first defined in RFC   2396 , published in August 1998, and finalized in RFC   3986 , published in January 2005. A URI is composed from an allowed set of ASCII characters consisting of reserved characters (gen-delims: : , / , ? , # , [ , ] , and @ ; sub-delims: ! , $ , & , ' , ( , ) , * , + , , , ; , and = ), unreserved characters ( uppercase and lowercase letters , decimal digits , - , . , _ , and ~ ), and

644-539: Is a technique by which a command is appended to a URL, usually at the end, after a "?" token . It is commonly used in WebDAV as a mechanism of adding functionality to HTTP . In a versioning system, for example, to add a "checkout" command to a URL, it is written as http://editing.com/resource/file.php?command=checkout . It has the advantage of both being easy for CGI parsers and also acts as an intermediary between HTTP and underlying resource, in this case. In XML ,

690-598: Is a unique sequence of characters that identifies an abstract or physical resource, such as resources on a webpage, mail address, phone number, books, real-world objects such as people and places, concepts. URIs are used to identify anything described using the Resource Description Framework (RDF), for example, concepts that are part of an ontology defined using the Web Ontology Language (OWL), and people who are described using

736-494: Is a useful but informal concept: a URL is a type of URI that identifies a resource via a representation of its primary access mechanism (e.g., its network "location"), rather than by some other attributes it may have. As such, a URL is simply a URI that happens to point to a resource over a network. However, in non-technical contexts and in software for the World Wide Web, the term "URL" remains widely used. Additionally,

782-548: Is analogous to a person's name, while a URL is analogous to their street address. In other words, a URN identifies an item and a URL provides a method for finding it. Technical publications, especially standards produced by the IETF and by the W3C, normally reflect a view outlined in a W3C Recommendation of 30 July 2001, which acknowledges the precedence of the term URI rather than endorsing any formal subdivision into URL and URN. URL

828-568: The http scheme. Simultaneously, the IETF published the content of RFC 3986 as the full standard STD 66, reflecting the establishment of the URI generic syntax as an official Internet protocol. In 2001, the World Wide Web Consortium's (W3C) Technical Architecture Group (TAG) published a guide to best practices and canonical URIs for publishing multiple versions of a given resource. For example, content might differ by language or by size to adjust for capacity or settings of

874-577: The RFC   1630 attempted to summarize the syntaxes of URL schemes in use at the time. It acknowledged -- but did not standardize —the existence of relative URLs and fragment identifiers. In December 1994, RFC   1738 formally defined relative and absolute URLs, refined the general URL syntax, defined how to resolve relative URLs to absolute form, and better enumerated the URL schemes then in use. The agreed definition and syntax of URNs had to wait until

920-546: The Friend of a Friend vocabulary would each have an individual URI. URIs which provide a means of locating and retrieving information resources on a network (either on the Internet or on another private network, such as a computer filesystem or an Intranet ) are Uniform Resource Locators ( URLs ). Therefore, URLs are a subset of URIs, ie. every URL is a URI (and not necessarily the other way around). Other URIs provide only

966-614: The Design of Network-based Software Architectures" at UC Irvine . To create the REST architectural style, Fielding identified the requirements that apply when creating a world-wide network-based application, such as the need for a low entry barrier to enable global adoption. He also surveyed many existing architectural styles for network-based applications, identifying which features are shared with other styles, such as caching and client–server features, and those which are unique to REST, such as

SECTION 20

#1732791173031

1012-638: The Semantic Web , which explained the use of content negotiation and the HTTP 303 response code for redirections in more detail. A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace. A URN may be used to talk about a resource without implying its location or how to access it. For example, in the International Standard Book Number (ISBN) system, ISBN 0-486-27557-4 identifies

1058-524: The URL http://example.org/wiki/Main_Page refers to a resource identified as /wiki/Main_Page , whose representation is obtainable via the Hypertext Transfer Protocol ( http: ) from a network host whose domain name is example.org . (In this case, HTTP usually implies it to be in the form of HTML and related code. In practice, that is not necessarily the case, as HTTP allows specifying arbitrary formats in its header.) A URN

1104-483: The Web's architecture, and there was pressure in the industry to agree on some standard for the Web interface protocols. For instance, several experimental extensions had been added to the communication protocol (HTTP) to support proxies , and more extensions were being proposed, but there was a need for a formal Web architecture with which to evaluate the impact of these changes. The W3C and IETF working groups together started work on creating formal descriptions of

1150-486: The Web's three primary standards: URI , HTTP , and HTML . Roy Fielding was involved in the creation of these standards (specifically HTTP 1.0 and 1.1, and URI), and during the next six years he created the REST architectural style, testing its constraints on the Web's protocol standards and using it as a means to define architectural improvements — and to identify architectural mismatches. Fielding defined REST in his 2000 PhD dissertation "Architectural Styles and

1196-430: The allowed set or is being used as a delimiter of, or within, the component. A percent-encoding of an identifying data octet is a sequence of three characters, consisting of the character % followed by the two hexadecimal digits representing that octet's numeric value. The URI generic syntax consists of five components organized hierarchically in order of decreasing significance from left to right: A component

1242-515: The browser's application state, making them unreliable; they also contain opaque data that can be a concern for privacy and security . The REST architectural style is designed for network-based applications, specifically client-server applications. But more than that, it is designed for Internet-scale usage, so the coupling between the user agent (client) and the origin server must be as loose as possible to facilitate large-scale adoption. The strong decoupling of client and server together with

1288-407: The character % . Syntax components and subcomponents are separated by delimiters from the reserved characters (only from generic reserved characters for components) and define identifying data represented as unreserved characters, reserved characters that do not act as delimiters in the component and subcomponent respectively, and percent-encodings when the corresponding character is outside

1334-400: The concept of resources. Fielding was trying to both categorise the existing architecture of the current implementation and identify which aspects should be considered central to the behavioural and performance requirements of the Web. By their nature, architectural styles are independent of any specific implementation, and while REST was created as part of the development of the Web standards,

1380-410: The design of HTTP -based APIs and what are widely considered best practices regarding the "verbs" ( HTTP methods ) a resource responds to while having little to do with REST as originally formulated—and is often even at odds with the concept. The term representational state transfer was introduced and defined in 2000 by computer scientist Roy Fielding in his doctoral dissertation. It means that

1426-448: The device used to access that content. In August 2002, IETF RFC   3305 pointed out that the term "URL" had, despite widespread public use, faded into near obsolescence, and serves only as a reminder that some URIs act as addresses by having schemes implying network accessibility, regardless of any such actual use. As URI-based standards such as Resource Description Framework make evident, resource identification need not suggest

Oracle Beehive - Misplaced Pages Continue

1472-526: The first time. During the debate over defining URLs and URNs, it became evident that the concepts embodied by the two terms were merely aspects of the fundamental, overarching, notion of resource identification . In June 1994, the IETF published Berners-Lee's first Request for Comments that acknowledged the existence of URLs and URNs. Most importantly, it defined a formal syntax for Universal Resource Identifiers (i.e. URL-like strings whose precise syntaxes and semantics depended on their schemes). In addition,

1518-496: The former, and the more contentious Uniform Resource Name came to represent the latter. In July 1992 Berners-Lee's report on the Internet Engineering Task Force (IETF) "UDI (Universal Document Identifiers) BOF " mentions URLs (as Uniform Resource Locators), URNs (originally, as Unique Resource Numbers), and the need to charter a new working group. In November 1992 the IETF "URI Working Group" met for

1564-426: The identifier of the first resource requested, and all other identifiers will be discovered. This means that those identifiers can change without the need to inform the client beforehand and that there can be only loose coupling between client and server. The Web began to enter everyday use in 1993–1994, when websites for general use started to become available. At the time, there was only a fragmented description of

1610-588: The implementation of the Web does not obey every constraint in the REST architectural style. Mismatches can occur due to ignorance or oversight, but the existence of the REST architectural style means that they can be identified before they become standardised. For example, Fielding identified the embedding of session information in URIs as a violation of the constraints of REST which can negatively affect shared caching and server scalability. HTTP cookies also violated REST constraints because they can become out of sync with

1656-475: The path, query and fragment, and the generic reserved character ? may be used in the query and fragment. The following figure displays example URIs and their component parts. DOIs ( digital object identifiers ) fit within the Handle System and fit within the URI system, as facilitated by appropriate syntax . A URI reference is either a URI or a relative reference when it does not begin with

1702-520: The publication of IETF RFC   2141 in May 1997. The publication of IETF RFC   2396 in August 1998 saw the URI syntax become a separate specification and most of the parts of RFCs 1630 and 1738 relating to URIs and URLs in general were revised and expanded by the IETF. The new RFC changed the meaning of U in URI from "Universal" to "Uniform." In December 1999, RFC   2732 provided

1748-549: The retrieval of resource representations over the Internet, nor need they imply network-based resources at all. The Semantic Web uses the HTTP URI scheme to identify both documents and concepts for practical uses, a distinction which has caused confusion as to how to distinguish the two. The TAG published an e-mail in 2005 with a solution of the problem, which became known as the httpRange-14 resolution . The W3C subsequently published an Interest Group Note titled Cool URIs for

1794-406: The same logical document: Resolving a URI reference against a base URI results in a target URI . This implies that the base URI exists and is an absolute URI (a URI with no fragment component). The base URI can be obtained, in order of precedence, from: Within a representation with a well defined base URI of a relative reference is resolved to its target URI as follows: URL munging

1840-430: The scheme http is generally used for interacting with web resources using HTTP, but the scheme file has no protocol. A URI has a scheme that refers to a specification for assigning identifiers within that scheme. As such, the URI syntax is a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme. The URI generic syntax

1886-425: The scheme, userinfo, host, path, query, and fragment, and the scheme- or implementation-specific reserved characters ! , $ , & , ' , ( , ) , * , , , ; , and = may be used in the userinfo, host, path, query, and fragment. Additionally, the generic reserved character : may be used in the userinfo, path, query and fragment, the generic reserved characters @ and / may be used in

Oracle Beehive - Misplaced Pages Continue

1932-468: The semantics of URI schemes; for example, a namespace name beginning with http: may have no connotation to the use of the HTTP . Originally, the namespace name could match the syntax of any non-empty URI reference, but the use of relative URI references was deprecated by the W3C. A separate W3C specification for namespaces in XML 1.1 permits Internationalized Resource Identifier (IRI) references to serve as

1978-701: The system architecture, it gains desirable non-functional properties , such as performance, scalability, simplicity, modifiability, visibility, portability, and reliability. The formal REST constraints are as follows: The uniform interface constraint is fundamental to the design of any RESTful system. It simplifies and decouples the architecture, which enables each part to evolve independently. The four constraints for this uniform interface are: Several models have been developed to help classify REST APIs according to their adherence to various principles of REST design, such as URI A Uniform Resource Identifier ( URI ), formerly Universal Resource Identifier ,

2024-484: The term "web address" (which has no formal definition) often occurs in non-technical publications as a synonym for a URI that uses the http or https schemes. Such assumptions can lead to confusion, for example, in the case of XML namespaces that have a visual similarity to resolvable URIs . Specifications produced by the WHATWG prefer URL over URI , and so newer HTML5 APIs use URL over URI . Standardize on

2070-422: The term URL. URI and IRI [Internationalized Resource Identifier] are just confusing. In practice a single algorithm is used for both so keeping them distinct is not helping anyone. URL also easily wins the search result popularity contest. While most URI schemes were originally designed to be used with a particular protocol , and often have the same name, they are semantically different from protocols. For example,

2116-575: The text-based transfer of information using a uniform addressing protocol provided the basis for meeting the requirements of the Web: extensibility , anarchic scalability and independent deployment of components, large-grain data transfer , and a low entry-barrier for content readers, content authors and developers. The constraints of the REST architectural style affect the following architectural properties: The REST architectural style defines six guiding constraints. When these constraints are applied to

#30969