DOCSLIB.ORG

Cisco Pulse Opensocial API Overview

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cisco Pulse Opensocial API Overview CHAPTER 1 Cisco Pulse OpenSocial API Overview This overview discusses these topics: • Cisco Pulse OpenSocial API Overview, page 1-1 • Cisco Pulse OpenSocial API Architecture, page 1-2 • Understanding the URL Templates, page 1-3 Cisco Pulse OpenSocial API Overview OpenSocial is comprised of APIs that enable third-party developers to create web-based social network applications. Cisco Pulse fully supports these categories of OpenSocial APIs: • People • Groups • Application data Cisco Pulse extends these APIs with the REST APIs described in Table 1-1. Table 1-1 Cisco Pulse OpenSocial REST API Extensions REST API Extensions Description Authentication APIs Allows the developer to log into the OpenSocial server, thereby requesting a session ID for authentication. Pulse Locator APIs Auto-completion APIs Allows users to view the Pulse Vocabulary terms that match the term they are typing into the Pulse Locator search interface. People search APIs Allows users to search for people with recent experience with a specified term. Profile search Allows the system to search profiles. Document search APIs Allows users to search for relevant documents for a specified term. Video search APIs Allows users to search for relevant videos for a specified term. Cisco Pulse API Reference Guide OL-21500-02 1-1 Chapter 1 Cisco Pulse OpenSocial API Overview Cisco Pulse OpenSocial API Architecture Table 1-1 Cisco Pulse OpenSocial REST API Extensions (continued) REST API Extensions Description Vocabulary management APIs Vocabulary APIs Allows users to add, modify, delete, and get terms in the Pulse and Restricted Vocabularies. User-suggested tag APIs Allows users to suggest tags for inclusion in the Pulse Vocabulary and business administrators to approve or reject the suggestions. Also allows business administrators to get all or specified user-suggested tags and to modify them. Tag APIs Allows users to add a tag to their profiles, change the status of a tag, and get tags. Profile APIs Allows users to add information to their profiles, modify their profile information. Allows a system administrator to delete profiles. As shown in Figure 1-1, the REST APIs allow a developer to integrate the back-end services of Cisco Pulse with interfaces customized for your organization. Figure 1-1 Cisco Pulse OpenSocial REST APIs REST API request Third-party Cisco Pulse server back-end server REST API response 277558 Cisco Pulse also supports OpenSocial JavaScript API extensions, which allow an OpenSocial gadget to directly invoke Cisco Pulse’s OpenSocial services through JavaScript objects and functions and without explicitly using the Cisco Pulse OpenSocial REST API extensions. For more information, see Chapter 7, “Cisco Pulse OpenSocial JavaScript API Overview.” Cisco Pulse OpenSocial API Architecture The Cisco Pulse OpenSocial API architecture is comprised of these major elements, which are shown in Figure 1-2: • OpenSocial container • REST APIs for people, groups, application data, and activities • OpenSocial API extensions, which are Cisco Pulse-specific REST APIs to retrieve raw data • OpenSocial JavaScript API extensions, which sends requests to get, create, update, and delete Cisco Pulse data that resides on the server. Cisco Pulse API Reference Guide 1-2 OL-21500-02 Chapter 1 Cisco Pulse OpenSocial API Overview Understanding the URL Templates Figure 1-2 Cisco Pulse OpenSocial API Architecture UI Widget UI Widget UI Widget (Cisco Specific) (Cisco Specific) (Customer Specific) JavaScript APIs High-level Pure OpenSocial REST APIs Low-level OpenSocial Java APIs OpenSocial Container REST (OS) to SQL to translation layer SQL Query Layer Groups LDAP MT (Manual Tags) CI Information Information Statistics Information Information 277559 Understanding the URL Templates For each Cisco Pulse OpenSocial REST API, a URL template is provided. For example: http://hostname:7090/social/rest/pulseservices/username/svcId?privilege=privilege&vocabType= vocabType&mainTerm=mainTerm&syn1=syn1&syn2=syn2&syn3=syn3&syn4=syn4&syn5=syn5 In the URL template, the question mark (?) acts as a delimiter. The parameters to the left and right of the question mark have these characteristics: • Parameters to the left of the question mark specify the location of the API. Therefore, the order of these parameters is critical. If you change the order of these parameters, your request fails. The hostname, username, and svcId parameters are present in most of the URL templates. Table 1-2 describes these parameters. • Parameters to the right of the question mark are the Cisco Pulse extensions. The order of these parameters is not critical. You can specify these parameters in any order. A parameter table, which is provided for each API, supplies the expected or optional values for each parameter. Cisco Pulse API Reference Guide OL-21500-02 1-3 Chapter 1 Cisco Pulse OpenSocial API Overview Understanding the URL Templates Table 1-2 General URL Template Parameters Parameter Description Expected Value Status hostname Specifies the name of the host on hostname Required which the OpenSocial server resides. For example, myhost1. This host is the Pulse Connect Appliance. The hostname can also be the IP address of the appliance. username Specifies a Cisco Pulse username, Cisco-Pulse [email protected] Required which you must specify in an email For example, george@ address format. mycompany.com svcId Specifies the ID of the service you are A parameter table, which is provided Required invoking. for each API, supplies the service ID that you must specify for the API. The convention of italics denotes arguments or variables, which must be filled in with a specified value. Note For the sake of brevity, the general parameters in Table 1-2 and authentication-related parameters, which are described in “Login Request” section on page 2-3, are not described with the URL template for each API. Cisco Pulse API Reference Guide 1-4 OL-21500-02.
Load more

Recommended publications
  • Opensocial: from Social Networks to Social Ecosystem
    2007 Inaugural IEEE International Conference on Digital Ecosystems and Technologies (IEEE DEST 2007) OpenSocial: From Social Networks to Social Ecosystem Juliana Mitchell-WongI, Ryszard Kowalczyk', Albena Rosheloval, Bruce Joy2 and Henry Tsai2 'Centre for Information Technology Research, Swinburne University, Hawthorn, VIC, Australia e-mail: (jmitchellwong, rkowalczyk, aroshelova)@ict.swin.edu.au 2Everyday Interactive Networks, Hawthorn, VIC, Australia, e-mail: (brucejoy, henrytsai)@ein.com.au ties to be managed using the one application. GAIM' and Abstract-Unlike the physical world where social ecosys- Trillian2 are two example applications for instant messaging tems are formed from the integrated and managed relation- communities. These applications however do not address ships between individuals and organisations, the online digital any of the fundamental issues: the independent and isolated world consists of many independent, isolated and incompatible nature of communities, the ignorance to overlapping rela- social networks established by organisations that have over- lapping and manually managed relationships. To bring the tionships in different communities, or the manual manage- online digital world in-line with the physical world, integration ment of relationships. of social networks, identification of overlapping relationships Communities on the other hand have moved towards in social networks, and automation of relationship manage- forming alliances with other communities to enable content ment in social networks are required. OpenSocial is a frame- search and retrieval between them by using common ontol- work that enables social networks to interlink and self- use common organise into a social ecosystem guided by the policies of indi- ogy [1]. The of ontology enables communities viduals and organisations. to interlink, but each of these communities assumes that their policies are agreeable by every community in the alli- Index Terms-social framework, self-organised, self- ance.
    [Show full text]
  • Ray Cromwell
    Building Applications with Google APIs Ray Cromwell Monday, June 1, 2009 “There’s an API for that” • code.google.com shows 60+ APIs • full spectrum (client, server, mobile, cloud) • application oriented (android, opensocial) • Does Google have a Platform? Monday, June 1, 2009 Application Ecosystem Client REST/JSON, GWT, Server ProtocolBuffers Earth PHP Java O3D App Services Media Docs Python Ruby Utility Blogger Spreadsheets Maps/Geo JPA/JDO/Other Translate Base Datastore GViz Social MySQL Search OpenSocial Auth FriendConnect $$$ ... GData Contacts AdSense Checkout Monday, June 1, 2009 Timefire • Store and Index large # of time series data • Scalable Charting Engine • Social Collaboration • Story Telling + Video/Audio sync • Like “Google Maps” but for “Time” Monday, June 1, 2009 Android Version 98% Shared Code with Web version Monday, June 1, 2009 Android • Full API stack • Tight integration with WebKit browser • Local database, 2D and 3D APIs • External XML UI/Layout system • Makes separating presentation from logic easier, benefits code sharing Monday, June 1, 2009 How was this done? • Google Web Toolkit is the Foundation • Target GWT JRE as LCD • Use Guice Dependency Injection for platform-specific APIs • Leverage GWT 1.6 event system Monday, June 1, 2009 Example App Code Device/Service JRE interfaces Guice Android Browser Impl Impl Android GWT Specific Specific Monday, June 1, 2009 Shared Widget Events interface HasClickHandler interface HasClickHandler addClickHandler(injectedHandler) addClickHandler(injectedHandler) Gin binds GwtHandlerImpl
    [Show full text]
  • Emergency Management in Social Media Generation
    EMERGENCY MANAGEMENT IN SOCIAL MEDIA GENERATION Deliverable 5.1 Identification of Social Network Providers and API Design Final Thomas Ludwig1, Christian Reuter1 University of Siegen1 September 2014 Work Package 5 Project Coordinator Prof. Dr.‐Ing. Rainer Koch (University of Paderborn) 7th Framework Programme for Research and Technological Development COOPERATION SEC‐2013.6.1‐1: The impact of social media in emergencies D5.1: Identification of Social Network Providers and API Design, Version V1, PU Distribution level Public (PU) Due date 30/09/2014 (M6) Sent to coordinator 30/09/2014 No. of document D5.1 Title Identification of Social Network Providers and API Design Status & Version Final Work Package 5: Information Collection and Presentation Related Deliverables D3.3, D4.1, D5.2, D5.4 Leading Partner University of Siegen Leading Authors Thomas Ludwig, University of Siegen Christian Reuter, University of Siegen Contributors Marc‐André Kaufhold, University of Siegen Federico Sangiorgio, IES (section 5.3) Federica Toscano, IES (section 5.3) Massimo Cristaldi, IES (section 5.3) Mark Tolley, OCC (section 5.4 and 5.5) Mel Mason, OCC (section 5.4 and 5.5) Reviewers Matthias Moi, University of Paderborn Keywords Social Network Provider, API, Open Social, Activity Streams, Facebook, Twitter, Google+, YouTube, Tumblr, Instagram This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under grant agreement no 608352. I D5.1: Identification of Social Network
    [Show full text]
  • Building the Polargrid Portal Using Web 2.0 and Opensocial
    Building the PolarGrid Portal Using Web 2.0 and OpenSocial Zhenhua Guo, Raminderjeet Singh, Marlon Pierce Community Grids Laboratory, Pervasive Technology Institute Indiana University, Bloomington 2719 East 10th Street, Bloomington, Indiana 47408 {zhguo, ramifnu, marpierc}@indiana.edu ABSTRACT service gateway are still useful, it is time to revisit some of the Science requires collaboration. In this paper, we investigate the software and standards used to actually build gateways. Two feasibility of coupling current social networking techniques to important candidates are the Google Gadget component model science gateways to provide a scientific collaboration model. We and the REST service development style for building gateways. are particularly interested in the integration of local and third Gadgets are attractive for three reasons. First, they are much party services, since we believe the latter provide more long-term easier to write than portlets and are to some degree framework- sustainability than gateway-provided service instances alone. Our agnostic. Second, they can be integrated into both iGoogle prototype use case for this study is the PolarGrid portal, in which (Google’s Start Page portal) and user-developed containers. we combine typical science portal functionality with widely used Finally, gadgets are actually a subset of the OpenSocial collaboration tools. Our goal is to determine the feasibility of specification [5], which enables developers to provide social rapidly developing a collaborative science gateway that networking capabilities. Standardization is useful but more incorporates third-party collaborative services with more typical importantly one can plug directly into pre-existing social networks science gateway capabilities. We specifically investigate Google with millions of users without trying to establish a new network Gadget, OpenSocial, and related standards.
    [Show full text]
  • An Analysis of Social Network Connect Services∗
    AN ANALYSIS OF SOCIAL NETWORK CONNECT SERVICES∗ Antonio Tapiador1,V´ıctor Sanchez´ 1 and Joaqu´ın Salvachua´ 1 1Universidad Politecnica´ de Madrid, Av. Complutense 30, Madrid, Spain fatapiador, vsanchez, [email protected] Keywords: Social Networks; API; OAuth; REST: mashups Abstract: Social network platforms are increasingly becoming identity providers and a media for showing multiple types of activity from third-party web sites. In this article, we analyze the services provided by seven of the most popular social network platforms. Results show OAuth emerging as the authentication and authorization protocol, giving support to three types of APIs, client-side or Javascript, server-side or representational state transfer (REST) and streaming. JSON is the most popular format, but there a considerable variety of resource types and a lack of representation standard, which makes harder for the third-party developer integrating with several services. 1 INTRODUCTION for instance: finding friends in the platform. On the other hand, this is also interesting for the provider that Popular social network platforms are leveraging iden- is now showing new kinds of activity in the streams. tity services. They provide authentication commodi- An attempt to provide a unified connect service ties, relieving third-party websites, applications and was made by OpenSocial (Hasel,¨ 2011), a standard services from managing user data. They are also an promoted by Google, Myspace and others, which has increasingly important media. Using already exis- been adopted to some extend. tent identity providers can improve the engagement In this article, we provide an in deep analysis of of users in those third-party sites.
    [Show full text]
  • Personal & Contextual Portability and Plasticity with Opensocial
    Widgets and Spaces: Personal & Contextual Portability and Plasticity with OpenSocial THÈSE NO 5804 (2013) PRÉSENTÉE LE 30 AOUT 2013 À LA FACULTÉ DES SCIENCES ET TECHNIQUES DE L'INGÉNIEUR INSTITUT DE GÉNIE ÉLECTRIQUE ET ÉLECTRONIQUE PROGRAMME DOCTORAL EN INFORMATIQUE, COMMUNICATIONS ET INFORMATION ÉCOLE POLYTECHNIQUE FÉDÉRALE DE LAUSANNE POUR L'OBTENTION DU GRADE DE DOCTEUR ÈS SCIENCES PAR Evgeny BOGDANOV acceptée sur proposition du jury: Dr A. Karimi, président du jury Dr D. Gillet, Dr C. Salzmann, directeurs de thèse Dr E. L.-C. Law, rapporteur Dr L. Moccozet, rapporteur Dr C. Ullrich, rapporteur Suisse 2013 A person who never made a mistake never tried anything new — Albert Einstein To my parents. Acknowledgments This thesis is only partially my work. It would not be possible without my friends, relatives, colleagues who were helping me (knowingly or unknowingly) during this PhD journey. I am hugely grateful to all of you! Denis Gillet and Christophe Salzmann. Thank you for accepting me into your research family, for giving me the freedom in choosing and shaping the research directions according to my interests, for being my mentors. After our discussions I was always leaving your office inspired and highly motivated. This is indeed something! I would like to thank my thesis committee members for reading my thesis and being my examinators: Alireza Karimi, Effie Lai-Chong Law, Carsten Ullrich, Laurent Moccozet. My research work was partially funded through the following projects: ROLE, PALETTE, SWITCH, GO-LAB. I am thankful to these projects and I did appreciate working in them. Stéphane Sire, I owe you a huge chunk of my thesis and my personal development.
    [Show full text]
  • Opensocial + Linked Data in Research Networking: UCSF Profiles Eric Meeks, Anirvan Chatterjee, Brian Tuner, Leslie Yuan “ It’S Basically Like
    Clinical and Translational Science Institute / CTSI at the University of California, San Francisco OpenSocial + Linked Data in Research Networking: UCSF Profiles Eric Meeks, Anirvan Chatterjee, Brian Tuner, Leslie Yuan “ it’s basically like for biomedical researchers ” UCSF Profiles • Contains deep researcher data • Based on Profiles open source code from Harvard, bravely launched by UCSF in 2009 • IIS/.NET + MS SQL Server + Tomcat/Java • UCSF adds OpenSocial (via Shindig) to an “unofficial” copy of the source • OpenSocial version adopted by Wake Forest and Baylor OpenSocial in UCSF Profiles UCTV and other Public YouTube Videos Links to ucsf.edu & other public news stories OpenSocial Challenges for Profiles and Research Networking • OpenSocial data model not a good match for researchers (both a PR and technical challenge) • With only two installations, we already experienced divergent extensions! (Wake Forest and UCSF have different methods for accessing researcher keywords) • How does the OpenSocial standard compare/compete with the Linked Data standard? Research Networking and Linked Data • Linked Open Data (LOD) standard supported by many publicly funded institutions • VIVO, a “competitive” product based on RDF and LOD is awarded a large grant • LOD and VIVO Ontology (extension of FOAF) becomes a recommended standard for research networking • Profiles adopts LOD, UCSF adds OpenSocial to the VIVO product Methods for Integrating Linked Data into OpenSocial • Needed to express semantic data in JSON – MIT Simile – Epimorphics – JSON-LD • Extended OSAPI in Shindig 2.0.2 – osapi.rdf.getViewer(…) – osapi.rdf.getOwner(…) – osapi.rdf.getRDF(…) Advantages of Linked Data and JSON -LD • Decouples data model from the OpenSocial API – Current integration is ontology agnostic • Same API works for people/friends/co- authors/circles/publications/etc.
    [Show full text]
  • Social Media API for Java
    Social Media API for Java JCP EC F2F Meeting Werner Keil Antoine Sabot-Durand Redwood City, California 10 / 01 / 12 Our Goal A JAVA API FOR ACCESS TO SOCIAL NETWORKS 2 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others Proliferation 3 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others Proliferation of Social Media 4 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others Apache Shindig • Open source implementation of OpenSocial & Gadgets specification • An Apache Software project • Available in Java & PHP • http://shindig.apache.org It’s Goal: “Shindig's goal was to allow new sites to start hosting social apps in under an hour's worth of work" 5 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others OpenSocial Container • Become an OpenSocial Container o Get Shindig (PHP or Java) or the Google implementation . http://shindig.apache.org o Look at examples & documentation . http://code.google.com/p/opensocial- resources/wiki/SampleApps • The “official” OpenSocial implementation has shifted – from Shindig to Google Code 6 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others What Is a Gadget? Simple gadgets for getting a Grid proxy credential and running remote commands. Both run on my own Web server. 7 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others Portable Contacts • REST API for Person and Contacts • Open source implementation • Compatible with OpenSocial • http://portablecontacts.net 8 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others SocialSite – Sun’s approach to Social Sun Microsystems • Socialsite: Shindig + gadget based UI written in Java • Open Source https://socialsite.dev.java.net/ 9 © 2010-2012 Werner Keil, Antoine Sabot-Durand and Others Facebooks’ Query Language •All of the Facebook API is basically a set of wrappers around their SQL like FQL query language.
    [Show full text]
  • Towards Inclusive Social Networks for the Developing World
    Towards Inclusive Social Networks for the Developing World Christian Akpona1, Rose Gohoue1, Herve Ahouantchede1, Fatna Belqasmi2(&), Roch Glitho1,3, and Jules Degila1 1 IMSP, Porto Novo, University of Abomey-Calavi, Cotonou, Republic of Benin 2 Zayed University, Abu Dhabi, United Arab Emirates [email protected] 3 Concordia University, Montreal, Canada Abstract. Social networks (e.g. Facebook) are becoming ubiquitous, especially in the developed world. However, they rely on two fundamental assumptions (i.e., reliable Internet connectivity, literacy) that exclude scores of potential end-users, especially in the developing world. Including these potential end-users will require lifting those two assumptions. This paper is a first step towards inclusive social networks in the developing world. It proposes and validates a two-layer system architecture. The proposed architecture allows end-users to access the social network with low-end cellular phones, using voice and Short Message Service (SMS), in addition to traditional access via a computer or smart phone, using keyboards. We have built a proof of concept prototype in which poorly literate end-users are included in two simplified dedicated social networks (a small farmers’ social network and a motorcycle taxis’ social network). Keywords: Social networks Á Developing economies Á Inclusive social networks Á SMS Á Low-end cellular phones Á Text-to-speech 1 Introduction Social networks are becoming ubiquitous, especially in the developed world. Face- book, for instance, announced during the release of its third quarter 2016 results that it had more than a billion daily active end-users. There is still no consensus on the fundamental definition of a social network, especially as most social networks embed a plethora of heteroclite applications.
    [Show full text]
  • Federated (Mobile) Social Networking
    GRUPPO TELECOM ITALIA May 2012 Università di Bologna Federated (Mobile) Social Networking • The past, present & future of the next generation of social communications Telecom Italia /Innovation & Industry Relations – Laurent-Walter Goix laurentwalter.goix@telecomitalia .it Table of contents ► Part 1: Introduction to the Social Networking topic, current trends & issues ► Part 2: Technical overview of the Social Network “standards” landscape ► Part 3: Internal “Research & Prototyping “activities Part 1: Introduction to the Social Networking topic, current trends & issues The value of Federated (Mobile) Social Networking Source: http://makemesocialblog.wordpress.com/2011/02/17/where-were-you/ May 2012 The FbkFacebook story The new communication ppgaradigm, the “wall”, is introduced in September 2006 http://mashable.com/2006/09/05/facebooks-facelift-mini-feeds- and-news-feeds/ GOIX Laurent-Walter / II.RP 4 The value of Federated (Mobile) Social Networking May 2012 Fundamental #1: what is the “wall” about? • For its owner, the “wall” (and its usual settings) can be considered –As the history of private/public activities (social, but potentially SMS sent, calls, etc) –As a privacy filter when propagating information (based on followers/circles/lists) The “wall” (or stream) is an always-on virtual presence on the Internet • For a viewer –Access to *authorized* content anytime, anywhere (without being seen, no real-time constraints) –Notification settings The “wall” is a new way of communicating: asynchronous, indirect • The wall may only be a
    [Show full text]
  • Gadget Server –Renders Gadget XML As HTML/JS/CSS • Opensocial Data Server –Restful API Server (In-Progress)
    A Technical Overview Chris Schalk, Developer Advocate 9/16/2008 Agenda • OpenSocial Concepts • Building OpenSocial Applications • Hosting OpenSocial Applications • Google Friend Connect 3 Agenda • OpenSocial Concepts • Building OpenSocial Applications • Hosting OpenSocial Applications • Google Friend Connect 4 Too many platforms! Standards based OpenSocial Write once… Deploy everywhere Use multiple times Cooooool! Not just Social Network Sites • Social network sites - Profiles and home pages ex: MySpace, Hi5 • Personal dashboards – Widgets ex: iGoogle, My Yahoo • Sites based around a Social Object ex: Flickr, YouTube • Corporate CRM systems ex: Oracle, SalesForce.com • Any web site 10 OpenSocial “Containers” Today: 375 Million User Reach Where is OpenSocial live today? Live to Users: Live Developer Sandboxes: • MySpace • iGoogle • orkut • imeem • Hi5 • CityIN • Freebar • Tianya • Friendster • Ning • Webon from Lycos • IDtail • Plaxo Pulse • YiQi • Mail.ru • Netlog - New! • Hyves - New! Individual Developer Links: http://code.google.com/apis/opensocial/gettingstared.html OpenSocial today 375,000,000 users 150,000,000 installs 4,500+ apps Pipeline of 100+ containers worldwide 20,000+ developers 10,000,000 daily app users 14 OpenSocial Roadmap • Version 0.5 was released in a “developer release” on Nov 1st. • First “sandbox” was made available on Orkut • Version 0.6 was released in December • Initial version of Shindig server software was launched as Apache incubator project • Other sandboxes came live - Hi5, Ning, Plaxo … • Version
    [Show full text]
  • Vysoke´Ucˇenítechnicke´V Brneˇ
    VYSOKE´ UCˇ ENI´ TECHNICKE´ V BRNEˇ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA INFORMACˇ NI´CH TECHNOLOGII´ U´ STAV INFORMACˇ NI´CH SYSTE´ MU˚ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION SYSTEMS SOCIAL NETWORK INTEGRATION INTO AN INFOR- MATION PORTAL BAKALA´ Rˇ SKA´ PRA´ CE BACHELOR’S THESIS AUTOR PRA´ CE DRAHOMI´RA HERRMANNOVA´ AUTHOR BRNO 2010 VYSOKE´ UCˇ ENI´ TECHNICKE´ V BRNEˇ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA INFORMACˇ NI´CH TECHNOLOGII´ U´ STAV INFORMACˇ NI´CH SYSTE´ MU˚ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION SYSTEMS INTEGRACE SOCIA´ LNI´CH SI´TI´ DO INFORMACˇ NI´HO PORTA´ LU SOCIAL NETWORK INTEGRATION INTO AN INFORMATION PORTAL BAKALA´ Rˇ SKA´ PRA´ CE BACHELOR’S THESIS AUTOR PRA´ CE DRAHOMI´RA HERRMANNOVA´ AUTHOR VEDOUCI´ PRA´ CE Ing. RADEK BURGET, Ph.D. SUPERVISOR BRNO 2010 Abstrakt Cílem bakalářské práce Integrace sociálních sítí do informačního portálu“ bylo vytvoření ” portálu, který by předvedl způsoby integrace současných sociálních sítí na internetu do jednoho portálu. Práce obsahuje seznámení se základními pojmy v této oblasti, jako je Social Web, Web 2.0 a sociální sítě. Dále představuje jednotlivé sociální sítě, které byly intergovány do portálu, a technologie a standardy k tomu použité - OpenID, OAuth a OpenSocial. Dále práce popisuje také jednotlivé etapy vývoje zadaného webového portálu. V závěru práce je také shrnutí a zhodnocení výsledků a zamyšlení nad možnými rozšířeními výsledného portálu. Abstract The task of the Bachelor’s Thesis Social Network Integration into an Information Portal“ ” was creating a web portal, which would demonstrate technical possibilities of integration of current social networks on the internet into one portal. The thesis contains introduction of basic concepts in this field - Social Web, Web 2.0 and Social Networking.
    [Show full text]