DOCSLIB.ORG

International Journal of Computer Science and Intelligent

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Open Source Platform for Universal Feed Retrieval and Management Prince Choudhary1, Shiva Venkatesh2 and John Paul C.I3 1,2,3 Information Science & Engineering, The National Institute of Engineering Mysuru Abstract— Now a days people are linked to a lot of websites, they want to access all these websites frequently. They boom in social media like Facebook, Twitter, Instagram, etc. has made life of people much easier with the communicating mediums they provide. But the boom has caused people not able to get the required content that one wants the most because they are spread across multiple or a large number of websites around the Globe. To tackle this problem comes RSS. With RSS it is possible to distribute updated web content from one web site to hundreds of other web sites around the world. RSS allows fast and robust browsing for news and their updates on social media. Keywords—social media; communicating; boom; robust; browsing. I. INTRODUCTION RSS stands for Really Simple Syndication. RSS was designed to show filtered data. If there is no RSS, users would have to check every site daily for new updates. This would be very time- consuming for users. With an RSS feed (often called a News feed) they can check your site quickly using an RSS aggregator (it is set of programs which collect and short data). Since RSS collects small data it is fast-loading and it can easily be used with cell phones or PDA's services. These with similar information without effort can share informations on web sites to make them more useful and robust. II. ALL ABOUT RSS RSS stands for Really Simple Syndication or often called Rich Site Summary. RSS is used by news weblogs, websites and podcasting and among other things. RSS feeds provides contents of web, or summaries what the web constitute, along with links to the full versions of the web content. RSS delivers this data or information as an XML file called an RSS feed, RSS stream, web feed, or RSS channel. In addition to facilitating syndication, RSS feeds allow a website's frequent readers to monitor updates on the site whenever they become available using an aggregator. The aggregator provides a robust look of the content in one browser display or desktop application. Such aggregators (applications) are also termed as RSS readers, feed readers, feed aggregators or news readers. III. NECESSITIES AND BENEFITS 3.1. RSS is Necessary for: News sites for listing news with title, date and descriptions. Companies for listing news and new products. Calendars for listing upcoming events and important days. Site changes for listing changed pages or new pages. 3.2. The benefits of using RSS are: With RSS user can choose to view the news that he want, the news that interest him and are relevant to his your work. With RSS user can extract wanted information from unwanted information. With RSS user can create his own news channel, and publish it to the Internet. @IJMTER-2016, All rights Reserved 62 International Journal of Modern Trends in Engineering and Research (IJMTER) Volume 03, Issue 06, [June– 2016] ISSN (Online):2349–9745; ISSN (Print):2393-8161 IV. IMPLEMENTATION 4.1. RSS is Written in XML These are commonly used tags in creation of an RSS file: <channel> - It describes the RSS feed. <title> - It defines the title of the channel. <link> - It defines the hyperlink to the channel. <description> - It describes the channel. <category> - It is used to specify a category for your feed. <copyright> - It notifies about copyrighted material. <image> - It allows an image to be displayed when aggregators present a feed. <language> - It is used to specify the language used to write your document. <item> - It defines an article or "story" in the RSS feed. <author> - It is used to put the e-mail address of the author. <enclosure> - It allows a media-file to be included with an item. 4.2. Following are the steps to get your RSS file up on the web: Give name to the file, must have an .xml extension. Validate your RSS file using some validator application available online. The RSS file must be uploaded to the web directory on your web server. Copy the RSS Logo or XML Logo button to your web directory. Put the buttons of RSS or XML on the page where you will offer RSS to other users around the globe. Then add a link to the button that links to the RSS file. Submit your RSS feed to the RSS Feed Directories. Register your feed with the major search engines like google, bing, yahoo etc. After registering your RSS feed, you must make sure that you update your content often and that your RSS feed is always uninterruptedly available. V. CONCLUSION RSS has become a necessity because of the trend of focus on content. Due to increasing content it is necessary to have the relevant data as per choice of the user. Hence comes RSS as a savior to the solution for this problem. It is going to be a big thing in future as content volume will keep on increasing and user feed filtering need will keep on increasing. Despite the challenges RSS is the most optimal and appropriate technology which must be tapped to provide better experience to users and increase or expand the reach of your website. REFERENCES [1] "The rss and xml application Media Type". The Working Group of Network. June 12, 2008. Retrieved 2009-09-26. [2] "Web feeds | RSS | The Guardian | bbc.co.uk", The BBC, London, 2009, webpage: BBCUK-webfeeds. [3] "XML 1.0 Namespaces" . W3C. August 11, 2008. [4] "NMN Directions for Future". Netscape Communications. Archived from the original on 2002-11-05. Retrieved 2008-11-21 @IJMTER-2016, All rights Reserved 63 .
Recommended publications
  • Architecture of the World Wide Web, First Edition Editor's Draft 14 October 2004

    Architecture of the World Wide Web, First Edition Editor's Draft 14 October 2004

    Architecture of the World Wide Web, First Edition Editor's Draft 14 October 2004 This version: http://www.w3.org/2001/tag/2004/webarch-20041014/ Latest editor's draft: http://www.w3.org/2001/tag/webarch/ Previous version: http://www.w3.org/2001/tag/2004/webarch-20040928/ Latest TR version: http://www.w3.org/TR/webarch/ Editors: Ian Jacobs, W3C Norman Walsh, Sun Microsystems, Inc. Authors: See acknowledgments (§8, pg. 42). Copyright © 2002-2004 W3C ® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. Abstract The World Wide Web is an information space of interrelated resources. This information space is the basis of, and is shared by, a number of information systems. In each of these systems, people and software retrieve, create, display, analyze, relate, and reason about resources. The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support. Status of this document This section describes the status of this document at the time of its publication.
  • Supplement 211: Dicomweb Support for the Application/Zip Payload

    Supplement 211: Dicomweb Support for the Application/Zip Payload

    5 Digital Imaging and Communications in Medicine (DICOM) Supplement 211: 10 DICOMweb Support for the application/zip Payload 15 20 Prepared by: Bill Wallace, Brad Genereaux DICOM Standards Committee, Working Group 27 1300 N. 17th Street Rosslyn, Virginia 22209 USA 25 Developed in accordance with work item WI 2018 -09 -C VERSION: 19 January 16, 2020 Table of Contents Scope and Field of Application ........................................................................................................................................ iii 30 Open Questions ....................................................................................................................................................... iii Closed Questions .................................................................................................................................................... iiii 8.6.1.3.1 File Extensions ................................................................................................................................. viv 8.6.1.3.2 BulkData URI ................................................................................................................................... viv 8.6.1.3.3 Logical Format ........................................................................................................................................ viv 35 8.6.1.3.4 Metadata Representations ...................................................................................................................... viv Scope and Field of Application
  • Digital Fountain Erasure-Recovery in Bittorrent

    Digital Fountain Erasure-Recovery in Bittorrent

    UNIVERSITÀ DEGLI STUDI DI BERGAMO Facoltà di Ingegneria Corso di Laurea Specialistica in Ingegneria Informatica Classe n. 35/S – Sistemi Informatici Digital Fountain Erasure Recovery in BitTorrent: integration and security issues Relatore: Chiar.mo Prof. Stefano Paraboschi Correlatore: Chiar.mo Prof. Andrea Lorenzo Vitali Tesi di Laurea Specialistica Michele BOLOGNA Matricola n. 56108 ANNO ACCADEMICO 2007 / 2008 This thesis has been written, typeset and prepared using LATEX 2". Printed on December 5, 2008. Alla mia famiglia “Would you tell me, please, which way I ought to go from here?” “That depends a good deal on where you want to get to,” said the Cat. “I don’t much care where —” said Alice. “Then it doesn’t matter which way you go,” said the Cat. “— so long as I get somewhere,” Alice added as an explanation. “Oh, you’re sure to do that,” said the Cat, “if you only walk enough.” Lewis Carroll Alice in Wonderland Acknowledgments (in Italian) Ci sono molte persone che mi hanno aiutato durante lo svolgimento di questo lavoro. Il primo ringraziamento va ai proff. Stefano Paraboschi e Andrea Vitali per la disponibilità, la competenza, i consigli, la pazienza e l’aiuto tecnico che mi hanno saputo dare. Grazie di avermi dato la maggior parte delle idee che sono poi confluite nella mia tesi. Un sentito ringraziamento anche a Andrea Rota e Ruben Villa per l’aiuto e i chiarimenti che mi hanno gentilmente fornito. Vorrei ringraziare STMicroelectronics, ed in particolare il gruppo Advanced System Technology, per avermi offerto le infrastrutture, gli spa- zi e tutto il necessario per svolgere al meglio il mio periodo di tirocinio.
  • Fast and Scalable Pattern Mining for Media-Type Focused Crawling

    Fast and Scalable Pattern Mining for Media-Type Focused Crawling

    Provided by the author(s) and NUI Galway in accordance with publisher policies. Please cite the published version when available. Title Fast and Scalable Pattern Mining for Media-Type Focused Crawling Author(s) Umbrich, Jürgen; Karnstedt, Marcel; Harth, Andreas Publication Date 2009 Jürgen Umbrich, Marcel Karnstedt, Andreas Harth "Fast and Publication Scalable Pattern Mining for Media-Type Focused Crawling", Information KDML 2009: Knowledge Discovery, Data Mining, and Machine Learning, in conjunction with LWA 2009, 2009. Item record http://hdl.handle.net/10379/1121 Downloaded 2021-09-27T17:53:57Z Some rights reserved. For more information, please see the item record link above. Fast and Scalable Pattern Mining for Media-Type Focused Crawling∗ [experience paper] Jurgen¨ Umbrich and Marcel Karnstedt and Andreas Harthy Digital Enterprise Research Institute (DERI) National University of Ireland, Galway, Ireland fi[email protected] Abstract 1999]) wants to infer the topic of a target page before de- voting bandwidth to download it. Further, a page’s content Search engines targeting content other than hy- may be hidden in images. pertext documents require a crawler that discov- ers resources identifying files of certain media types. Na¨ıve crawling approaches do not guaran- A crawler for media type targeted search engines is fo- tee a sufficient supply of new URIs (Uniform Re- cused on the document formats (such as audio and video) source Identifiers) to visit; effective and scalable instead of the topic covered by the documents. For a scal- mechanisms for discovering and crawling tar- able media type focused crawler it is absolutely essential geted resources are needed.
  • Describing Media Content of Binary Data in XML W3C Working Group Note 4 May 2005

    Describing Media Content of Binary Data in XML W3C Working Group Note 4 May 2005

    Table of Contents Describing Media Content of Binary Data in XML W3C Working Group Note 4 May 2005 This version: http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504 Latest version: http://www.w3.org/TR/xml-media-types Previous version: http://www.w3.org/TR/2005/NOTE-xml-media-types-20050502 Editors: Anish Karmarkar, Oracle Ümit Yalç&#305;nalp, SAP Copyright © 2005 W3C ® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. > >Abstract This document addresses the need to indicate the content-type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected content-type(s) associated with binary element content. It is expected that the additional information about the content-type will be used for optimizing the handling of binary data that is part of a Web services message. Status of this Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. This document is a W3C Working Group Note. This document includes the resolution of the comments received on the Last Call Working Draft previously published. The comments on this document and their resolution can be found in the Web Services Description Working Group’s issues list. There is no technical difference between this document and the 2 May 2005 version; the acknowledgement section has been updated to thank external contributors.
  • 2016 Technical Guidelines for Digitizing Cultural Heritage Materials

    2016 Technical Guidelines for Digitizing Cultural Heritage Materials

    September 2016 Technical Guidelines for Digitizing Cultural Heritage Materials Creation of Raster Image Files i Document Information Title Editor Technical Guidelines for Digitizing Cultural Heritage Materials: Thomas Rieger Creation of Raster Image Files Document Type Technical Guidelines Publication Date September 2016 Source Documents Title Editors Technical Guidelines for Digitizing Cultural Heritage Materials: Don Williams and Michael Creation of Raster Image Master Files Stelmach http://www.digitizationguidelines.gov/guidelines/FADGI_Still_Image- Tech_Guidelines_2010-08-24.pdf Document Type Technical Guidelines Publication Date August 2010 Title Author s Technical Guidelines for Digitizing Archival Records for Electronic Steven Puglia, Jeffrey Reed, and Access: Creation of Production Master Files – Raster Images Erin Rhodes http://www.archives.gov/preservation/technical/guidelines.pdf U.S. National Archives and Records Administration Document Type Technical Guidelines Publication Date June 2004 This work is available for worldwide use and reuse under CC0 1.0 Universal. ii Table of Contents INTRODUCTION ........................................................................................................................................... 7 SCOPE .......................................................................................................................................................... 7 THE FADGI STAR SYSTEM .......................................................................................................................
  • Specifications for Implementing Web Feeds in DLXS Kevin S

    Specifications for Implementing Web Feeds in DLXS Kevin S

    Hawkins 1/5/2011 5:01:52 PM Page 1 of 5 * SCHOLARLY PUBLISHING OFFICE WHITEPAPER Specifications for implementing web feeds in DLXS Kevin S. Hawkins Executive Summary SPO uses DLXS to deliver nearly all of its publications online, but this software does not offer any functionality for web feeds (commonly called RSS feeds). The components of web feeds are reviewed, and recommendations are made for implementing Atom 1.0 web feeds in SPO publications using a script run during releasing which determines which content to push to the feed. Motivations Members of the editorial board of the Journal of Electronic Publishing (collid jep) and SPO staff have requested that web feed functionality be provided for SPO publications. This would allow end users to subscribe to feeds of not only serial content (the obvious use) but in theory any other collection to which content is added, especially on a regular basis. A feed could provide a single notice that a collection has been updated, perhaps with a table of contents (henceforth a small feed), or instead contain separate notices for each item added to the collection (a large feed). Components of a web feed A web feed operates with three necessary components: • a website that syndicates (or publishes) a feed • a feed standard being used by the website • the end user’s news aggregator (feed reader or news reader), which retrieves the feed periodically. A feed is an XML document containing individual entries (also items, stories, or articles). Syndicating a feed The content provider’s website often has buttons (icons called chicklets) to be used by the end user to add a feed to his or her news aggregator.
  • Despliegue España-América Latina De Broadcatching E-Learning

    Despliegue España-América Latina De Broadcatching E-Learning

    Despliegue España-América Latina de Broadcatching e-learning Rafael García Monroy E.T.S.I.T. U.P.M. Departamento Ingeniería de Sistemas Telemáticos e-mail: [email protected] Abstract . Los avances tecnológicos y la eliminación de fronteras que resultan del potente y exponencial despliegue de Internet permiten que compartir vídeos de material educativo de gran calidad sea viable. Ya que las exigencias de los usuarios finales –alumnos- crecen paralelamente a la adopción de los avances mencionados, y las posibilidades reales de mejorar los servicios son una realidad, no queda más que emplear las herramientas existentes para crear nuevos modelos innovadores que mejoren constantemente las plataformas de difusión de conocimiento, pilar del desarrollo sostenible. El siguiente artículo describe el despliegue de un modelo e-learning basado en Broadcatching (BitTorrent, + RSS), a través del cual clases de vídeo grabadas en España podrán ser inmediatamente distribuidas a universidades latinoamericanas con las que se tenga convenio, compartiendo recursos de red y, de gran importancia, diseminando los ficheros educativos con una excelente calidad de contenido. De esta manera, la distancia, el costo de distribución y las limitaciones temporales pasan a segundo plano, permitiendo que los contenidos educativos de primera calidad tengan un acceso de naturaleza universal. Palabras clave: BitTorrent, broadcatching, e-learning, P2P, RSS, vídeo. 1 Introducción redes de distribución. Y es precisamente este el punto que hay que explotar para que el alumno obtenga el La cooperación en cualquier ámbito conlleva al mejor contenido educativo posible: la obtención de desarrollo sostenible, en que las partes implicadas vídeos de clase de alta definición que son pesados, comparten el fruto de la inversión.
  • Media Type Application/Vnd.Oracle.Resource+Json

    Media Type Application/Vnd.Oracle.Resource+Json

    New Media Type for Oracle REST Services to Support Specialized Resource Types O R A C L E WHITEPAPER | M A R C H 2 0 1 5 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Contents Introduction 3 Conventions and Terminology 3 Core terminology 3 Singular Resource 4 Collection Resource 8 Exception Detail Resource 13 Status Resource 14 Query Description Resource 15 create-form Resource 16 edit-form Resource 17 JSON Schema 18 IANA Considerations 28 References 28 Change Log 28 2 | ORACLE WHITEPAPER: NEW MEDIA TYPE FOR ORACLE REST SERVICES TO SUPPORT SPECIALIZED RESOURCE TYPES Introduction This document defines a new media type, application/vnd.oracle.resource+json, which can be used by REST services to support the specialized resource types defined in the following table. Resource Type Description Singular Single entity resource, such as an employee or a purchase order. For more information, see “Singular Resource.” Collection List of items, such as employees or purchase orders. See “Collection Resource.” Exception Detail Detailed information about a failed request. See “Exception Detail Resource.” Status Status of a long running job. See “Status Resource.” Query description Query syntax description used by client to build the "q" query parameter.
  • Social Media Solution Guide

    Social Media Solution Guide

    Social Media Solution Guide Deploy Social Messaging Server with an RSS Channel 9/30/2021 Deploy Social Messaging Server with an RSS Channel Deploy Social Messaging Server with an RSS Channel Contents • 1 Deploy Social Messaging Server with an RSS Channel • 1.1 Prepare the RSS Channel • 1.2 Configure the Options • 1.3 Interaction Attributes • 1.4 Next Steps Social Media Solution Guide 2 Deploy Social Messaging Server with an RSS Channel Warning The APIs and other features of social media sites may change with little warning. The information provided on this page was correct at the time of publication (22 February 2013). For an RSS channel, you need two installation packages: Social Messaging Server and Genesys Driver for Use with RSS. The Driver adds RSS-specific features to Social Messaging Server and does not require its own Application object in the Configuration Server database. You can also create a Custom Media Channel Driver. Important Unlike some other eServices components, Social Messaging Server does not require Java Environment and Libraries for eServices and UCS. Prepare the RSS Channel 1. Deploy Social Messaging Server. 2. Run the installation for Genesys Driver for Use with RSS, selecting the desired Social Messaging Server object: Social Media Solution Guide 3 Deploy Social Messaging Server with an RSS Channel Select your Social Messaging Server Object 3. Locate the driver-for-rss-options.cfg configuration file in the \<Social Messaging Server application>\media-channel-drivers\channel-rss directory. 4. In Configuration Manager, open your Social Messaging Server Application, go to the Options tab, and import driver-for-rss-options.cfg.
  • Wrangling Messy CSV Files by Detecting Row and Type Patterns

    Wrangling Messy CSV Files by Detecting Row and Type Patterns

    Wrangling Messy CSV Files by Detecting Row and Type Patterns Gerrit J.J. van den Burg1, Alfredo Nazábal1, and Charles Sutton1,2,3 1The Alan Turing Institute, London, UK 2Google, Inc. Mountain View, CA, USA 3School of Informatics, The University of Edinburgh, UK November 29, 2018 Abstract It is well known that data scientists spend the majority of their time on preparing data for analysis. One of the first steps in this preparation phase is to load the data from the raw storage format. Comma-separated value (CSV) files are a popular format for tabular data due to their simplicity and ostensible ease of use. However, formatting standards for CSV files are not followed consistently, so each file requires manual inspection and potentially repair before the data can be loaded, an enormous waste of human effort for a task that should be one of the simplest parts of data science. The first and most essential step in retrieving data from CSV files is deciding on the dialect of the file, such as the cell delimiter and quote character. Existing dialect detection approaches are few and non-robust. In this paper, we propose a dialect detection method based on a novel measure of data consistency of parsed data files. Our method achieves 97% overall accuracy on a large corpus of real- world CSV files and improves the accuracy on messy CSV files by almost 22% compared to existing approaches, including those in the Python standard library. Keywords — Data Wrangling, Data Parsing, Comma Separated Values arXiv:1811.11242v1 [cs.DB] 27 Nov 2018 1 CSV is a textbook example of how not to design a textual file format.
  • An Introduction to Georss: a Standards Based Approach for Geo-Enabling RSS Feeds

    An Introduction to Georss: a Standards Based Approach for Geo-Enabling RSS Feeds

    Open Geospatial Consortium Inc. Date: 2006-07-19 Reference number of this document: OGC 06-050r3 Version: 1.0.0 Category: OpenGIS® White Paper Editors: Carl Reed OGC White Paper An Introduction to GeoRSS: A Standards Based Approach for Geo-enabling RSS feeds. Warning This document is not an OGC Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting do Document type: OpenGIS® White Paper Document subtype: White Paper Document stage: APPROVED Document language: English OGC 06-050r3 Contents Page i. Preface – Executive Summary........................................................................................ iv ii. Submitting organizations............................................................................................... iv iii. GeoRSS White Paper and OGC contact points............................................................ iv iv. Future work.....................................................................................................................v Foreword........................................................................................................................... vi Introduction...................................................................................................................... vii 1 Scope.................................................................................................................................1