TL;DR: A group identifier represents an association between each of a number of different abbreviated namespace identifiers with a corresponding hierarchical namespace as mentioned in this paper, and it is accessed by a computing system that determines that the group identifier is associated with the hierarchically structured document.
Abstract: A group identifier represents an association between each of a number of different abbreviated namespace identifiers with a corresponding hierarchical namespace (e.g., an XML namespace). A hierarchically-structured document (e.g., an XML document) is accessed by a computing system that determines that the group identifier is associated with the hierarchically-structured document. Hence, when using the abbreviated namespace identifiers in the hierarchically-structured document, the computing system knows that the corresponding namespace is associated with the designated portions of the hierarchically-structured document. Also, a schema description language document (e.g., an XSD document) may specify multiple target namespaces for a single element. Accordingly, groupings of elements may be included in different namespaces to creating overlapping or even nested namespaces.
TL;DR: In this paper, an application server, configured for dynamically generating web page (e.g., HTML) document based on execution of XML documents, dynamically generates an HTML page having selected form elements based on a stored XML document that defines available HTML form elements and respective attributes, and based on user attributes retrieved by the application server from an open network database server (such as LDAP).
Abstract: An application server, configured for dynamically generating a web page (e.g., HTML) document based on execution of XML documents, dynamically generates an HTML page having selected form elements based on a stored XML document that defines available HTML form elements and respective attributes, and based on user attributes retrieved by the application server from an open network database server (such as LDAP). The application server, in response to a request from a user, accesses an XML document configured for specifying attributes associated with the request; the XML document may specify as form elements menus that are available for generation based on qualified user attributes, or may specify HTML fields that can be generated for display on the HTML page based on the qualified user attributes. The application server also retrieves the user attributes, and dynamically generates the HTML page based on identifying the user attributes matching the qualified user attributes of the accessed XML document. Hence, HTML pages having form elements can be dynamically generated, providing personalized HTML pages without the necessity of modifying CGI scripts or stored HTML pages.
TL;DR: The W3C Uniform Resource Identifier Interest Group (URI Interest Group) as mentioned in this paper addresses and attempts to clarify issues pertaining to URIs, including how URI space is partitioned and the relationship between URI, URLs, and URNs, describes how URI schemes and URN namespaces are registered, and presents recommendations for continued work on this subject.
Abstract: This document, a product of the W3C Uniform Resource Identifier (URI) Interest Group, addresses and attempts to clarify issues pertaining to URIs. This document addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs, describes how URI schemes and URN namespaces ids are registered, and presents recommendations for continued work on this subject.
TL;DR: In this article, a method and system for managing application state information, represented by a substring of a Uniform Resource Identifier (URI), which identifies a resource in a network is presented.
Abstract: An embodiment provides a method and system for managing application state information, which is represented by a substring of a Uniform Resource Identifier (URI), which identifies a resource in a network. The substring comprises a plurality of nested data arrays. A URI parser and a URI generator convert the application state information between an object representation and a URI string representation. Preferably, the URI is a Uniform Resource Locator (URL), the application state information is provided by a web application, and the URI string representation uses a JavaScript Object Notation (JSON).
TL;DR: By making namespaces explicit, Piccola is easily able to express various abstractions that would normally require more heavyweight techniques, such as language extensions or meta-programming.
Abstract: A namespace is a mapping from labels to values. Most programming languages support different forms of namespaces, such as records, dictionaries, objects, environments, packages and even keyword-based parameters. Typically only a few of these notions are first-class, leading to arbitrary restrictions and lim- ited abstraction power in the host language. Piccola is a small language that uni- fies various notions of namespaces as first-class forms, or extensible, immutable records. By making namespaces explicit, Piccola is easily able to express various abstractions that would normally require more heavyweight techniques, such as language extensions or meta-programming.