Slides for talk given at IWMW 1998 held at the University of Newcastle on 15-17 September 1998.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-sep1998/materials/
LOD2 plenary meeting in Paris: presentation of WP5: State of Play: Linked Data Visualization, Browsing and Authoring, by Renaud Delbru (National University of Ireland, Galway).
This document summarizes a webinar on metadata for managing scientific research data. The webinar covered why metadata is important for scientific data management, definitions of data and metadata, selected metadata standards including Dublin Core, Darwin Core and FGDC, challenges in generating metadata and opportunities to address these challenges, and advice for getting started with metadata. The webinar emphasized that metadata standards provide guidelines not strict rules, and encouraged participants to keep metadata simple while aiming to facilitate reuse of data.
The document discusses a webinar presented by LOD2 on creating knowledge from interlinked data. It describes LOD2 as an EU-funded project involving leading linked open data organizations. The webinar agenda includes discussing SIREn, a plugin for Elasticsearch that allows indexing and searching of JSON documents. It provides an overview of Elasticsearch and describes how to install SIREn, create an index, index documents, and perform searches on nested JSON data.
Slides of the presentation by Robert Isele of Free University of Berlin, Germany in the course of the LOD2 webinar: SILK on 21.02.2012 - for more information please see: http://lod2.eu/BlogPost/webinar-series
This document summarizes Linked Library Data initiatives and the role of the Dublin Core Metadata Initiative. It discusses how libraries are publishing structured data using vocabularies like FRBR, MARC, and RDA. It also outlines efforts to align library metadata with the Dublin Core Abstract Model and link library data on the web through the W3C Linked Data Incubator Group. The document concludes that distributing bibliographic control through linked data allows for greater interlinking and description of values as non-literal resources.
This webinar in the course of the LOD2 webinar series will present use cases and live demos of D2R (Free University Berlin) and Sparqlify (University of Leipzig).
D2R Server is a tool for publishing relational databases on the Semantic Web. It enables RDF and HTML browsers to navigate the content of the database, and allows applications to query the database using the SPARQL query language.
Sparqlify is a tool enabling one to define expressive RDF views on relational databases and query them with a subset of the SPARQL query language. By featuring a novel RDF view definition syntax, it aims at simplifying the RDB-RDF mapping process.
more to be found at:
About the Webinar
In May 2012, the Library of Congress announced a new modeling initiative focused on reflecting the MARC 21 library standard as a Linked Data model for the Web, with an initial model to be proposed by the consulting company Zepheira. The goal of the initiative is to translate the MARC 21 format to a Linked Data model while retaining the richness and benefits of existing data in the historical format.
In this webinar, Eric Miller of Zepheira will report on progress towards this important goal, starting with an analysis of the translation problem and concluding with potential migration scenarios for a broad-based transition from MARC to a new bibliographic framework.
LOD2 plenary meeting in Paris: presentation of WP5: State of Play: Linked Data Visualization, Browsing and Authoring, by Renaud Delbru (National University of Ireland, Galway).
This document summarizes a webinar on metadata for managing scientific research data. The webinar covered why metadata is important for scientific data management, definitions of data and metadata, selected metadata standards including Dublin Core, Darwin Core and FGDC, challenges in generating metadata and opportunities to address these challenges, and advice for getting started with metadata. The webinar emphasized that metadata standards provide guidelines not strict rules, and encouraged participants to keep metadata simple while aiming to facilitate reuse of data.
The document discusses a webinar presented by LOD2 on creating knowledge from interlinked data. It describes LOD2 as an EU-funded project involving leading linked open data organizations. The webinar agenda includes discussing SIREn, a plugin for Elasticsearch that allows indexing and searching of JSON documents. It provides an overview of Elasticsearch and describes how to install SIREn, create an index, index documents, and perform searches on nested JSON data.
Slides of the presentation by Robert Isele of Free University of Berlin, Germany in the course of the LOD2 webinar: SILK on 21.02.2012 - for more information please see: http://lod2.eu/BlogPost/webinar-series
This document summarizes Linked Library Data initiatives and the role of the Dublin Core Metadata Initiative. It discusses how libraries are publishing structured data using vocabularies like FRBR, MARC, and RDA. It also outlines efforts to align library metadata with the Dublin Core Abstract Model and link library data on the web through the W3C Linked Data Incubator Group. The document concludes that distributing bibliographic control through linked data allows for greater interlinking and description of values as non-literal resources.
This webinar in the course of the LOD2 webinar series will present use cases and live demos of D2R (Free University Berlin) and Sparqlify (University of Leipzig).
D2R Server is a tool for publishing relational databases on the Semantic Web. It enables RDF and HTML browsers to navigate the content of the database, and allows applications to query the database using the SPARQL query language.
Sparqlify is a tool enabling one to define expressive RDF views on relational databases and query them with a subset of the SPARQL query language. By featuring a novel RDF view definition syntax, it aims at simplifying the RDB-RDF mapping process.
more to be found at:
About the Webinar
In May 2012, the Library of Congress announced a new modeling initiative focused on reflecting the MARC 21 library standard as a Linked Data model for the Web, with an initial model to be proposed by the consulting company Zepheira. The goal of the initiative is to translate the MARC 21 format to a Linked Data model while retaining the richness and benefits of existing data in the historical format.
In this webinar, Eric Miller of Zepheira will report on progress towards this important goal, starting with an analysis of the translation problem and concluding with potential migration scenarios for a broad-based transition from MARC to a new bibliographic framework.
This document discusses interaction with linked data, focusing on visualization techniques. It begins with an overview of the linked data visualization process, including extracting data analytically, applying visualization transformations, and generating views. It then covers challenges like scalability, handling heterogeneous data, and enabling user interaction. Various visualization techniques are classified and examples are provided, including bar charts, graphs, timelines, and maps. Finally, linked data visualization tools and examples using tools like Sigma, Sindice, and Information Workbench are described.
Link Sets And Why They Are Important (EDF2012)Anja Jentzsch
This document discusses the importance of links between datasets on the semantic web. It outlines that while there are over 30 billion triples published as linked open data, less than 500 million of these are links between datasets. This limits the ability to connect data islands into a global web of data. The document then describes tools like the LATC platform that can help automate the process of identifying links between datasets through linkage rules and machine learning of rules. It provides examples of how the LATC workbench can be used to select datasets, write linkage rules, generate links, and ensure link quality.
This document discusses the generation of linked data platforms (LDPs) in highly decentralized information ecosystems. It presents a model for automating the generation of LDPs that considers data heterogeneity, hosting constraints, and reusability of LDP designs. The model includes an LDP generation workflow, a design language called LDP-DL to describe LDP designs, and an LDP generation toolkit to implement the workflow. The goal is to facilitate data exploitation for consumers in decentralized environments.
This presentation covers the whole spectrum of Linked Data production and exposure. After a grounding in the Linked Data principles and best practices, with special emphasis on the VoID vocabulary, we cover R2RML, operating on relational databases, Open Refine, operating on spreadsheets, and GATECloud, operating on natural language. Finally we describe the means to increase interlinkage between datasets, especially the use of tools like Silk.
1) Microformats are conventions for embedding semantics in HTML to enable decentralized development of metadata. They use class names to label commonly used data types like people, events, reviews.
2) Microformats are designed for humans and machines, intended to allow information to be automatically processed by software. They emerged from an open community process.
3) Popular microformats include hCard for contact information and hCalendar for events. Rel-license adds metadata about content licenses. Tools like Firefox extensions can detect and surface microformatted data.
NISO Standards update: KBart and Demand Driven Acquisitions Best PracticesJason Price, PhD
This document summarizes a presentation about developing best practices for demand-driven acquisition (DDA) of monographs. It defines DDA and discusses the need for standardized practices to help libraries, publishers, and vendors effectively implement DDA programs. The presentation outlines goals to develop a flexible DDA model, recommendations around access models, technology, and metrics, and addresses obstacles. It notes next steps will include surveys, focus groups, and interviews to inform the development of NISO recommended practices for DDA by December 2013.
This document summarizes a webinar on using metadata for public sector administration. It discusses the Asset Description Metadata Schema (ADMS), a vocabulary for describing semantic interoperability assets to facilitate their discovery and reuse. ADMS was developed to provide a common way to describe assets so they can be more easily searched, identified, compared and obtained from a single access point. It reuses terms from standards like Dublin Core and defines properties and classifications to characterize assets consistently.
The document provides an introduction to the semantic web, discussing its development from earlier metadata standards like Dublin Core. It explains the limitations of XML for representing semantics and the need for shared ontologies. The semantic web aims to add formal semantics to web content to enable software agents to process web resources like humans. Key technologies include RDF, RDF Schema, and DAML+OIL. Challenges include complexity, industry adoption, and trust.
The document provides an introduction to Dublin Core metadata, including:
1) Dublin Core is a set of metadata standards including 15 simple elements and over 50 qualified elements for describing resources.
2) Dublin Core metadata can be used to improve resource discovery and is recommended for metadata harvesting and the semantic web.
3) Custom mappings can be made from other metadata standards like LOM to the Dublin Core Abstract Model to make metadata interoperable.
The document discusses key trends in the food packaging industry between 2016 and beyond. It identifies five major trends: 1) Increasing importance of design and shelf appeal to stand out, 2) Increasing competitive intensity driving cost focus, 3) Growing focus on sustainability and environmental friendliness, 4) Intelligent packaging solutions continuing to develop, and 5) Increased e-tailing volumes driving new packaging demands. These trends will impact brand owners, retailers, and logistics providers by requiring more efficient and sustainable packaging designs that enhance the consumer experience both in stores and online.
Este documento presenta una introducción a la poesía del siglo XIX, enfocándose en el parnasianismo y el simbolismo. Explica que el parnasianismo surgió como una reacción contra el realismo y el naturalismo, buscando un arte que se justifique a sí mismo por su belleza estética. Destaca a poetas parnasianos como Charles Leconte de Lisle y Théophile Gautier. Luego, describe las características del simbolismo, incluyendo su musicalidad y uso del verso libre, así como a sus principales
Viewpoint Retail Packaging 2016 and beyond_EnglishVesa Penttinen
Retail packaging is experiencing dynamic changes as consumers demand more convenient and sustainable shopping. This is putting pressure on retailers and brands to innovate. Key trends include the rise of discount retailers focusing on cost efficiency through packaging solutions, increased private label penetration that is making packaging a more important brand element, the growth of e-commerce shifting packaging needs, and a stronger focus on sustainability. Intelligent packaging using technologies like RFID is emerging but not widespread yet. Navigating these complex changes while improving packaging functions and reducing costs presents challenges for retailers and brands.
This document provides an overview of abdominal trauma including mechanisms of injury, signs and symptoms, diagnostic tests, and treatment approaches for various organ injuries. Key points include:
- Delay in recognizing intra-abdominal injuries can lead to death from hemorrhage.
- FAST, DPL, and CT scans are used to diagnose injuries, with CT being the most specific and accurate test.
- Common solid organ injuries are to the spleen, liver, kidneys, and pancreas. Signs may include abdominal tenderness or bruising. Treatment depends on injury severity and may involve surgery or embolization.
- Hollow organ injuries to the bowel or bladder can cause peritonitis and require surgical repair.
Presentació del tema 12 de l'assignatura de biologia de 2n de batxillerat.
Presentació preparada amb el llibre de 2n de Batxillerat Santillana i altres materials.
Biologia 2n Batxillerat. UD17. Microorganismes, malalties i biotecnologiaOriol Baradad
Presentació del tema 17 de l'assignatura de biologia de 2n de batxillerat.
Presentació preparada amb el llibre de 2n de Batxillerat Santillana i altres materials.
IWMW 2002: Web standards briefing (session C2)IWMW
Web Standards Briefing session at IWMW 2002 event by Brian Kelly.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/materials/kelly1/
The document provides an overview of the evolution and trends of web technologies and applications. It discusses the key stages in the evolution of the web from pre-web to modern mobile web. These stages include the early/simple web using static HTML, the dynamic web enabled by server-side processing, the web as a platform supported by mature frameworks, and advances like Web 2.0 and responsive design for mobile. It also covers fundamental technologies, components, servers, processing capabilities, and trends that have shaped the landscape of web development.
Open for Business - Open Archives, OpenURL, RSS and the Dublin CoreAndy Powell
UKOLN is a center of expertise in digital information management supported by various standards and technologies. The document provides an overview of context-sensitive linking, metadata harvesting, RSS, OpenURL, and Dublin Core, describing their purposes and importance in integrating heterogeneous collections and enabling discovery and access across platforms. Key technologies discussed include the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), RSS, and OpenURL, which allow separation of discovery and delivery of content through standards-based linking.
The Web Data Commons Microdata, RDFa, and Microformat Dataset Series @ ISWC2014Robert Meusel
The document describes a series of datasets created by parsing HTML pages to extract structured data in the form of Microdata, RDFa, and Microformats. It provides an overview of the datasets created in 2010, 2012, and 2013, which contain over 30 billion RDF quads extracted from over 1.7 million domains. The datasets are hosted online and provide insights into the usage of different vocabularies and markup languages as well as opportunities for applying and analyzing the large-scale structured web data.
A set of slides that provides a high-level overview of the W3C Linked Data Platform specification presented at the 4th Linked Data in Architecture and Construction Workshop.
For more detailed and technical version of the presentation, please refer to
http://www.slideshare.net/nandana/learning-w3c-linked-data-platform-with-examples
LDAC 2016 programme
http://smartcity.linkeddata.es/LDAC2016/#programme
This document discusses interaction with linked data, focusing on visualization techniques. It begins with an overview of the linked data visualization process, including extracting data analytically, applying visualization transformations, and generating views. It then covers challenges like scalability, handling heterogeneous data, and enabling user interaction. Various visualization techniques are classified and examples are provided, including bar charts, graphs, timelines, and maps. Finally, linked data visualization tools and examples using tools like Sigma, Sindice, and Information Workbench are described.
Link Sets And Why They Are Important (EDF2012)Anja Jentzsch
This document discusses the importance of links between datasets on the semantic web. It outlines that while there are over 30 billion triples published as linked open data, less than 500 million of these are links between datasets. This limits the ability to connect data islands into a global web of data. The document then describes tools like the LATC platform that can help automate the process of identifying links between datasets through linkage rules and machine learning of rules. It provides examples of how the LATC workbench can be used to select datasets, write linkage rules, generate links, and ensure link quality.
This document discusses the generation of linked data platforms (LDPs) in highly decentralized information ecosystems. It presents a model for automating the generation of LDPs that considers data heterogeneity, hosting constraints, and reusability of LDP designs. The model includes an LDP generation workflow, a design language called LDP-DL to describe LDP designs, and an LDP generation toolkit to implement the workflow. The goal is to facilitate data exploitation for consumers in decentralized environments.
This presentation covers the whole spectrum of Linked Data production and exposure. After a grounding in the Linked Data principles and best practices, with special emphasis on the VoID vocabulary, we cover R2RML, operating on relational databases, Open Refine, operating on spreadsheets, and GATECloud, operating on natural language. Finally we describe the means to increase interlinkage between datasets, especially the use of tools like Silk.
1) Microformats are conventions for embedding semantics in HTML to enable decentralized development of metadata. They use class names to label commonly used data types like people, events, reviews.
2) Microformats are designed for humans and machines, intended to allow information to be automatically processed by software. They emerged from an open community process.
3) Popular microformats include hCard for contact information and hCalendar for events. Rel-license adds metadata about content licenses. Tools like Firefox extensions can detect and surface microformatted data.
NISO Standards update: KBart and Demand Driven Acquisitions Best PracticesJason Price, PhD
This document summarizes a presentation about developing best practices for demand-driven acquisition (DDA) of monographs. It defines DDA and discusses the need for standardized practices to help libraries, publishers, and vendors effectively implement DDA programs. The presentation outlines goals to develop a flexible DDA model, recommendations around access models, technology, and metrics, and addresses obstacles. It notes next steps will include surveys, focus groups, and interviews to inform the development of NISO recommended practices for DDA by December 2013.
This document summarizes a webinar on using metadata for public sector administration. It discusses the Asset Description Metadata Schema (ADMS), a vocabulary for describing semantic interoperability assets to facilitate their discovery and reuse. ADMS was developed to provide a common way to describe assets so they can be more easily searched, identified, compared and obtained from a single access point. It reuses terms from standards like Dublin Core and defines properties and classifications to characterize assets consistently.
The document provides an introduction to the semantic web, discussing its development from earlier metadata standards like Dublin Core. It explains the limitations of XML for representing semantics and the need for shared ontologies. The semantic web aims to add formal semantics to web content to enable software agents to process web resources like humans. Key technologies include RDF, RDF Schema, and DAML+OIL. Challenges include complexity, industry adoption, and trust.
The document provides an introduction to Dublin Core metadata, including:
1) Dublin Core is a set of metadata standards including 15 simple elements and over 50 qualified elements for describing resources.
2) Dublin Core metadata can be used to improve resource discovery and is recommended for metadata harvesting and the semantic web.
3) Custom mappings can be made from other metadata standards like LOM to the Dublin Core Abstract Model to make metadata interoperable.
The document discusses key trends in the food packaging industry between 2016 and beyond. It identifies five major trends: 1) Increasing importance of design and shelf appeal to stand out, 2) Increasing competitive intensity driving cost focus, 3) Growing focus on sustainability and environmental friendliness, 4) Intelligent packaging solutions continuing to develop, and 5) Increased e-tailing volumes driving new packaging demands. These trends will impact brand owners, retailers, and logistics providers by requiring more efficient and sustainable packaging designs that enhance the consumer experience both in stores and online.
Este documento presenta una introducción a la poesía del siglo XIX, enfocándose en el parnasianismo y el simbolismo. Explica que el parnasianismo surgió como una reacción contra el realismo y el naturalismo, buscando un arte que se justifique a sí mismo por su belleza estética. Destaca a poetas parnasianos como Charles Leconte de Lisle y Théophile Gautier. Luego, describe las características del simbolismo, incluyendo su musicalidad y uso del verso libre, así como a sus principales
Viewpoint Retail Packaging 2016 and beyond_EnglishVesa Penttinen
Retail packaging is experiencing dynamic changes as consumers demand more convenient and sustainable shopping. This is putting pressure on retailers and brands to innovate. Key trends include the rise of discount retailers focusing on cost efficiency through packaging solutions, increased private label penetration that is making packaging a more important brand element, the growth of e-commerce shifting packaging needs, and a stronger focus on sustainability. Intelligent packaging using technologies like RFID is emerging but not widespread yet. Navigating these complex changes while improving packaging functions and reducing costs presents challenges for retailers and brands.
This document provides an overview of abdominal trauma including mechanisms of injury, signs and symptoms, diagnostic tests, and treatment approaches for various organ injuries. Key points include:
- Delay in recognizing intra-abdominal injuries can lead to death from hemorrhage.
- FAST, DPL, and CT scans are used to diagnose injuries, with CT being the most specific and accurate test.
- Common solid organ injuries are to the spleen, liver, kidneys, and pancreas. Signs may include abdominal tenderness or bruising. Treatment depends on injury severity and may involve surgery or embolization.
- Hollow organ injuries to the bowel or bladder can cause peritonitis and require surgical repair.
Presentació del tema 12 de l'assignatura de biologia de 2n de batxillerat.
Presentació preparada amb el llibre de 2n de Batxillerat Santillana i altres materials.
Biologia 2n Batxillerat. UD17. Microorganismes, malalties i biotecnologiaOriol Baradad
Presentació del tema 17 de l'assignatura de biologia de 2n de batxillerat.
Presentació preparada amb el llibre de 2n de Batxillerat Santillana i altres materials.
IWMW 2002: Web standards briefing (session C2)IWMW
Web Standards Briefing session at IWMW 2002 event by Brian Kelly.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/materials/kelly1/
The document provides an overview of the evolution and trends of web technologies and applications. It discusses the key stages in the evolution of the web from pre-web to modern mobile web. These stages include the early/simple web using static HTML, the dynamic web enabled by server-side processing, the web as a platform supported by mature frameworks, and advances like Web 2.0 and responsive design for mobile. It also covers fundamental technologies, components, servers, processing capabilities, and trends that have shaped the landscape of web development.
Open for Business - Open Archives, OpenURL, RSS and the Dublin CoreAndy Powell
UKOLN is a center of expertise in digital information management supported by various standards and technologies. The document provides an overview of context-sensitive linking, metadata harvesting, RSS, OpenURL, and Dublin Core, describing their purposes and importance in integrating heterogeneous collections and enabling discovery and access across platforms. Key technologies discussed include the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), RSS, and OpenURL, which allow separation of discovery and delivery of content through standards-based linking.
The Web Data Commons Microdata, RDFa, and Microformat Dataset Series @ ISWC2014Robert Meusel
The document describes a series of datasets created by parsing HTML pages to extract structured data in the form of Microdata, RDFa, and Microformats. It provides an overview of the datasets created in 2010, 2012, and 2013, which contain over 30 billion RDF quads extracted from over 1.7 million domains. The datasets are hosted online and provide insights into the usage of different vocabularies and markup languages as well as opportunities for applying and analyzing the large-scale structured web data.
A set of slides that provides a high-level overview of the W3C Linked Data Platform specification presented at the 4th Linked Data in Architecture and Construction Workshop.
For more detailed and technical version of the presentation, please refer to
http://www.slideshare.net/nandana/learning-w3c-linked-data-platform-with-examples
LDAC 2016 programme
http://smartcity.linkeddata.es/LDAC2016/#programme
This document provides an introduction to HTML and web development. It outlines Richard Dron's role helping students develop technical skills, and the aims and learning outcomes of the Principles of Systems Development course. The document discusses the history of HTML, recommends learning HTML 4.01 and introduces key HTML elements and markup essentials. It also provides examples of document structure, hyperlinks, and lists before directing students to additional resources.
Tim Berners-Lee invented the World Wide Web in 1989-1990 at CERN as a means to transfer text and graphics simultaneously using a client/server data transfer protocol. The web relies on URIs for locating resources, HTTP for accessing resources over the web, and hypertext for easy navigation between resources using HTML. Key components included browsers to send HTTP requests to servers and render returned web pages constructed with HTML, CSS, and other files.
Microformats are simple conventions for embedding semantics in HTML to enable decentralized development. They are designed for humans first and machines second, using existing HTML standards. Common microformats include hCard for contact information, hCalendar for events, and rel-license for indicating content licenses. Tools like Firefox extensions can consume microformats, and sites like Flickr and Meetup.com use microformats to share information in a structured way. Developers can also build their own applications using microformats.
An introduction deck for the Web of Data to my team, including basic semantic web, Linked Open Data, primer, and then DBpedia, Linked Data Integration Framework (LDIF), Common Crawl Database, Web Data Commons.
This document provides an introduction to web technologies courses. It defines key terms like the Internet and the World Wide Web. It outlines the history and growth of the web from 1995 to present day. It also describes the focus of the course which is web development technologies including protocols, architectures, languages, and methods/tools. The document lists prerequisites and provides an overview of course contents, exams, and references.
This document provides an introduction to web programming and HTML. It discusses how this course will make students familiar with building web sites and applications that run in browsers using scripting languages. The objectives are to introduce technologies for building web pages, standards, best practices, IDEs, connecting sites to databases, and web applications. Main technologies covered are HTML, CSS, JavaScript, Angular JS, PHP, and MySQL.
Code for Startup MVP (Ruby on Rails) Session 1Henry S
First Session on Learning to Code for Startup MVP's using Ruby on Rails.
This session covers the web architecture, Git/GitHub and makes a real rails app that is deployed to Heroku at the end.
Thanks,
Henry
Usage of Linked Data: Introduction and Application ScenariosEUCLID project
This presentation introduces the main principles of Linked Data, the underlying technologies and background standards. It provides basic knowledge for how data can be published over the Web, how it can be queried, and what are the possible use cases and benefits. As an example, we use the development of a music portal (based on the MusicBrainz dataset), which facilitates access to a wide range of information and multimedia resources relating to music.
This document provides an introduction to fundamental concepts and technologies related to the Internet and World Wide Web. It discusses the differences between the Internet, which is a global system of interconnected computer networks, and the Web, which is a service that allows accessing multimedia documents over the Internet. The document then provides a brief history of the development of the Internet and Web. It explains basic Internet communication protocols and standards like TCP/IP and HTTP. It also describes HTML, CSS, and JavaScript which are key technologies for building static and dynamic Web pages.
This document discusses the history and concepts of Representational State Transfer (REST). It provides context on how REST began in the 1990s alongside the growth of the World Wide Web. It discusses three perspectives on the web - as an information space, computational space, and hypermedia system. It also discusses Roy Fielding's dissertation which defined REST and the constraints that make it applicable to large-scale distributed hypermedia systems like the Web.
Standard Generalized Markup Language (SGML) is a metalanguage used to define markup languages like HTML and XML. It requires defining document structure rules through a Document Type Definition (DTD). While powerful, SGML is complex. HTML simplified SGML and does not require a DTD. The World Wide Web Consortium (W3C) develops standards to ensure the long-term growth of the web, including HTML versions like HTML5 which adds audio/video embedding and new elements.
Topics:
- Web Architecture Overview
- HTTP (Hypertext Transfer Protocol)
- REST (Representational State Transfer)
- JSON (JavaScript Object Notation)
Slides for the course of "Ambient Intelligence: Technology and Design" given at Politecnico di Torino during year 2013/2014.
Course website: http://bit.ly/polito-ami
The document introduces some basic concepts of web application programming including HTTP, clients and servers, resources, requests and responses.
HTTP is a stateless protocol used to transfer information on intranets and the World Wide Web. It defines request and response methods between clients and servers. Clients such as web browsers make HTTP requests to servers, which store and provide resources/files in response. Common resources are accessed via URLs.
HTTP requests use methods like GET to retrieve representations of resources. A GET request involves opening a connection, sending the request, and reading the response. Responses contain header information and the requested resource. Standards like HTML, CSS, XML, and JavaScript are used to structure modern web documents and provide inter
This document summarizes the author's experience moving from heading the web services team at a modern, centralized university to a traditional, decentralized university. At the modern university, there was a strong emphasis on branding and visual identity across a centralized website. However, at the traditional university, websites were managed separately by different departments, leading to duplication, incorrect information, and a lack of consistent branding or user experience. The author outlines steps to improve communication, gain support from top administrators, and reshape the web team to develop a unified online identity and branding while still supporting individual departments.
UKOLN provides leadership to libraries, information organizations, and cultural heritage institutions to help them advance their services in digital environments. They conduct research, provide advice and consulting, and promote community building through events. UKOLN works on projects at local, regional, national, and global levels to help different organizations collaborate and make their resources interoperable. Sharing knowledge through conferences and workshops is important for developing a joined-up approach where organizations work together.
This document discusses various web tools including browsers, content management systems, and browser management. It covers Opera browser, WebTV, Zope content management system, and an example from City University Business School. Specifically:
1. It discusses different browsers like Opera and WebTV, issues with browser management, and recommends Zope content management system for improving workflows.
2. Zope is described as middleware, an authoring tool, and object database that can improve how we work and manage content.
3. An example from City University Business School demonstrates combining current software like Lotus Notes to provide web content management.
This document provides a personal contingency plan for beating panic by creating choices, weighing options, and making a plan. It outlines thinking of 5 potential choices when facing panic and assessing those choices using SWOT analysis. The plan recommends crafting a story for each choice by considering who, what, why, how, where, when, and with what. It also identifies 7 qualities to cultivate: committed, decisive, healthy, mentored, persuasive, solvent, and specialist.
Debate on "The house believes that the future of Web in UK Higher and Further Education communities lies in the adoption of open source software" at IWMW 2002.
Panel session on “Avoiding Portal Wars” given at the IWMW 2002 event.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/talks/panel/
Social participation through forums and blogs has been used for student recruitment in higher education. Existing social media sites or creating your own can help drive traffic and peer recommendations. Fears around negative comments, lack of control and the unknown are holding institutions back. To improve, institutions should assign responsibilities, build relationships through targeted content, embrace change and recognize social media's potential for recruitment.
The document outlines the tasks for a photo scavenger hunt held at the University of Greenwich from June 25-27, 2019 as part of the IWMW 2019 conference. Participants were instructed to find Prime Meridian markers, take photos with strangers in uniforms, get to know local dogs, pour drinks, carry large objects, hang from fences, mourn a dead parrot, multitask, and pretend to be king of the world.
1) The University's web estate has evolved organically leading to gaps in knowledge and risks from fragmentation.
2) There are over 1,497 websites using various platforms with over 1 million pages, but governance is limited and quality varies widely.
3) The strategy aims to establish central governance and standards while allowing flexibility, with a unified modern platform, engaged user communities, and data-driven decision making.
Static Site Generators - Developing Websites in Low-resource ConditionIWMW
Paul Walk discusses static site generators as an alternative to content management systems for publishing websites. Static site generators allow content to be authored in simple text files using formats like Markdown and compiled into static HTML and CSS that can be hosted on basic web servers. They provide benefits like minimal infrastructure needs, easy preservation of content, and increased security compared to systems that rely on databases. However, they may not be as user-friendly for content authoring. In general, static site generators are best suited for smaller, simpler websites that don't require advanced user access controls or dynamic functionality.
This document provides an agenda for the final day of the IWMW 2019 conference on June 27, 2019. The conference focused on strategic thinking and was held at the University of Greenwich in London. The agenda discusses continuing professional development for institutional digital teams, supporting regional communities of practice groups established after the previous conference, maintaining the IWMW blog and Twitter presence after the event, and governance topics like the future role of the IWMW Oversight Group. It also thanks the speakers, sponsors, advisory group, live streamers, official cartoonist, and host university for their contributions to the successful three-day conference.
This document provides an agenda and notes for Session 7 of the IWMW 2019 conference with the theme "Strategic Thinking". The session will be chaired by Andrew Millar and use the hashtag #iwmw19. Issues to be discussed include supporting professional development for institutional digital teams, following up on regional groups from last year, governance of the IWMW blog and Twitter account, sustainability and scope of future IWMW events, and looking ahead to IWMW's 25th anniversary. The document expresses thanks to speakers, sponsors, the advisory group, those who helped amplify the event online, the official cartoonist, and the host university.
The document discusses the need for vertical learning and communities of practice in a VUCA world. It provides examples of successful communities of practice across institutions, including a work shadowing scheme and action learning sets for women. Tips are given for establishing a community of practice, such as identifying interested groups, using existing connections, defining membership and leadership, and ensuring the ability to meet regularly.
How to train your content- so it doesn't slow you down... IWMW
This document discusses how to optimize web content, especially images, to improve performance and accessibility. It provides statistics on how images make up a large portion of web page sizes and explains common image formats. Optimization techniques are suggested like using responsive images, compression tools, and content delivery networks. The document stresses considering performance and accessibility throughout the design and development process from user research to deployment. Improving assets at their source and removing blocking elements can enhance the user experience.
Grassroots & Guerrillas: The Beginnings of a UX RevolutionIWMW
This document summarizes Kat Husbands' presentation on the beginnings of a UX revolution at the University of Glasgow. It describes how over time, UX has progressed from being unrecognized to becoming more embedded in the organization's culture and practices. It provides examples of projects where UX methods like surveys, testing, and workshops were used to redesign pages like the staff homepage and student printing pages. Feedback shows these projects improved users' experiences. The presentation urges others to start small with UX work, iterate based on testing, and communicate results to continue progressing UX maturity within their organizations.
Brand Guideline of Bashundhara A4 Paper - 2024khabri85
It outlines the basic identity elements such as symbol, logotype, colors, and typefaces. It provides examples of applying the identity to materials like letterhead, business cards, reports, folders, and websites.
How to Manage Reception Report in Odoo 17Celine George
A business may deal with both sales and purchases occasionally. They buy things from vendors and then sell them to their customers. Such dealings can be confusing at times. Because multiple clients may inquire about the same product at the same time, after purchasing those products, customers must be assigned to them. Odoo has a tool called Reception Report that can be used to complete this assignment. By enabling this, a reception report comes automatically after confirming a receipt, from which we can assign products to orders.
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
How to Setup Default Value for a Field in Odoo 17Celine George
In Odoo, we can set a default value for a field during the creation of a record for a model. We have many methods in odoo for setting a default value to the field.
1. 1
Deploying New
Web Technologies
Brian Kelly Email Address
UK Web Focus B.Kelly@ukoln.ac.uk
UKOLN URL
University of Bath http://www.ukoln.ac.uk/
UKOLN is funded by the British Library Research and Innovation Centre,
the Joint Information Systems Committee of the Higher Education Funding
Councils, as well as by project funding from the JISC’s Electronic Libraries
Programme and the European Union.
UKOLN also receives support from the University of Bath where it is based.
2. 2
Contents
• Background
• Web Developments:
• Data Formats
• Transport
• Addressing
• Metadata
• Deployment Issues
• Questions
Aims of Talk
• To give an overview of
the Web architecture
and Web
standardisation
• To review new web
developments
• To address
implementation models
Aims of Talk
• To give an overview of
the Web architecture
and Web
standardisation
• To review new web
developments
• To address
implementation models
3. 3
Web and Standardisation
W3C
•Produces W3C
Recommendations on
Web protocols
•Managed approach to
developments
•Protocols initially developed
by W3C members
•Decisions made by W3C,
influenced by member
and public review
•UK members
include JISC,
UKERNA,
Southampton and
Bristol
IETF
• Produces Internet
Drafts on Internet protocols
• Bottom-up approach to developments
• Protocols developed by
interested individuals
• "Rough consensus and working
code"
ISO
• Produces ISO
Standards
• Can be slow moving
and bureaucratic
• Produce robust
standards
Proprietary
• De facto standards
• Often initially appealing
(cf PowerPoint)
• May emerge as
standards
PNG
HTML
Z39.50
Java?
PNG
HTML
Z39.50
Java?
PNG
HTML
HTTP
PNG
HTML
HTTP
HTTP
URN
HTTP
URN
HTML
extensions
PDF and Java?
HTML
extensions
PDF and Java?
4. 4
The Web Vision
Tim Berners-Lee's (and W3C's) vision for the
Web:
• Evolvability is critical
• Automation of information management:
If a decision can be made by machine, it should
• All structured data formats should be based on
XML
• Migrate HTML to XML
• All logical assertions to map onto RDF model
• All metadata to use RDF
See keynote talk at WWW 7 conference at
<URL: http://www.w3.org/Talks/1998/
0415-Evolvability/slide1-1.htm>
5. 5
Web Protocols
Web initially based on three
simple protocols:
• Data Formats
HTML (HyperText Markup
Language) provides the data format for native
documents
• Addressing
URLs (Uniform Resource Locator) provides an
addressing mechanism for web resources
• Transport
HTTP (HyperText Transfer Protocol) defines
transfer of resources between client and server
Data Format
HTML
Addressing
URL
Transport
HTTP
6. 6
HTML History
HTML 1.0 Unpublished specification.
HTML 2.0 Spec. based on innovations from NCSA
(forms and inline images!)
HTML 3.0 Proposed spec. (renamed from HTML+).
Very comprehensive
Failed to complete IETF standardisation
Little implementation experience
Proprietary Introduction of proprietary HTML elements
by Netscape and Microsoft
HTML 3.2 Spec. based on description of mainstream
innovations in marketplace
HTML 4.0 Current recommendation1998
1994
1997
1994-5
1995
1992
Dilemna
Proprietary extensions
cause problems.
But experiments
are needed
7. 7
HTML 4.0, CSS 2.0 and DOM
HTML 4.0 used in conjunction with CSS 2.0
(Cascading Style Sheets) and the DOM provides an
architecturally pure, yet functionally rich environment
HTML 4.0 : W3C-Rec
• Improved forms
• Hooks for stylesheets
• Hooks for scripting
languages
• Table enhancements
• Better printing
CSS 2.0 : W3C-Rec
• Support for all HTML
formatting
• Positioning of HTML
elements
• Multiple media support
CSS Problems
• Changes during CSS development
• Netscape & IE incompatibilities
• Continued use of browsers with
known bugs
CSS Problems
• Changes during CSS development
• Netscape & IE incompatibilities
• Continued use of browsers with
known bugs
DOM : W3C-Rec
• Document Object Model
• Hooks for scripting
languages
• Permits changes to
HTML & CSS properties
and content (DHTML)
8. 8
HTML Limitations
HTML 4.0 / CSS 2.0 have limitations:
• Difficulties in introducing new elements
– Time-consuming standardisation process
(<ABBREV>)
– Dictated by browser vendor (<BLINK>, <MARQUEE>)
• Area may be inappropriate for standarisation:
– Covers specialist area (maths, music, ...)
– Application-specific (<STUD-NUM>)
• HTML is a display (output) not storage format
• HTML's lack of arbitrary structure limits
functionality:
– Find all memos copied to John Smith
– How many unique tracks on Jackson Browne CDs
9. 9
XML
XML:
• Extensible Markup Language
• A lightweight SGML designed for network use
• Addresses HTML's lack of evolvability
• Arbitrary elements can be defined (<STUDENT-
NUMBER>, <PART-NO>, etc)
• Agreement achieved quickly - XML 1.0 became
W3C Recommendation in Feb 1998
• Support from industry (SGML vendors, Microsoft,
etc.)
• Various XML DTDs already agreed (MathML,
CML)
• Support in Netscape 5 and IE 5
10. 10
XML Deployment
Ariadne issue 14 has an
article on "What Is XML?"
Describes how XML
support can be provided:
• Natively by new browsers
• Back end conversion
of XML - HTML
• Client-side conversion
of XML - HTML / CSS
• Java rendering of XML
Examples of intermediaries
See http://www.ariadne.ac.uk/issue15/what-is/See http://www.ariadne.ac.uk/issue15/what-is/
11. 11
XLink, XPointer and XSL
XLink will provide sophisticated
hyperlinking missing in HTML:
• Links that lead user to multiple destinations
• Bidirectional links
• Links with special behaviors:
– Expand-in-place / Replace / Create new window
– Link on load / Link on user action
• Link databases
XPointer will provide
access to arbitrary
portions of XML resource.
Interesting IPR issues!
XSL stylesheet language will provide extensibility and
transformation facilities (e.g. create a table of contents)
England
France
<commentary xml:link="extended" inline="false">
<locator href="smith2.1" role="Essay"/>
<locator href="jones1.4" role="Rebuttal"/>
<locator href="robin3.2" role="Comparison"/>
</commentary>
<commentary xml:link="extended" inline="false">
<locator href="smith2.1" role="Essay"/>
<locator href="jones1.4" role="Rebuttal"/>
<locator href="robin3.2" role="Comparison"/>
</commentary>
12. 12
Addressing
URLs (e.g. http://www.bristol-
poly.ac.uk/depts/music/latest.html)
have limitations:
• Lack of long-term persistency
– Organisation changes name
– Department shut down / merged
– Directory structure reorganised
• Inability to support multiple versions of resources
(mirroring)
URNs (Uniform Resource Names):
• Proposed as solution
• Difficult to implement (no W3C activity in this area)
13. 13
Addressing - Solutions
DOIs (Document Object Identifiers):
• Proposed by publishing industry as a solution
• Aimed at supporting rights ownership
• Business model needed
PURLs (Persistent URLs):
• Provide single level of redirection
Pragmatic Solution:
• URLs don't break - people break them
• Design URLs to have long life-span
Further information:
<URL: http://www.ukoln.ac.uk/metadata/resources/urn/>
<URL: http://hosted.ukoln.ac.uk/biblink/wp2/
links.html>
14. 14
Transport
HTTP/0.9 and HTTP/1.0:
Design flaws and implementation problems
HTTP/1.1:
Addresses some of these problems
60% server support
Performance benefits! (60% packet traffic reduction)
Is acting as fire-fighter
Not sufficiently flexible or extensible
HTTP/NG:
Radical redesign used object-oriented technologies
Undergoing trials
Gradual transition (using proxies)
15. 15
Metadata
Metadata - the missing architectural component
from the initial implementation
of the web
Metadata / RDF
PICS, TCN,
MCF, DSig,
DC,...
Addressing
URL
Data format
HTML
Transport
HTTP
Metadata Needs:
• Resource discovery
• Content filtering
• Authentication
• Improved navigation
• Multiple format support
• Rights management
Metadata Needs:
• Resource discovery
• Content filtering
• Authentication
• Improved navigation
• Multiple format support
• Rights management
16. 16
Metadata Examples
DSig (Digital Signatures initiative):
• Key component for providing trust on the web
• DSig 2.0 will be based on RDF and will support
signed assertion:
– This page is from the University of Bath
– This page is a legally-binding list of courses
provided by the University
P3P (Platform for Privacy Preferences):
• Developing methods for exchanging Privacy
Practices of Web sites and user
Note that discussions about additional rights
management metadata are currently taking place
17. 17
RDF
RDF (Resource Description Framework):
• Highlight of WWW 7 conference
• Provides a metadata framework ("machine
understandable metadata for the web")
• Based on ideas from content rating (PICS),
resource discovery (Dublin Core) and site mapping
• Based on a formal data model (direct label graphs)
• Applications include:
– cataloging resources – resource discovery
– electronic commerce – intelligent agents
– digital signatures – content rating
– intellectual property rights – privacy
18. 18
Browser Support for RDF
Mozilla (Netscape's
source code release)
provides support for
RDF.
Mozilla supports site
maps in RDF, as well
as bookmarks and
history lists
See Netscape's or
HotWired home page
for a link to the RDF
file.
Trusted
3rd
Party
Metadata
Embedded
Metadata
e.g.
sitemaps
Image from http://purl.oclc.org/net/eric/talks/www7/devday/Image from http://purl.oclc.org/net/eric/talks/www7/devday/
19. 19
Deployment Issues
Various interesting new technologies have
been outlined
How can they be deployed in our environment?
Should we:
• Ignore them?
• Accept them fully?
• Accept them partly?
20. 20
Ignore New Developments
We can chose to ignore new developments,
and continue to use HTML 3.2:
Safe option, with no new training, support or
software costs
Experience in effectiveness, limitations, etc.
Fails to address current performance problems
Fails to address accessibility problems
Fails to provide new functionality
Service likely to look "old-fashioned" compared
with competition
21. 21
Fully Accept New Developments
Can chose to more fully to, say, HTML 4.0 and
CSS 2.0:
Can be exciting to be at leading edge
Performance benefits
Accessibility benefits
Based on open-standards
Provides motivation for users to upgrade browsers
Likely to be solution at some point (cf. Gopher)
Backwards compatibility problems with old browsers
Costly to deploy new authoring news, training, ..
Likely to be bugs and incompatibilities with new tools
and browsers
22. 22
Implement "Safe" Solutions
An alternative is to use "safe" technologies
which are backwards compatible and avoid
major browser bugs
Attractive sounding compromise position
Lose some functionality, but not all
Can be difficult or expensive to find "safe" options
(does .margin-left work on IE on SGI?)
Tools may not allow safe options to be chosen
Lack of validation tools for checking conformance
with restricted set of specification
Note See <URL: www.webreview.com/guides/
style/insafegrid.htm> for unsafe CSS 2.0 properties
23. 23
Decision Time
Which would you opt for?
Stick with current technologies
Cheap, default option. Continuation of
performance and accessibility problems.
Unlikely to be long term solution.
Deploy new technologies
More expensive option. Functionality,
performance and accessibility benefits. Access
problems for old browsers.
Use "safe" new technologies
May require home-grown tools and support.
Avoids some of the problems of other solutions
24. 24
An Alternative
An alternative approach to deploying new
technologies is available:
• Use more intelligent server-side software
• Use "proxies" to address limitations of
browser technologies. The term intermediary
was used in a paper [1] at the WWW 7
conference to describe this approach
• Protocol solutions, such as Transparent
Content Negotiation (TCN)
[1] "Intermediaries: New Places For Producing and
Manipulating Web Content"
25. 25
Intelligent Server Software
Simple model:
• Server receives request for resource
• Server delivers resource to client
More sophisticated model:
• Server receives request for resource
• Server processes header information from client
• Server delivers resource to client based on client
information
This is referred to as browser-sniffing or user-agent
negotiation
Note that server support is now available in Apache and
in server add-ons such as PHP/FI and MS Active
Server Pages (ASP)
26. 26
Portion of CSS file for IE
Total 797 lines
W3C CSS Gallery
W3C have a link to a core
style sampler service.
The service provides 8 core
style sheets which can be
freely linked to.
The style sheets use "browser
sniffing". Different style
sheets are delivered to
different browsers.
H1, H2, H3, H4, H5, H6, ..
{color: black;
background: white}
Portion of CSS file for Netscape
Total 169 lines
H1
{font-family: Tahoma, ...
font-size-adjust: .53;
margin-top: 1.33em;
font-weight: 500; ...}
27. 27
Java Intermediaries
Netscape and Internet
Explorer don't support
MathML
Who cares? MathML
Java renderers are
available
This concept can be
generalised to deploying
support for other new
markup languages.
For example see the
Displets work at
http://www.cs.unibo
.it/~fabio/displet/
28. 28
Deploying URNs
Problem
Today's browsers can't process URNs, such as:
urn:doi:10.1000/1
Possible Solution
• A separate program could resolve URNs into URLs
• Andy Powell (UKOLN) has demonstrated use of
Netscape's autoproxy to pass on URNs of the
format above to Squid for resolution [1]
• Example of use of an intermediary to deploy new
technologies not supported by current browsers
[1] "Resolving DOI Based URNs Using Squid" at
http://mirrored.ukoln.ac.uk/lis-journals/
dlib/dlib/dlib/june98/06powell.html
29. 29
Intermediaries
Intermediaries:
• Enable new functionality to be introduced to the
web without extending the client or the server
• Intermediaries can be implemented using proxies
• Intermediaries can be used for applications such
as web personalisation, document caching,
content distillation and protocol extension
• Demonstration available using WBI (Web Browser
Intelligence)
• See <URL: http://wwwcssrv.almaden.
ibm.com/wbi/>
• Another example for web accessibility at <URL:
http://www.inf.ethz.ch/department/IS/ea/blinds/>
30. 30
Web Applications
An Example
• We're familiar with HTML
validation services
(e.g. HENSA mirror)
• We can "go there" and use the service
• We can also have a link from the page which
will run the service (rather than just go to the
form)
• Consider:
– Web page is in Bath
– User is in Sheffield
– Application is in Kent
• An example of a web (intermediary?)
application
31. 31
Examples
Examples of remote web
applications include:
• Link checking
• Website analysis
• Document format
conversion
• Accessibility support
Imagine an intermediary
service which called an
XML - HTML conversion
service if the browser agent
didn't support XML
http://www.ukoln.ac.uk/web-focus/
webwatch/services/url-info/
http://wheel.compose.cs.cmu.edu:8001/
cgi-bin/browse/objweb
32. 32
Content Negotiation
Transparent Content Negotiation (TCN):
• Method of deploying new formats
Client:
ACCEPT image/gif, image/png
Server:
If foo.png exists, send, else foo.gif
• Used for logos on W3C website
• Not widely deployed
Transparent Feature Negotiation:
• Proposal for deploying new HTML elements
• Over-engineered? Requires naming authority
33. 33
Fourth and Fifth Ways
Several other options for deploying new web
technologies (e.g. on low spec PCs):
Run Browser on Server
• Use Windows Terminal Server, Citrix, etc.
• Browser runs on NT server
Deploy JavaPC (e.g. for DOS)
• Use the JavaPC and run HotJava browser (min.
spec 486 PC with 8Mb)
Opera
• Supports CSS, Frames, … on 486 PCs (8Mb)
• See <URL: http://www.operasoftware.com/>
34. 34
Conclusions
To conclude:
• New web protocols are still being developed
• Deployment of new technologies can be expensive
or time-consuming, but is likely to be needed
• Various deployment models:
Don't implement Implement fully
Implement via proxy Others (thin clients, …)
• We can't do it all ourselves
• Experience in developing (wide-area) web
applications will help in developing intermediaries