Multiple users Zero install SaaS model: instant access to features We worry about the data management, but leave you in control All new (versions) Talis applications now built on same Platform, e.g. Engage. So can not only build new apps on the service, can also access data underlying existing services
i.e. similar to Amazon S3. Can upload and store any kinds of data. May be web site assets, e.g. images, CSS, javascript, etc. May be other documents or collateral.
i.e. similar to Amazon S3. Can upload and store any kinds of data. May be web site assets, e.g. images, CSS, javascript, etc. May be other documents or collateral.
Main set of features are around the structured data storage. Management of RDF metadata. Resource Description Framework More later but basically a means to capture in a highly structured and flexible way, metadata about anything.
As you remain in control of your data, you obviously want to control who has access to it. By default on the platform we allow public read access, but this can be changed. Each store can has its own set of access control options, i.e. which platform users can access which features. There are a useful set of defaults, i.e. public read, admin to add, update or modify configuration
Roy Fielding’s thesis, responsible for many of the Internet RFCs. Describes a formal basis for the web architecture. Growing agreement that following these architectural principles is the best way to build internet-scale applications, whether that means web sites or web APIs. Anything else means you’re working against the web architecture meaning that you’re using a sub-optimal solution. This is why the Talis Platform follows these principles rather than using, say, SOAP or some other web services APIs. REST, essentially, involves using HTTP correctly. About understanding and using the HTTP protocol to its fullest extent, because in doing so you allow web browsers, proxy servers, search engines, etc to all interact with you application correctly and in a way that has massive scalability.
And al of this is made available through a standards compliant framework. With essentially one exception (which I’ll point out later) everything that we’ll look at is based on open internet standards. The technologies like HTTP, RDF, SPARQL, all of the data formats we generate are open standards. This is part of the Talis ethos. We don’t believe in proprietary software. We use and create a lot of open source software ourselves and believe this is the only viable way for internet services to develop.
As well as following the REST architectural guidelines, within the Platform team we have our own set of best practices that apply to the design of new services. The service checklist is online as part of the API documentation, but includes things like ensuring we have a consistent url structure, that there’s a human interface to every API, to make it easy to play with the system. That error messages are human-readable, etc
E.g. public data, but also private authentication data.
E.g. public data, but also private authentication data.
E.g. public data, but also private authentication data.
Want to review some basic concepts and technologies that underpin the design and implementation of the Platform. How many people already understand the terms REST, Content Negotation, RDF.
E.g. public data, but also private authentication data.