1. Dynamic Content and Protocol-Level Interoperability hussein suleman uct cs honours 2006

2. What are CMSes?  CMS= Content Management System  Online systems to create, store, edit, secure, preserve, transform and publish original and acquired digital content.  Examples: Slashdot Freshmeat SourceForge Wikipedia

3. Zope.org

4. PHPNuke, PostNuke, Zope  Manage basic content (pages) and gather resources from different locations.  Easy to use and install for end users.  Professional appearance.  Minimal installation resources.  Modular and extensible. Portal approach to user interface.

5. Wikipedia

6. Wiki  Wikis are collaborative website editors, using a Web interface.  Every page (generally) has an “edit” button.  HTML is too complex so it is simplified e.g., !! heading, *bullets, _bold_ New pages are created by linking to them.  Security is not necessary - actions can be undone by an administrator.

7. Blogger.com

8. Weblogs  Online Web-based journals. There are also online photo albums, shopping lists, CD inventories, etc.  Simple interface for non-techie users to publish thoughts.  Single or group.  Usually free - what are the economics?

9. Moodle

10. Learning Management Systems  Learning Management Systems (LMSes) handle not just creation and dissemination of content, but provide learning-specific facilities as well. e.g., assignment submission, online testing  LMSes are a superset of CMSes. Learning is not just about content!  LMSes follow Web standards as well as particular learning-related standards: IMS Metadata Set, Content packaging, Question and Test Interoperability SCORM Content Packaging/Delivery

11. Ananzi

12. Web CMS/Portal Interoperability  Federated Authentication  Federated Search  Content Syndication

13. Federated Authentication  Shibboleth is a networked authentication/authorisation model. Single sign-on model. Access without identity!  Only by attributes e.g., student at UCT. Privacy is user-controlled – users can decide how much information to pass on to third parties. Trust relationships are established among collaborating systems out-of-band. SAML records are exchanged to specify attributes (and club membership) of users.  Security Assertion Markup Language (SAML) is an XML-based security assertion language.

14. Federated Search Protocols 1/2  SDLIP (Simple Digital Library Interoperability Protocol) Defines simple HTTP/CORBA-based interfaces for remote searching (esp. wrapping existing search systems) Stateless/ful a/synchronous operation 3 sub-interfaces  source metadata  search  result access

15. Federated Search Protocols 2/2  Z39.50 is the traditional remote search protocol for library systems. ANSI/NISO/ISO standard Comparatively complicated syntax/operation Based on older standards (1998)  Latest standards for federated search: SRW – Search/Retrieve for the Web SRU – Search/Retrieve URL mechanism?  http://myserver.com/myurl/searchRetrieve?quer y=dc.title=cat&maximumRecords=10&recordSchema =http%3a//www.loc.gov/mods/&sortKeys=title,dc &startRecord=1 (excerpt from ZING website)

16. SRW Request SOAPAction: "searchRetrieve" (dc.author exact "jones" prox///5 title >= "smith") /record/title,"http://www.loc.gov/zing/srw/dcsche ma/v1.0/",1,0,highValue /record/datafield[@tag="100"]/subfield[@code="a"],"http://www.l oc.gov/marcxml/",,,"Smith" 1 10 http://www.loc.gov/mods/ (excerpt from ZING website)

17. SRW Response 2 8c527d60-c3b4-4cec-a1de-1ff80a5932df 600 http://www.loc.gov/mods/ <?xml version="1.0" encoding="UTF- 8"?> <mods xmlns:xlink="http://www.w3.org/TR/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/" xsi:schemaLocation="http://www.loc.gov/mods/ http://www.loc.gov/standards/mods/mods.xsd"> <titleInfo> <title>Sound and fury : the making of the punditocracy /</title> </titleInfo> <name type="personal"> <namePart>Alterman, Eric.</namePart> <role>creator</role> </name>... 1... (excerpt from ZING website)

18. Content Syndication - RSS  Really Simple Syndication (RSS) is a (predecessor to SOAP) standard to transfer a list of recently updated entries from one CMS to another.  RSS 2.0 is arguably a dynamically-generated “data format” rather than a “protocol”.  Lots of different (incompatible) versions: 0.91, 0.92, 2.0, etc.  RSS 0.92 used the Resource Description Framework (RDF) XML format to encode items.  Blogs, Wikis and other CMSes generally support RSS, sometimes both as client and server.  Alternatives? OAI-PMH?

19. RSS Time Sequence ClientServer HTTP GET /rss.xml RSS Document v1 HTTP GET /rss.xml RSS Document v2......

20. RSS Example Liftoff News http://liftoff.msfc.nasa.gov/ Liftoff to Space Exploration. en-us Tue, 10 Jun 2003 04:00:00 GMT Tue, 10 Jun 2003 09:41:01 GMT http://blogs.law.harvard.edu/tech/rss Weblog Editor 2.0 editor@example.com webmaster@example.com Star City http://liftoff.msfc.nasa.gov/news/2003/news-starcity.asp How do Americans get ready to work … Tue, 03 Jun 2003 09:39:21 GMT http://liftoff.msfc.nasa.gov/2003/06/03.html#item573 Sky watchers in Europe, Asia, and parts of Alaska and Canada will experience a <a href="http://science.nasa.gov/headlines/y2003/30may_solareclipse.htm">partial eclipse Fri, 30 May 2003 11:06:42 GMT http://liftoff.msfc.nasa.gov/2003/05/30.html#item572 source: http://www.rssboard.org/files/sample-rss-2.xml

21. RSS Basic Structure some channel some link stuff… an_item … …

22. RSS Channel Tags TagDescription titlename of the channel linkURL of website corresponding to channel descriptiondescription of channel languagelanguage of channel copyrightcopyright statement managingEditoremail of content editor ttlnumber of minutes before channel expires and must be refetched pubDatetime when content was created lastBuildDatelast time content was updated

23. RSS Item Tags TagDescription titlename of the item linkURL of the item descriptionsynopsis of item guidunique identifier for item categoryclassification of item commentsURL of page where comments can be added sourcethe RSS channel an element came from pubDatetime when item was created

24. RSS Cloud  Notification system for RSS Why contact the server waiting for an update when the server can contact you when it updates its content?  Two methods: client  cloud_server, registers the procedure, port and transport protocol (e.g., SOAP) to use to notify the client when content changes. cloud_server  client, sends the RSS URL for the changed document.  Clients must register every 24 hours.

25. Podcasting  Podcasting refers to the distribution of multimedia (non-text) files over the Internet using RSS-like technology.  Media files are linked to RSS items using the tag and automatically downloaded to mobile devices. source: http://www.rssboard.org/rss-specification

26. References  Internet2 (2006) Shibboleth Project. Website http://shibboleth.internet2.edu/ http://shibboleth.internet2.edu/  Library of Congress (2006) SRU: Search and Retrieve via URL. Website http://www.loc.gov/standards/sru/ http://www.loc.gov/standards/sru/  RSS Advisory Board (2005) Really Simple Syndication: RSS 2.0.1 Specification (revision 6). Available http://www.rssboard.org/rss- specificationhttp://www.rssboard.org/rss- specification  RSS Advisory Board (2001) Really Simple Syndication: RssCloud API. Available http://www.rssboard.org/rsscloud-interface http://www.rssboard.org/rsscloud-interface  Sureau, D. G. (2006) RSS - Really Simple Syndication. Available http://www.xul.fr/en-xml- rss.htmlhttp://www.xul.fr/en-xml- rss.html