RSS 3.0: The Future of Content Syndication

RSS is a technology that has significantly influenced the way people access and consume information on the web. At its core, RSS is a content syndication format that enables users to receive updates from their preferred websites in an easy and automated manner. This is essentially a news alert service. The importance of RSS lies in its ability to provide quick and organized access to online information, allowing users to stay informed about publications and other relevant content without having to manually visit each website. Moreover, RSS enables greater informational freedom, as users choose which websites and information sources they wish to follow, without depending on recommendation algorithms or social networks, which apply filters and biases that risk informational manipulation, reducing users to passivity. It could be said that the potential of RSS resides in the simplicity of its system (which is open source), with open standards that facilitate its implementation on any online publishing platform. However, the rise of social networks and the deliberate shutdown of the Google Reader service (the primary content aggregation service) triggered a shift in how we consume online information, thereby affecting freedom of choice on the web and limiting and transforming users’ informational options.

The history of RSS dates back to the late 1990s, when Dave Winer, one of the pioneers of the blogosphere (the collective community of Internet blogs), created the RSS 0.9 format as a means to allow users to syndicate (subscribe to) and receive updates from blogs. As blogs grew in popularity, the demand for a standardized syndication solution increased, leading to the creation of the RSS 2.0 specification in 2002.

At its peak, RSS was widely used by blogs, news sites, and other online media. However, with the emergence of social networks and recommendation algorithms, RSS lost popularity and ceased to be as widely used as before. Although RSS was a simple system, the lack of development around aggregation software, readers, and filtering methods, combined with difficulties in monetization and the implementation of a social layer, prevented it from competing on equal terms with emerging technologies. Even in the early stages of social networks, RSS was introduced to track user posts, though it remained a controversial feature due to privacy concerns, leading to its eventual removal. Nevertheless, the need to monitor social media content has spurred the development of RSS solutions to convert their content into syndication feeds, demonstrating a latent demand despite corporate policies that largely contributed to the stagnation of syndication technology.

Despite its decline, RSS remains an important technology if one values reclaiming the independence and freedom of information. Its ability to organize and provide automated access to relevant content continues to be a valuable feature for most users, only hindered by the lack of suitable and stable software over time.

The RSS 2.0 Format

RSS 2.0 is a content syndication format designed for the distribution of information on the web. It enables website publishers to share and update content such as news, articles, blogs, and other types of information in a manner easily readable by content aggregators and feed readers. The format is based on an XML structure with a set of predefined tags that allow the representation of various types of information within an RSS 2.0 document. These tags include elements such as title, description, publication date, author, and a permanent link to the original source. Although the structure is simple, it can be extended through the extensibility property inherent in XML-based formats by incorporating tags from other standards such as Dublin Core, MARC-XML, MADS, MODS, EAD, among others. This enables the description of documents and multimedia files, making it significantly more versatile. It is important to note that the simplicity of RSS specifications aims to ensure compatibility across different systems and applications. Thus, the information contained in a syndication feed can be easily read and interpreted by any reader or aggregator, allowing any website or content platform to implement it.

<?xml version="1.0" encoding="UTF-8"?>

<title>Channel Title</title>

<description>Channel Description</description>

<language>Channel Language</language>

<copyright>Channel Copyright</copyright>

<managingEditor>Channel Editor</managingEditor>

<webMaster>Channel Web Master</webMaster>

<pubDate>Channel Publication Date</pubDate>

<lastBuildDate>Channel Last Build Date</lastBuildDate>

<category>Channel category</category>

<generator>Channel generator</generator>

<docs>Channel documentation</docs>

<ttl>Channel TTL</ttl>

<item>

<title>Item title</title>

<description>Item description</description>

<author>Item author</author>

<category>Item category</category>

<comments>Item comments</comments>

<guid isPermaLink="Indicates whether the GUID is a permanent link">GUID value</guid>

<pubDate>Item publication date</pubDate>

</item>

</channel>

</rss>

Table 1. XML tag structure of an RSS 2.0 format

This code shows the complete set of tags for the RSS 2.0 format, as specified in the official standards of the Harvard Law School and the RSS Advisory Board. Note that the RSS channel consists of the <channel> element, which contains the tags describing the channel itself, as well as the <item> elements corresponding to the content blocks, news items, or documents to be reflected in the channel. The channel code is updated with new content published on the associated website. Thus, any new entry or information from the web is reflected in the syndication channel, triggering an informational alert for all users subscribed to the channel.

Improvements to the RSS Format

Integration of blockchain technology to ensure the immutability and authenticity of information. A true implementation of blockchain using the RSS structure as a foundation would enable users to verify the authenticity of data and content hosted on the RSS feed, significantly enhancing its integrity and security. This enhancement could also include advanced blockchain functionalities, such as the creation of smart contracts to automate specific actions in response to predefined events within the RSS feed. Additionally, a function for decentralized validation of RSS data using blockchain nodes could be introduced, allowing users to verify the authenticity of news, content, and files without relying on a single centralized source. Feeds with a larger number of subscribers would, in such a scenario, possess a more extensive network of nodes; if linked to a cryptocurrency, this could serve as a payment mechanism for the creative efforts of authors whose sources feed into the RSS channel, thereby establishing a proportional reward system based on actual reader consumption and demand.
Implementation of semantic tags to enhance the description and classification of content. Currently, RSS 2.0 already supports extensions for including metadata. However, the inclusion of semantic metadata can significantly improve the quality of the information transmitted. It would enable a better understanding of the data being conveyed and facilitate the integration of information from multiple sources. The use of standardized metadata formats, such as RDF (Resource Description Framework) or JSON-LD (JSON for Linking Data), could allow for the integration of data from diverse sources, the identification of the most relevant information, and the creation of customized feeds (also known as syndication channels) tailored to users’ needs. Furthermore, the incorporation of semantic metadata could help reduce reliance on recommendation algorithms and social networks for accessing information, empowering users to make more informed and critical decisions.
Add support for multimedia files, including live streams. This would enable users subscribed to a feed channel to receive and play multimedia content directly within their content aggregators. To achieve this, a new tag could be incorporated into the RSS format to allow the inclusion of links to multimedia content, whether in standard formats (e.g., MP3 or MP4) or live streaming formats such as RTMP or HLS. Additionally, it would be beneficial to permit customization of video formats and resolutions, as well as the addition of subtitles and audio descriptions to enhance the accessibility of multimedia content.
Implement authentication and authorization methods to ensure user privacy and security. Users often must trust that the RSS aggregation provider will not share their personal information or use it for malicious purposes. A potential solution to this issue is the implementation of authentication and authorization methods in RSS. For instance, users could be required to authenticate with a username and password before accessing their RSS feed. Users could also be allowed to define what information they wish to share with RSS aggregators and how that information should be used. Another way to enhance the security and privacy of RSS would be to employ authentication and authorization methods based on emerging technologies such as public-key cryptography and multi-factor authentication. In this manner, user privacy and security could be guaranteed without compromising the convenience and usability of RSS.
Provide support for real-time data sources, such as sensors and IoT devices. Many Internet of Things (IoT) devices generate large volumes of real-time data, and it is essential to be able to access and utilize this data efficiently and effectively. To address this need, new specific tags and elements could be added to describe sensor and IoT device data that could automatically publish content via an RSS feed, including aspects such as geographic location, sampling frequency, and sensor type.
Include advanced customization options to enable users to tailor their reading experience according to their needs and preferences. One approach to implementing this improvement would be to provide a customizable user interface, the ability to add search widgets, annotation and favorite content selection tools, personalized notifications for email or mobile devices, support for adding annotations to content, enabling text highlighting, facilitating micro-scraping, and other productive utilities.
Add support for indexing and searching content within the RSS file. Currently, users must manually review channels to find the information they desire, which can be tedious and time-consuming. By adding support for indexing and searching content within the RSS file, users could perform searches directly within the file to locate specific information rather than manually reviewing the entire file. This could enhance efficiency and user experience when using RSS. To implement this improvement, a search engine could be employed to crawl and store data in a search index.
Improve accessibility for users with visual and hearing impairments through the integration of audio descriptions and subtitles. These advanced accessibility features could be optional, allowing users to choose whether or not to enable them. Additionally, compatibility with assistive technologies, such as screen readers and other support tools, should be ensured to provide a fully accessible experience.
Promote interoperability with other web systems and standards, enabling the integration and synchronization of content across different platforms and applications. This involves compatibility with JSON, RDF, and microformats, so that RSS channel information can be processed by other applications and reused for additional tasks and functions.

RSS 3.0 Format: A Proposal

In this section, we present an initial draft proposal, by no means definitive, but intended to provide a foundation upon which to build, refine, and develop a future RSS 3.0 format. While it is true that a new format should entail a rethinking of existing tags and the introduction of new ones, Table 2 below leverages XML's extensibility property by incorporating Dublin Core tags, which offer enhanced descriptive capabilities, as well as blockchain-specific tags.

<?xml version="1.0" encoding="UTF-8"?>

<title>Channel Title</title>

<description>Channel Description</description>

<language>Channel Language</language>

<copyright>Channel Copyright</copyright>

<managingEditor>Channel Editor</managingEditor>

<webMaster>Channel Web Master</webMaster>

<pubDate>Channel Publication Date</pubDate>

<lastBuildDate>Channel Last Build Date</lastBuildDate>

<category>Channel category</category>

<generator>Channel generator</generator>

<docs>Channel documentation</docs>

<ttl>Channel TTL</ttl>

<item>

<title>Item title</title>

<description>Item description</description>

<author>Item author</author>

<category>Item category</category>

<comments>Item comments</comments>

<guid isPermaLink="Indicates whether the GUID is a permanent link">GUID value</guid>

<pubDate>Item publication date</pubDate>

<dc:contributor>Author name</dc:contributor>

<dc:coverage>Location where the news occurred</dc:coverage>

<dc:date>2022-12-31T23:59:59Z</dc:date>

<dc:description>Detailed description of news item 1</dc:description>

<dc:format>text/html</dc:format>

<dc:identifier>https://www.midominio.com/noticia1</dc:identifier>

<dc:language>es</dc:language>

<dc:publisher>Publication name</dc:publisher>

<dc:relation>Relation to other news items</dc:relation>

<dc:rights>Copyright of the news item</dc:rights>

<dc:source>Source of the news item</dc:source>

<dc:subject>Topic of the news item</dc:subject>

<dc:title>News Item 1</dc:title>

<dc:type>Type of news item</dc:type>

<hash>0x9ffjd939393jdfdf93jdfdfj39393jfjdfj3</hash>

<minerAddress>0x9d9jd93939jdfj93jdfjdfj93jdfj9j3</minerAddress>

<data>{

"title": "News 1",

"link": "https://www.midominio.com/news/news1",

"description": "Brief description of news 1"

}</data>

</transaction>

</transactions>

</item>

</channel>

</rss>

Table 2. XML tag structure of a hypothetical RSS 3.0 format

Regarding Dublin Core tags, the complete basic set is observed, allowing specification of format, title, description, identifier, source, publisher, link to related news, rights, subject, and type. It would be advisable to consider integrating these tags as native elements in a hypothetical RSS 3.0 specification, thereby simplifying metadata naming without requiring a Dublin Core extension, enhancing richness and complexity to achieve greater descriptive exhaustiveness. This procedure should be based on the principle of a common denominator for objects that could be registered in a new RSS 3.0 format—for example, news articles, scientific papers, micro-publications, multimedia, office files, periodic data streams for self-publishing, etc.

On the other hand, the blockchain aspect is reflected, as it would appear in a real blockchain log, with key labels such as the block identifier <blockNumber><hash> and <previousHash> that enable chaining blocks or content to be registered via their keys. Furthermore, if one wishes to implement a system of rewards based on interest, reads, and subscriptions, it is necessary to link the RSS blockchain to a mining and cryptocurrency system that captures the difficulty of the mathematical problem to be solved, the target, and the miner of the node network responsible for resolving said problem. However, unlike other cryptocurrency cases, the fixation of content should coincide with the publication date of the content at the moment the platform author decides to make it public. To accommodate this, the system can be designed to grant mining rewards prior to data registration, maintaining a pool of miners queued to perform the registration of transactions and content precisely at the moment the content creator publishes their entries. In this way, immediacy in the process could be ensured. Another possibility would be to reduce the difficulty of the cryptocurrency’s mathematical problems, in order to guarantee a rapid response time from miners, functioning as other crypto systems typically do. In any case, it appears fundamental that the blockchain system be simplified as much as possible to preserve the simplicity that characterizes the RSS format.

An Aggregator for RSS 3.0

Content aggregators are programs that allow users to subscribe to any syndication feed, store its content, read it, receive information alerts, apply filters, and facilitate information retrieval. It is therefore essential that, alongside the RSS 3.0 content syndication format, such programs and open-source code be provided to maximize their utility. In this regard, it seems advisable to offer pre-built code in major programming languages such as PHP and Python, enabling developers to integrate them into their creations and internet-based content creation and publishing platforms. Furthermore, it is indispensable to provide users with an aggregation program that can be installed on mobile devices, desktop environments, and web servers, incorporating all the expected functionalities of the new RSS 3.0 version. These aggregators should also operate as nodes in the RSS blockchain network, implying their participation in the transactional network.

Focusing on the technical aspect of retrieving content from an RSS 3.0 feed, the code used by aggregators would not differ significantly from that of aggregators for earlier versions. Table 3 presents two options for collecting <item> content within a syndication channel, which we can consider the core of the aggregation program. The SimpleXMLElement and cURL function libraries can still be employed, yielding identical results.

<?php

// Option 1 - SimpleXMLElement Parser

// =======================================================

$rss = new SimpleXMLElement(file_get_contents('rss.xml'));

foreach ($rss->channel->item as $item) {

$title = $item->title;

$description = $item->description;

$link = $item->link;

$timestamp = $item->timestamp;

$hash = $item->hash;

$previousHash = $item->previousHash;

$nonce = $item->nonce;

$difficulty = $item->difficulty;

$transactions = $item->transactions->transaction->data;

$minerAddress = $item->minerAddress;

$contributor = $item->children('dc', true)->contributor;

$coverage = $item->children('dc', true)->coverage;

$date = $item->children('dc', true)->date;

$dcDescription = $item->children('dc', true)->description;

$format = $item->children('dc', true)->format;

$identifier = $item->children('dc', true)->identifier;

$language = $item->children('dc', true)->language;

$publisher = $item->children('dc', true)->publisher;

$relation = $item->children('dc', true)->relation;

$rights = $item->children('dc', true)->rights;

$source = $item->children('dc', true)->source;

$subject = $item->children('dc', true)->subject;

}

// Option 2 - cURL Parser

// =======================================================

$url = 'rss.xml';

$ch = curl_init();

curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);

curl_setopt($ch, CURLOPT_URL, $url);

$data = curl_exec($ch);

curl_close($ch);

$doc = new DOMDocument();

$doc->loadXML($data);

$items = $doc->getElementsByTagName('item');

foreach ($items as $item) {

$title = $item->getElementsByTagName('title')->item(0)->nodeValue;

$description = $item->getElementsByTagName('description')->item(0)->nodeValue;

$link = $item->getElementsByTagName('link')->item(0)->nodeValue;

$timestamp = $item->getElementsByTagName('timestamp')->item(0)->nodeValue;

$hash = $item->getElementsByTagName('hash')->item(0)->nodeValue;

$previousHash = $item->getElementsByTagName('previousHash')->item(0)->nodeValue;

$nonce = $item->getElementsByTagName('nonce')->item(0)->nodeValue;

$difficulty = $item->getElementsByTagName('difficulty')->item(0)->nodeValue;

$transactions = $item->getElementsByTagName('transaction')->item(0)->nodeValue;

$minerAddress = $item->getElementsByTagName('minerAddress')->item(0)->nodeValue;

$contributor = $item->getElementsByTagName('dc:contributor')->item(0)->nodeValue;

$coverage = $item->getElementsByTagName('dc:coverage')->item(0)->nodeValue;

$date = $item->getElementsByTagName('dc:date')->item(0)->nodeValue;

$dcDescription = $item->getElementsByTagName('dc:description')->item(0)->nodeValue;

$format = $item->getElementsByTagName('dc:format')->item(0)->nodeValue;

$identifier = $item->getElementsByTagName('dc:identifier')->item(0)->nodeValue;

$language = $item->getElementsByTagName('dc:language')->item(0)->nodeValue;

$publisher = $item->getElementsByTagName('dc:publisher')->item(0)->nodeValue;

$relation = $item->getElementsByTagName('dc:relation')->item(0)->nodeValue;

$rights = $item->getElementsByTagName('dc:rights')->item(0)->nodeValue;

$source = $item->getElementsByTagName('dc:source')->item(0)->nodeValue;

$subject= $item->getElementsByTagName('dc:subject')->item(0)->nodeValue;

$title = $item->getElementsByTagName('dc:title')->item(0)->nodeValue;

$type = $item->getElementsByTagName('dc:type')->item(0)->nodeValue;

}

Table 3. Two examples of RSS 3.0 parsers with PHP, using the cURL and SimpleXMLElement techniques

On the other hand, the addition related to blockchain, and specifically to the <transaction> tags for transactions, requires a secondary foreach loop that iterates through all the annotations in the transaction array of the RSS remuneration system; see the tentative example in Table 4.

<?php

$url = 'https://example.com/rss.xml';

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, $url);

curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);

$data = curl_exec($ch);

curl_close($ch);

$dom = new DOMDocument();

$dom->loadXML($data);

$items = $dom->getElementsByTagName('item');

$transactions = array();

foreach ($items as $item) {

$transactionsNode = $item->getElementsByTagName('transactions')->item(0);

$transactionsList = $transactionsNode->getElementsByTagName('transaction');

foreach ($transactionsList as $transaction) {

$transactions[] = array(

'hash' => $transaction->getElementsByTagName('hash')->item(0)->nodeValue,

'previousHash' => $transaction->getElementsByTagName('previousHash')->item(0)->nodeValue

);

}

$subject = $item->getElementsByTagName('dc:subject')->item(0)->nodeValue;

$title = $item->getElementsByTagName('dc:title')->item(0)->nodeValue;

$type = $item->getElementsByTagName('dc:type')->item(0)->nodeValue;

}

Table 4. PHP procedure for the recursive extraction of items and transactions from a blockchain on an RSS 3.0 channel

Conclusions and Future Developments

The evolution of web standards is fundamental to the adaptation and continuous improvement of technology. RSS has been an important standard for content syndication, but its lack of updates demonstrates the need for a new version, such as RSS 3.0, that addresses current deficiencies and challenges, such as the integration of blockchain, indexing and retrieval systems, accessibility, or personalization.
User privacy and security are increasingly important issues in the digital age. By incorporating authentication and authorization methods, RSS 3.0 could enhance user data confidentiality, which is crucial for protecting users' rights and privacy.
Internet users have diverse needs and preferences, so advanced customization options in RSS 3.0 would be essential to meet the varied requirements of users. This would also enhance the user experience and increase user engagement and loyalty. These objectives require the development of better content aggregators and the release of the necessary source code to facilitate the creation of plugins and modules for web publishing systems. Parser/aggregators play a key role in the functioning of RSS and can be improved to provide users with a more advanced and personalized reading experience.
The ability to aggregate and display multiple RSS channels within a single user interface is a useful feature that would enable users to manage and view their content more effectively. This would also promote interoperability between different systems and applications, thereby improving content management efficiency and the overall user experience.

Bibliography

Arnepalli, K.; Rao, K.S. (2021). Blockchain Technology: Possibility of Application for Library Networks in India. Pearl: A Journal of Library and Information Science, 15(3), 153-161. http://dx.doi.org/10.5958/0975-6922.2021.00017.6
Babu, P.R. (2020). Measuring Research in RSS Feed Literature: A Scientometric Study. In Measuring and Implementing Altmetrics in Library and Information Science Research (pp. 74-86). IGI Global. http://dx.doi.org/10.4018/978-1-7998-1309-5.ch008
Barman, B. (2020). Changing the Ways the Libraries Reach to the User: RSS and its Applications in Libraries with Special Reference to Feedburner. Library Philosophy and Practicehttps://digitalcommons.unl.edu/libphilprac/3832
Cammack, R.G. (2007). Open content Web mapping service: a Really Simple Syndication (RSS) approach. Location Based Services and TeleCartographyhttps://doi.org/10.1007/978-3-540-36728-4_30
Chabini, M.; Sabiri, K.; Aaroud, A.; Akodadi, K. (2022). Fighting Fake News Propagation Using Blockchain in Journalism: A Systematic Literature Review. In International Conference on Digital Technologies and Applications (pp. 241-255). Springer, Cham. https://doi.org/10.1007/978-3-031-01942-5_24
Creus Tomàs, J.; Amann, B.; Travers, N.; Vodislav, D. (2011). RoSeS: A continuous content-based query engine for RSS feeds. In Database and Expert Systems Applications: 22nd International Conference, DEXA 2011, Toulouse, France, August 29-September 2, 2011, Proceedings, Part II 22 (pp. 203-218). Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-642-23091-2_19
Dabbagh, M.; Sookhak, M.; Safa, N.S. (2019). The evolution of blockchain: A bibliometric study. IEEE Access, 7, 19212-19221. https://doi.org/10.1109/ACCESS.2019.2895646
Frederick, D.E. (2019). Blockchain, libraries and the data deluge. Library Hi Tech News, 36(10), 1-7. https://doi.org/10.1108/LHTN-09-2019-0059
Goldsborough, R. (2007). Keeping up with really simple syndication (RSS). Teacher Librarian, 34(3), 51. https://yorkspace.library.yorku.ca/xmlui/bitstream/handle/10315/2548/RSS_Nariani.pdf
Hammersley, B. (2003). Content syndication with RSS. O’Reilly Media. http://ommolketab.ir/aaf-lib/etjpcc1ogme36te7qj0wwauc2bo7cq.pdf
Hammond, T.; Hannay, T.; Lund, B. (2004). The role of RSS in science publishing. D-Lib Magazine, 10(12), 1082-9873. http://dlib.org/dlib/december04/hammond/12hammond.html
Hofman, D.; Novin, A. (2018). Blocked and chained: Blockchain and the problems of transparency. Proceedings of the Association for Information Science and Technology, 55(1), 171-178. https://doi.org/10.1002/pra2.2018.14505501019
Kelly, B. (2005). RSS–more than just news feeds. New Review of Information Networking, 11(02), 219-227. https://doi.org/10.1080/13614570600573425
Lee, M.J.; Miller, C.; Newnham, L. (2008). RSS and content syndication in higher education: subscribing to a new model of teaching and learning. Educational Media International, 45(4), 311-322. https://doi.org/10.1080/09523980802573255
Mahboob, K.; Ali, F.; Nizami, H. (2019). Sentiment analysis of RSS feeds on sports news–a case study. International Journal of Information Technology and Computer Science, 11(12), 19-29. http://dx.doi.org/10.5815/ijitcs.2019.12.02
Marche, C.; Cabiddu, I.; Castangia, C.G.; Serreli, L.; Nitti, M. (2022, September). Fake News Detection based on Blockchain Technology. In 2022 IEEE 33rd Annual International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC) (pp. 654-659). IEEE. https://doi.org/10.1109/PIMRC54779.2022.9978074
Miah, M.; Miah, S.J.; Venkatraman, S. (2021). Blockchain: At a glance idea for information science researchers. Journal of Information and Optimization Sciences, 42(7), 1589-1624. https://doi.org/10.1080/02522667.2021.1930644
Mohammed, A.J.; Husni, H. (2012). Blogs Search Engine Using RSS Syndication and Fuzzy Parameters. UACEE International Journal of Computer Science and its Applications, 2(3). http://dx.doi.org/10.3850/978-981-07-2969-1_PCT-145
Ochoa, I.S.; de Mello, G.; Silva, L.A.; Gomes, A.J.; Fernandes, A.M.; Leithardt, V.R.Q. (2019). Fakechain: A blockchain architecture to ensure trust in social media networks. In Quality of Information and Communications Technology: 12th International Conference, QUATIC 2019, Ciudad Real, Spain, September 11–13, 2019, Proceedings 12 (pp. 105–118). Springer International Publishing. https://doi.org/10.1007/978-3-030-29238-6_8
O’Shea, M.; Levene, M. (2011). Mining and visualising information from RSS feeds: a case study. International Journal of Web Information Systems. https://doi.org/10.1108/17440081111141763
Safdar, M.; Qutab, S.; Ullah, F.S.; Siddique, N.; Khan, M.A. (2022). A mapping review of literature on Blockchain usage by libraries: Challenges and opportunities. Journal of Librarianship and Information Sciencehttps://doi.org/10.1177/09610006221090225
Seneviratne, O. (2022, June). Blockchain for Social Good: Combating Misinformation on the Web with AI and Blockchain. In 14th ACM Web Science Conference 2022 (pp. 435–442). https://doi.org/10.1145/3501247.3539016
Shae, Z.; Tsai, J. (2019, July). AI blockchain platform for trusting news. In 2019 IEEE 39th International Conference on Distributed Computing Systems (ICDCS) (pp. 1610-1619). IEEE. https://doi.org/10.1109/ICDCS.2019.00160
Shang, W., Liu, M., Lin, W., & Jia, M. (2018, June). Tracing the source of news based on blockchain. In 2018 IEEE/ACIS 17th International Conference on Computer and Information Science (ICIS) (pp. 377-381). IEEE. https://doi.org/10.1109/ICIS.2018.8466516
Stolz, A.; Hepp, M. (2013, May). From RDF to RSS and Atom: content syndication with linked data. In Proceedings of the 24th ACM Conference on Hypertext and Social Media (pp. 236-241). https://doi.org/10.1145/2481492.2481523