DOCSLIB.ORG

HTML and CSS Overview of the WWW

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HTML and CSS Overview of the WWW HTML and CSS Overview of the WWW • Internet • 1969 - ARPANET • Global interconnected network of computer networks • WWW • NSFNET removes restriction on commercial use of Internet • Tim Berners-Lee at CERN created WWW as a way to hyperlink to documents to view them; used: • HTML (HyperText Markup Language) • HTTP (HyperText Transfer Protocol) • URLs (uniform resource locator) • Mosaic becomes available Overview of the WWW (cont) • Client/Server Model • Describes relationship between two computer programs • Client requests a service • E.g., Web browser requests Web page using HTTP and URL • Server fulfills the request • E.g., Web server sends the Web page file • Client and server usually reside on different computers Overview of the WWW (cont) • URL • Specifies a Web page address • Basic form: how://where/what • how - protocol • where – domain name of the computer • what – local name of file including the path to it (name can be omitted if it is index.html) • Example: http://cs.unh.edu/~sna4/408/index.html | | | | | protocol | folder | file name domain name of Web server sub-folder Overview of the WWW (cont) • Domain names • Locates an organization or other entity on the Internet • DNS (Domain Name System) • Divides the Internet into logical groups • Associates domain names with unique IP address • TLDs – Top-Level Domain Names • Right most part of the domain name • Either generic or country code • Generic examples: .com, .mil, .org, .name, .gov • Country code examples: .au, .de, .in, .jp, .nl, .us, eu Overview of the WWW (cont) • IP addresses • Each device on the Internet is assigned an IP address • IPv4 allowed for at most 4 billion possible IP address • Not enough with proliferation of mobile devices • IPv6 is most recent version of the Internet Protocol • IP address is lengthened from 32 bits to 128 bits (4 bytes to 16 bytes) • 2128 possible unique addresses available HTML • HyperText Markup Language • Started in early 90s, version number increased as language evolved • Simple, text-based mark-up language • Describes meaning of the content • Paragraphs, headings, lists, etc. • Works with CSS (Cascading Style Sheets) HTML (cont.) • CSS (cont.) • Defines how your content and Web page will look • Created in 1996 (after HTML) • Progressive Enhancement • Info on WWW should be accessible to all • Describe content with HTML - accessible to all • Add design with CSS • Viewable with old browsers, mobile devices, screen readers, etc. Web Page Building Blocks Web page consists of three components: 1.Text content 2.References to other files E.g., image files, audio, video, links to other pages, style sheets 3.Markup • HTML elements that describe text content • Does not define how content should appear in browser • Browser has built-in CSS file (aka style sheet) that specifies how each HTML element displays by default Basic HTML Page <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <title>Hello HTML</title> </head> <body> <p>Hello World!</p> </body> </html> Basic HTML • HTML tags do not appear in the browser • Always use HTML5’s DOCTYPE declaration • Code above the <body> is info for browsers and search engines – not visible except for title • Text in title: <title> …</title> appears at top of browser • Default name of browser bookmark • Valuable info for search engine Basic HTML (cont.) • Page’s content goes between <body> … </body> -- this part is visible to users • </html> signals the end of the page • Lines in example are separated with carriage return – this just makes the code easy to read Semantic HTML • Markup describes the meaning of the content, does not define how the content should appear (CSS does that) • Before HTML5 there were block-level and inline elements; now inline = phrasing content • Why semantics matter: • Improved accessibility • Improved SEO • Lighter code and faster pages • Easier code maintenance and styling Markup: Elements, Attributes, and Values • There are 3 principle markup components: • Elements - can contain text or they can be empty and describe the different parts of the Web page: • I am <em>happy</em> to be here! • <img src=“mypic.jpg” width = “110” height = “160” alt = “Picture of Sofia” /> • Attributes contain info about the content in the document <a href = “http://www.amazon.com”>Books</a> href is an attribute of a; http://www.amazon.com is the value for href Some Elements ● <p> … </p> paragraph ● <article> … </article> a distinct piece of content ● <h1> … </h1> heading level 1 (most important) ● … ● <h6> … </h6> heading level 6 (least important) ● <strong> … </strong> important text (usually the same as <b>, bold text) ● <em> … </em> stress emphasis (is usually the same as <i>, italicizing content) ● <a> … </a> link (phrasing content element) Parents and Children • If one element contains another, it is said to be the parent of the enclosed, or child, element: <p>I am <em>happy</em> to be here.</p> • Any elements contained in the child element are considered descendants of the outer, parent element. • Each element must be properly nested • Incorrect: <p>Hello <em>world</p>!</em> Text Content • White space collapses when rendered by browser • It is standard practice to encode pages in UTF-8 • Unicode is a superset of ASCII (American Standard Code for Information Interchange) • The document’s character encoding is specified right after the <head> tag using the charset attribute • Character references are replaced by the corresponding symbol; e.g., &copy; is © File Names • File names are case sensitive • Use .html extension • Suggestions: • No spaces in file names • Use lowercase to avoid confusion • Use – (dash) instead of _ (underscore) URLS • Absolute urls contain all three parts of the url: how://where/what • Relative urls are relative to the currently loaded page on the same server where/what (don’t need where if same directory) Use .. to point to a directory at a higher level of the file hierarchy (Ex: <a href=”../page.html”>) • Use relative when possible to make code portable HTML Tag - Comments <!-- comments go here --> • Provides a way to document your HTML code and make notes to yourself • Comments are not rendered by browser (you need to view the source code to see them) • You can place a comment anywhere in your HTML • Example: <!-- This page was created by Sofia Lemons 02/23/16 --> Note: Do not include embedded HTML code in the comment tag as this may produce unpredictable results HTML Tag - Paragraph <p> … </p> • Use the paragraph tag to break text into paragraphs • Enclose block of text with beginning and ending paragraph tags • Examples: <p>This is the title sentence for the first paragraph.</p> <p>This is the start of paragraph two.</p> <p>This is the third paragraph.</p> <p>This is the title sentence for the first paragraph.</p> <p>This is the start of paragraph two.</p> <p>This is the third paragraph.</p> • Note: In the examples, both will be rendered exactly the same by the Web browser but the source code for the second one is easier for us to write and read. HTML Tag – Line Break <br /> • The <br /> tag adds a line break but the browser does not add any vertical space • Notice the built-in ending tag • Example: <p>This is the title sentence <br /> for the first paragraph.</p> HTML Tag - Headings <h1>…</h1> etc. • Use heading tags to designate headings and sub- headings • Most browsers support a hierarchy of six levels of HTML headings where <h1> is the largest and <h6> is the smallest • Browsers will display the headings in bold with various sizes and spacing on separate lines • Example 1: <h6>Copyright Sofia Lemons, 2016. All rights reserved.</h6> • Example 2: <h1>Sofia’s Homepage for CS408</h1> <h1>Spring 2016</h1> HTML Tag - Image <img /> • Used to include in-line images • src (source) attribute is used to specify the URL of the image to be displayed • Either relative or absolute URL can be used to point to image file • 3 most common image file types have .gif, .jpg, or .png extensions • Other attributes are: • alt - an “alternative” text string that describes the image • height and width - the dimensions of the image in pixels • Importance of using the alt, height, and width attributes • Notice built-in end of tag! HTML Tag - <img /> (cont) Example 1: <img src = “IMAGES/mypicture.jpg” alt = “Picture of Me” height = “160” width = “120” /> uses a relative url Example 2: <img src = “http://pubpages.unh.edu/~sna4/408/ GRAPHICS/Fall12/sofia.jpg” alt = “Picture of Sofia” height = “160” width = “120” /> not recommended! Uses absolute url HTML Tag - Anchor <a> … </a> • Anchor tag is used to create hyperlinks • Three basic parts of a hyperlink: • Beginning and ending tag pair <a> … </a> • href (hypertext reference) attribute that specifies the URL of the page to be loaded when the hyperlink is selected • Text or graphic that appears on-screen as the active link Clickable Text Hyperlinks • Text is used as the “hot spot” for the link <a href = “mypage.html”>My Homepage</a> • Example 1: <a href = “mypage.html”>My Homepage</a> This uses a relative URL • Example 2: <a href = “http://www.usa.gov/documents/whitehouse.html”>Wh ite House</a> This uses an absolute URL Clickable Image Hyperlinks • An image is used as “hot spot” for link • Example: <a href = “http://www.usa.gov/wogulis/notready.html”> <img src = “wheelbarrow.gif” alt = “Under Construction” height = “50” width = “50” /></a> Mailto Hyperlinks • Provides a convenient way for someone viewing your Web page to send you e-mail • Example: <a href = “mailto:[email protected]”>Contact Sofia</a> A mail dialog
Load more

Recommended publications
  • HTML5 for .NET Developers by Jim Jackson II Ian Gilman
    S AMPLE CHAPTER Single page web apps, JavaScript, and semantic markup Jim Jackson II Ian Gilman FOREWORD BY Scott Hanselman MANNING HTML5 for .NET Developers by Jim Jackson II Ian Gilman Chapter 1 Copyright 2013 Manning Publications brief contents 1 ■ HTML5 and .NET 1 2 ■ A markup primer: classic HTML, semantic HTML, and CSS 33 3 ■ Audio and video controls 66 4 ■ Canvas 90 5 ■ The History API: Changing the game for MVC sites 118 6 ■ Geolocation and web mapping 147 7 ■ Web workers and drag and drop 185 8 ■ Websockets 214 9 ■ Local storage and state management 248 10 ■ Offline web applications 273 vii HTML5 and .NET This chapter covers ■ Understanding the scope of HTML5 ■ Touring the new features in HTML5 ■ Assessing where HTML5 fits in software projects ■ Learning what an HTML application is ■ Getting started with HTML applications in Visual Studio You’re really going to love HTML5. It’s like having a box of brand new toys in front of you when you have nothing else to do but play. Forget pushing the envelope; using HTML5 on the client and .NET on the server gives you the ability to create entirely new envelopes for executing applications inside browsers that just a few years ago would have been difficult to build even as desktop applications. The abil- ity to use the skills you already have to build robust and fault-tolerant .NET solu- tions for any browser anywhere gives you an advantage in the market that we hope to prove throughout this book. For instance, with HTML5, you can ■ Tap the new Geolocation API to locate your users anywhere
    [Show full text]
  • Weaving a Web of Linked Resources
    Semantic Web 8 (2017) 767–772 767 DOI 10.3233/SW-170284 IOS Press Editorial Weaving a Web of linked resources Fabien Gandon a,*, Marta Sabou b and Harald Sack c a Wimmics, Université Côte d’Azur, Inria, CNRS, I3S, Sophia Antipolis, France E-mail: [email protected] b CDL-Flex, Vienna University of Technology, Austria E-mail: [email protected] c FIZ Karlsruhe, Leibniz Institute for Information Infrastructure, KIT Karlsruhe, Germany E-mail: Harald.Sack@fiz-Karlsruhe.de Abstract. This editorial introduces the special issue based on the best papers from ESWC 2015. And since ESWC’15 marked 15 years of Semantic Web research, we extended this editorial to a position paper that reflects the path that we, as a community, traveled so far with the goal of transforming the Web of Pages to a Web of Resources. We discuss some of the key challenges, research topics and trends addressed by the Semantic Web community in its journey. We conclude that the symbiotic relation of our community with the Web requires a truly multidisciplinary research approach to support the Web’s diversity. Keywords: Semantic Web, trends, challenges 1. From a Web of pages to a Web of resources a first wave of deployment of the Semantic Web with the Linked Data principles and the Linked Open Data As we write this article Tim Berners-Lee just re- 5-Star rules [3] leading to the publication and growth ceived the Turing Award “for inventing the World of linked open datasets towards the Web of Data, as Wide Web, the first Web browser, and the fundamental depicted in Fig.
    [Show full text]
  • Microformats: Empowering Your Markup for Web 2.0
    Microformats: Empowering Your Markup for Web 2.0 John Allsopp Microformats: Empowering Your Markup for Web 2.0 Copyright © 2007 by John Allsopp All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-59059814-6 ISBN-10 (pbk): 1-59059-814-8 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013. Phone 1-800-SPRINGER, fax 201-348-4505, e-mail [email protected],or visit www.springeronline.com. For information on translations, please contact Apress directly at 2560 Ninth Street, Suite 219, Berkeley, CA 94710. Phone 510-549-5930, fax 510-549-5939, e-mail [email protected], or visit www.apress.com. The information in this book is distributed on an “as is” basis, without warranty. Although every precaution has been taken in the preparation of this work, neither the author(s) nor Apress shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this work.
    [Show full text]
  • Enhanced Semantic Web Layered Architecture Model
    NEW ASPECTS of APPLIED INFORMATICS, BIOMEDICAL ELECTRONICS & INFORMATICS and COMMUNICATIONS Enhanced Semantic Web Layered Architecture Model Islam H. Harb, Salah Abdel-Mageid, Hassan Farahat, M. S. Farag Comp. Sys. Engineer Comp. Sys. Engineer Comp. Sys. Engineer Math. Dept. Al-Azhar Univ. Al-Azhar Univ. Al-Azhar Univ. Al-Azhar Univ. Egypt. Egypt. Egypt. Egypt. [email protected], [email protected] [email protected] Abstract: - This paper introduces the traditional web and its limitations, and how these limitations can be overcome by putting the lights on a new interesting approach for the web which is the Semantic Web. The most common technologies that can be used to construct such smart web are discussed briefly, and then its current layered architecture models as proposed by Tim Berners-Lee and others are evaluated to alleviate discrepancies and weak points. An enhanced architecture obeying layered architecture evaluation criteria and standard principles is proposed. This enhanced model is evaluated and contrasted against other models. Key-Words: - Semantic web, ontology, XML, RDF, URI and Functional Layers. 1 Introduction the system engineering description and the layers integration. The Semantic Web may be considered as an This paper introduces an Enhanced Semantic Web evolution to this WWW which aims to make all the Layered Architecture Model. This enhanced model information and application data on the internet introduces a new architecture which follows the universally shared and machine processable in a very layered architecture as [12], [18]. This enhanced efficient way. It is an intelligent web which can proposed architecture alleviates the previous work understand the information semantics and services weak points.
    [Show full text]
  • Website Development and Web Standards in the Ubiquitous World: Where Are We Going?
    WSEAS TRANSACTIONS on COMPUTERS Serena Pastore Website development and web standards in the ubiquitous world: Where are we going? SERENA PASTORE INAF-Astronomical Observatory of Padova National Institute for Astrophisics (INAF) Vicolo Osservatorio 5 – 35122 - Padova ITALY [email protected] Abstract: - A website is actually the first indispensable tool for information dissemination, but its development embraces various aspects: the choice of Content Management System (CMS) to implement production and the publishing process, the provision of relationships and interconnections with social networks and public web services, and the reuse of information from other sources. Meanwhile, the context where web content is displayed has dramatically changed with the advent of mobile devices that are very different in terms of size and features, which have led to a ubiquitous world made of mobile Internet-connected devices. Users’ behavior on mobile web devices means that developers need new strategies for web design. The paper analyzes technologies, methods, and solutions that should be adopted to provide a good user experience regardless of the devices used to visualize the content in its various forms (i.e., web pages, web applications, widgets, social applications, and so on), assuring that open standards are adhered to, and thus providing wider accessibility to users. The strategies for website development cover responsive technology vs. mobile apps, the interconnection with social networks and web services in the Google world, the adoption
    [Show full text]
  • Representing Knowledge in the Semantic Web Oreste Signore W3C Office in Italy at CNR - Via G
    Representing Knowledge in the Semantic Web Oreste Signore W3C Office in Italy at CNR - via G. Moruzzi, 1 -56124 Pisa - (Italy) Phone: +39 050 315 2995 (office) e.mail: [email protected] home page: http://www.weblab.isti.cnr.it/people/oreste/ Abstract – The Web is an immense repository of data and knowledge. Semantic web technologies support semantic interoperability and machine-to-machine interaction. A significant role is played by ontologies, which can support reasoning. Generally much emphasis is given to retrieval, while users tend to browse by association. If data are semantically annotated, an appropriate intelligent user agent aware of the mental model and interests of the user can support her/him in finding the desired information. The whole process must be supported by a core ontology. 1. Introduction W3C leads the evolution of the Web. Universal Access and Semantic Web show a significant impact upon interoperability, technological as well as semantic. In this paper we will discuss the role played by XML to support interoperability within applications, while RDF helps in cross applications interoperability. Subsequently, the paper considers the metadata issue, with a brief description of RDF and the Semantic Web stack. Finally, we discuss an example in the area of cultural heritage, which is very rich in variety of possible associations, presenting an architecture where intelligent agents make use of core ontology to help users in finding the appropriate information. 2. The World Wide Web Consortium (W3C) The Wide Web Consortium (W3C) was created in October 1994 to lead the World Wide Web to its full potential by developing common protocols that promote its evolution and ensure its interoperability.
    [Show full text]
  • The Semantic
    The Fate of the Semantic Web Technology experts and stakeholders who participated in a recent survey believe online information will continue to be organized and made accessible in smarter and more useful ways in coming years, but there is stark dispute about whether the improvements will match the visionary ideals of those who are working to build the semantic web. Janna Quitney Anderson, Elon University Lee Rainie, Pew Research Center’s Internet & American Life Project May 4, 2010 Pew Research Center’s Internet & American Life Project An initiative of the Pew Research Center 1615 L St., NW – Suite 700 Washington, D.C. 20036 202‐419‐4500 | pewInternet.org This publication is part of a Pew Research Center series that captures people’s expectations for the future of the Internet, in the process presenting a snapshot of current attitudes. Find out more at: http://www.pewInternet.org/topics/Future‐of‐the‐Internet.aspx and http://www.imaginingtheinternet.org. 1 Overview Sir Tim Berners‐Lee, the inventor of the World Wide Web, has worked along with many others in the Internet community for more than a decade to achieve his next big dream: the semantic web. His vision is a web that allows software agents to carry out sophisticated tasks for users, making meaningful connections between bits of information so “computers can perform more of the tedious work involved in finding, combining, and acting upon information on the web.”1 The concept of the semantic web has been fluid and evolving and never quite found a concrete expression and easily‐understood application that could be grasped readily by ordinary Internet users.
    [Show full text]
  • Motivation, Possibilities, and Difficulties for Participating in the Semantic
    Motivation, Possibilities, and Difficulties for Participating in the Semantic Web Aning Rothe Professor: Prof. Dr. rer. nat. habil. Dr. h. c. Alexander Schill Supervisor: Dipl. -Inf. habil Marius Feldmann Department of Computer Science Institute for System Architecture TECHNISCHE UNIVERSITAT¨ DRESDEN July, 2008 APPROVAL Author: Aning Rothe Matrikel-Nr.: 2810396 Title: Motivation, Possibilities, and Difficulties for Participating in the Semantic Web Degree: Master of Science Examining Committee: Dated: A THESIS SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIRE- MENTS FOR THE DEGREE OF MASTER OF SCIENCE IN INSTITUTE FOR SYSTEM ARCHITECTURE TECHNISCHE UNIVERSITAT¨ DRESDEN The author reserves all rights. This work may not be reproduced in whole or in part without the author’s written permission. Permission is granted to Technische Universit¨at Dresden to make copies for non-commercial purposes. The author certifies that all works during this research has been completed by myself. Any copyrighted material that appeared in this work has been cited, and all external helps that I received in this research work have been clearly acknowl- edged. Signature of Author Dated: Acknowledgements I would like to express my heartfelt thanks to my supervisor Mr. Marius Feldmann, who gave me the chance to do this thesis. Without his advice, encouragement, enduring patience and constant support, the work presented in this thesis would not have been possible. I also wish to thank Prof. Dr. Alexander Schill who provided direction and all ideas along the way as I expected. I appreciate his guidance and additional helpful proposal I needed in order to accomplish this thesis. Additionally, I am greatly indebted to Liu, Wu, Deng and Wason for sharing and providing me their knowledge, and to Xu for giving her advice.
    [Show full text]
  • Textbook Web Site Minimal Html5 Document Minimal
    HTML5 INTERACTIVE WEB SITES LECTURE 2 CS 50.12 : : Fall 2013 : : Corrine Haverinen Santa Rosa Junior College TEXTBOOK WEB SITE Introducing HTML5 Errata, links, example files, some new stuff MINIMAL HTML5 DOCUMENT <!DOCTYPE html> <meta charset="utf-8"> <title>Always Title Your Documents</title> <p>Your exciting new stuff</p> Should we use <html> <head> <body> tags? MINIMAL HTML5 DOCUMENT, SAFER Reasons to use <html> <head> <body> tags <html> element with language good for accessibility <html lang=en> IE8 and below: require the <body> element in order to apply CSS MINIMAL HTML5 DOCUMENT, SAFER <!DOCTYPE html> <html lang=en> <head> <meta charset="utf-8"> <title>Always Title Your Documents</title> </head> <body> <p>Your exciting new stuff</p> </body> </html> SEMANTIC HTML conveying the meaning behind Web pages understanding how things are related to each other embed semantics in Web docs with: HTML elements, body, #d headings, lists, blockquote use new HTML5 sectioning elements use the correct element or tag to describe the content semantic tags used for their purpose, not for styling ARIA enhancement Microdata such as Microformats, RDFa REASONS TO USE SEMANTIC HTML lighter, cleaner code accessibility search engine optimization if your important content is not in the HTML (JS, CSS, etc) search engines will not see it easier for search engines to get what your site is about semantically correct the right way as opposed to such practices as hidden text used to increase relevance Hold meaning even though repurposed (RSS feeds, redesign of layout) Easier for developers to work with OLD METHOD ­ DIV TAGS <div> based layouts ­ standard way to layout and style content <div> is flow content element, does not stand apart in the structure of the document <div> tags have no meaning semantically, no impact on the computable structure of the page or document outline HTML5 NEW SEMANTIC ELEMENTS <header> <nav> <hgroup> <main> NEW!! <section> <article> <aside> <footer> HTML5 ELEMENTS ­ OLD BROWSERS New tags stylable in all modern browsers..
    [Show full text]
  • Semantic HTML
    Semantic HTML !1 The Need for Semantic Elements " Give content on the page meaning and structure " Semantics portray the value of content on a page, and are not just its style " Semantic markup can be " Semantic markup can make interpreted by tools for the site maintenance easier as visually impaired new developers can quickly grasp the site structure " Search Engines can use semantic markup to better " Updating / Restyling may by categorise and classify streamlined by using semantic elements content !2 Standard Semantic Elements " Semantic HTML is HTML in which: " Text is wrapped in elements that reflect the content. For example: " A paragraph is contained in a <p> element. " A sequential list is contained in an <ol> element. " A large block of text quoted from another source is contained in a <blockquote> element. " HTML elements are not used for a purpose other than their semantic purpose. For example: " <h1> contains headings; it is not for making text bigger. " <blockquote> contains a long quote; it is not for indenting text. " An empty paragraph element ( <p></p> ) is not used to skip lines. " Text contains no stylistic information directly. For example: " No use of format tags such as <font> or <center> . " No reference to colors or location in classes or IDs. !3 http://www.adobe.com/devnet/archive/html5/articles/semantic-markup.html HTML5 Semantic Elements <header> <nav> <section> <article> <aside> <figcaption> <figure> <footer> !4 <nav> <nav> <h1>Navigation</h1> <ul> <li><a href="articles.html">Index of all articles</a></li> <li><a
    [Show full text]
  • Semantic Web and Electronic Information Resources1, Infotheca Journal 4(2003)2, P
    D.Radovanovic: Semantic Web and Electronic Information Resources1, Infotheca journal 4(2003)2, p. 157-163 UDC 004.738.5:004.451.53:004.22 Semantic Web and Electronic Information Resources Danica Radovanović Abstract The usage of electronic resources depends on good possibilities of searching and the Semantic Web concept can be convenient solution for information retrieval (IR). WWW (World Wide Web) enables, with the help of search engines and huge number of available (meta)information, data that can satisfy user's need for information, but only at some extent. At the same time, there are more and more research efforts to increase the efficiency for IR until one gets as much as possible relevant information on the Web. As one of the latest results of this W3C efforts, Semantic Web presents a group of organized technological standards, IT products, and information linked in such a way that can be easily indexed and semantically filtered through the process of classification on the global scale. Semantic Web and its principles make IR easier because it can be also observed as very useful and successful way of representing data on the WWW or as a group of globally linked databases. The architecture of Semantic Web consists of three important IT standards: XML (eXtensible MarkUp Language), RDF (Resource Description Framework) and the ontologies. Semantic web is still under development and is not in common usage but it promises that it will radically improve the possibility of searching, sorting and classification of information. Key words: Semantic Web, electronic information resources, information retrieval, information representation, Internet, standards 1.
    [Show full text]
  • A Semantic Web Primer Antoniou and Van Harmelen Computer Science / Internet
    A Semantic Web Primer A Semantic Web computer science / Internet A Semantic Web Primer Second Edition Second Edition Grigoris Antoniou and Frank van Harmelen The development of the Semantic Web, with machine-readable content, has the potential to revolutionize the World Wide Web and its uses. A Semantic Web Primer provides an introduction and guide to this still emerging field, describing its key ideas, languages, and technologies. Suitable for use as a textbook or for self-study by professionals, it concentrates on undergraduate-level fundamental concepts and techniques that will enable readers to proceed with building applications on their own and includes exercises, project descriptions, and annotated references to relevant online materials. A Semantic Web Primer provides a systematic treatment of the different languages (XML, RDF, OWL, and rules) and technologies (explicit metadata, ontologies, and logic and inference) that are central to Semantic Web development as well as such crucial related topics as ontology engineering and application scenarios. This substantially revised and updated second edition reflects recent developments in the field, covering new application areas and tools. The new material includes a Harmelen and van Antoniou discussion of such topics as SPARQL as the RDF query language; OWL DLP and its interesting practical and theoretical Edition Second properties; the SWRL language (in the chapter on rules); OWL-S (on which the discussion of Web services is now based). The new final chapter considers the state of the art of the field today, captures ongoing discussions, and outlines the most challenging issues facing the Semantic Web in the future. Supplementary materials, including slides, online versions of many of the code fragments in the book, and links to further reading, can be found at http://www.semanticwebprimer.org.
    [Show full text]