(IJCSIS) International Journal of Computer Science and Information Security,Vol. 8, No. 9 December, 2010
extension of the file of RSS version 1.0 is preferable to be(.rdf). Care should be taken here because RSS will bediscussed in the scope of RDF; RSS 0.9 and 1.0 is the onlyspecification standard of RSS that uses RDF vocabularies theother specification (RSS 0.91, 0.92, 0.93, 0.94, and 2.0) doesnot [1, 16]; they are more basic XML implementation. Its fileuses mainly the following two namespaces as two attributeswithin <rdf:RDF> tag:
•
xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#
•
xmlns=http://purl.org/rss/1.0
/
A.
The anatomy Of RSS file
Each RSS file consists of a single channel thatcontains the information gathered from many different sites; itis represented by the <channel> element. The attributerdf:about is used with in <channel> tag to describe the locationand the name of the RSS file
.
Some required tags within the channel element can beused to describe the channel itself such as
•
<title> element to describe the title of the channel.
•
<link> element to describe the URL of the parent siteor the news page.
•
<description> element to provide a brief descriptionof the channel contents, function, etc.As shown in figure.1; the channel contains number of items (<items>) listed in an ordered collection described by theRDF container <rdf:seq>. The items listed in the channel willbe described outside the channel after the closing </channel>tag using the above <title>, <link> and<description> tags. Thefollowing block diagram illustrates the anatomy of the RSSfile.
Figure.1 Anatomy of RSS File
B.
The relationship of RSS to RDF
Earlier
versions of RSS did not include any RDFvocabularies; it is just a syntactic XML representation of thepublished news. Although XML is a universal Meta languagefor defining Markup [7]; it is worth mentioned that XML hassome deficits, for example it does not provide a satisfactorysemantics representation that is embedded in statements; thereis no standard way exists to assign meaning to the nesting of the XML elements.Expressing the RSS 1.0 in a language described inRDF concepts and abstract syntax makes it conforms toRDF/XML syntax specification that has a precise formalsemantic defined in RDF semantics; thus easy interoperabilitywith other RDF Languages and obviously can be read andprocessed by machines [13].The foundation of RSS 1.0 serves the purpose of this paperthat intends to extend the RSS 1.0 to be used outside of strictnews and announcements syndication by focusing on a genericmeans of structured metadata exchanging [4] and how it canincorporate with other RDF ontologies by providing a simplemodular extension mechanism to accommodate newvocabularies.III.
SYSTEM ARCHITECTURE
The main purpose of the proposed architecture is to extendthe RSS data gathered from different resources to exceed justsyndication purpose by making an ontology that can interactwith other ontologies to have a tight and well-defined metadataabout the news and announcements. It will make acollaborative space that makes everything is linked.Classification operation can be done as well as many questionscan be answered.The framework presented in this research can beconsidered as integrated semantic web architecture. The word“integrated” refers to that this architecture consists of morethan one component, each one has a specific task, and the word“semantic” means that, this architecture is based on semanticweb technologies to make the presented ontology.Figure.2 shows the schematic diagram for this architecture
Identify applicable sponsor/s here.
(sponsors)
RDF declaration and used namespacesChannelList of items
•
Item1
•
Item2
•
Item3
•
..
•
Item nDescription of each Item in the channelRDF file closingPresentationInf. request
DBXML
Semi structured dataGenerator
RDF storage/ Query Engine
RDF/XMLRDF QueryInference
Data request
QueryCompositionPresentationbrowsing
UIOWLApplication LayerExtending andInference LayerRDF LayerSource and Storage Layer
Other ontologies
Rules
Reasoner
RSS files (Structured data)RSSOntology
API
Figure.2 The schematic diagram of the architectureUnstructured data
204http://sites.google.com/site/ijcsis/ISSN 1947-5500