|COOKIES: By using this website you agree that we can place Google Analytics Cookies on your device for performance monitoring.|
This document is intended for webmasters who use feeds from talks.cam on their pages. It provides a sense of what to expect from the service. This is more of a reference page – for more practical information, find out more about disseminating talks.
The document is currently being edited to create a first draft and should be treated as highly provisional.
Talks.cam public specification
Filtering of user generated content
Structure and content of feeds
Feeds are used to take talks.cam content and use it on other websites. Some examples are at http://www.inference.phy.cam.ac.uk/talks/penguin/compatible.html
General structure of URL
The general structure of a url to get a feed from talks.cam is:
LISTID is the number identifying the listFORMAT may take these values:
/show/archive/LISTID is a special case – it is simply a convenience shortcut to /show/index/LISTID?seconds_after_today=0&reverse_order=true
General structure of parameters
The url may be qualified with the following optional optional parameters:
If several parameters are used that restrict the number of talks displayed, then the restrictions will be ANDed.
If no parameters are provided, then all talks in the list whose start_time is after midnight this morning will be displayed.
Time is specified in seconds since the start of 1970.
Possible layoutsPossible values for the optional layout parameter are:
A note on term datesTalks.cam assumes that there are four terms a year:
document.write("html fragments that display the talks")
The html fragments will contain html created by the talks.cam system. If layout=embed is used, then the webpage must provide appropriate css to format the page. If layout=embedcss is used, then talks.cam will provide some basic css to format the talks.
To ensure proper (and safe) display of the feed, the webpage server MUST specify that the page is encoded in the UTF -8 character set.
To reduce the possibility of tampering with talks.cam it is hosted on a server where every attempt has been made to secure access. Remote login access is restricted to a small number of talks.cam managers. However, the server is shared with several other web sites, which means its potential for compromise has been increased.
Changes to this document