XRX is a new web development architecture that is a milestone in elegant simplicity. XRX stands for: XForms on the client REST interfaces and XQuery on the server Because XRX uses a single model for data (XML) it avoids the translation complexity of other architectures. The simplicity and elegance of XRX allows developers to focus on other value-added features of web application development and enables non-programmers to create a rich web interaction experience without the need to use procedural programming languages.
CloudKit provides RESTful JSON storage with optional OpenID and OAuth support, including OAuth Discovery. Stored entities are versioned. Services manage their own storage and do not require schema updates when models change. CloudKit is Rack middleware and as such can be used on its own or alongside other Rack-based applications or middleware components such as Rails, Merb or Sinatra. The CloudKit stack provides an optional OAuth Filter with support for OAuth Core 1.0 and OAuth Discovery. Share your APIs with other web services, desktop apps, Open Social gadgets and more. + An OpenID Filter supplies authentication for browser-based clients. Both the OAuth and OpenID Filters collaborate to simultaneously provide login screens and auth challenges in a single HTTP response. + Discoverable, schema-free, auto-versioned JSON storage tracks each version of each JSON document to allow progressive diff/merge with decentralized or occasionally connected clients.
This is the Watson Web interface for searching ontologies and semantic documents using keywords. This interface is subject to frequent evolutions and improvements. If you want to share your opinion, suggest improvement or comment on the results, don't hesitate to contact us... At the moment, you can enter a set of keywords (e.g. "cat dog old_lady"), and obtain a list of URIs of semantic documents in which the keywords appear as identifiers or in literals of classes, properties, and individuals. You can also use "jokers" in the keywords (e.g., "ca? dog*"). Navigation in the results follows very simple principles. First, whenever a sign appears, it can be used to display additional information about the element it is attached with. Second, every URI is clickable. A URI is a link to a page describing either the entity or the semantic document it corresponds to, and gives access to additional functionalities using this particular entity or document.
For much of the first year or two in the life of Web services - and indeed all of their history up to that point - they were about remote procedure calls (RPC); exposing remote APIs across the Internet in order to facilitate machine-to-machine communication and ultimately, business-to-business integration over the Internet. It didn’t take very long however, for Web services proponents to realize that they needed to distance themselves from RPC and its well-deserved reputation as a poor large scale integration architectural style, due to the failure of systems such as CORBA, DCOM, and RMI to see any widespread use on the Internet. So, sometime in 2000/2001, collective wisdom in the space shifted towards a preference for “document oriented” services. Vendors quickly jumped on board with upgraded toolkits, and that was that; documents were the New Big Thing.
The ADO.NET Data Services framework consists of a combination of patterns and libraries that enable the creation and consumption of data services for the web. The goal of the ADO.Net Data Services framework is to facilitate the creation of flexible data services that are naturally integrated with the web, using URIs to point to pieces of data and simple, well-known formats to represent that data, such as JSON and plain XML. This results in the data service being surfaced to the web as a REST-style resource collection that is addressable with URIs and that agents can interact with using the usual HTTP verbs such as GET, POST or DELETE. Many of the Microsoft cloud data services (Windows Azure tables, SQL Data Services, etc.) expose data using the same REST interaction conventions followed by ADO.NET Data Services. This enables using the ADO.NET Data Services client libraries and developer tools when working not only with on premises services created using the ADO.NET Data Services Fra
Picture Services is a code sample that highlights the REST and syndication capabilities of WCF in the .NET Framework 3.5. In a nutshell, the projects in this code sample show how to syndicate pictures retrieved from Windows Desktop Search, Flickr, or the local file system. This screencast takes you on a quick tour of the sample, showing the basics of the projects. You can download Picture Services here.