Microformats I: What & Why

The document discusses several options for publishing data on the Semantic Web. It describes Linked Data as the preferred approach, which involves using URIs to identify things and including links between related data to improve discovery. It also outlines publishing metadata in HTML documents using standards like RDFa and Microdata, as well as exposing SPARQL endpoints and data feeds.

This document discusses publishing content on the Semantic Web. It introduces basic concepts of RDF and the Semantic Web like resources, literals, and triples. It then describes six main ways to publish RDF data on the web: 1) standalone RDF documents, 2) metadata inside webpages using techniques like RDFa, 3) SPARQL endpoints, 4) feeds, 5) XSLT transformations, and 6) automatic markup tools. Finally, it briefly discusses the history of embedding metadata in HTML and examples of metadata standards.

The document discusses different options for publishing metadata on the Semantic Web, including standalone RDF documents, embedding metadata in web pages using techniques like RDFa, providing SPARQL endpoints, publishing feeds, and using automated tools. It provides examples and discusses the advantages of each approach. A brief history of metadata publishing efforts is also presented, from early initiatives like HTML meta tags and SHOE to current standards like RDFa and microformats.

The document discusses developing Linked Data and Semantic Web applications. It begins with key concepts related to Linked Data, the Semantic Web, and applications. It then describes two key steps in developing such applications: publishing data as Linked Data and consuming Linked Data to build applications. Examples are provided of extracting, enriching, and linking different datasets to build a real estate recommendation application that performs semantic searches over the integrated data. Ontologies are created and reused to represent the domains and support interoperability. The document emphasizes integrating the data and software engineering perspectives in developing Semantic Web applications.

This document discusses the need for named graphs in RDF to represent contextual information like provenance and source of RDF data. It proposes extensions to the RDF/XML syntax to associate RDF descriptions and statements with named graphs. This allows modeling things like different hypotheses, temporal aspects, points of view, and distributed storage in a way that is currently not possible without named graphs in the RDF model.

This is a one hour talk introducing Linked Data and how Linked Data can be consumed by humans and by machines through SPARQL

This document introduces linked data and discusses how publishing data as linked RDF triples on the web allows for a global linked database. It explains that linked data uses HTTP URIs to identify things and links data from different sources to be queried using SPARQL. Publishing linked data provides benefits like being able to integrate and discover related data on the web. Tools are available to convert existing data or publish new data as linked open data.

The document discusses a webinar presented by NISO and DCMI on Schema.org and Linked Data. The webinar provides an overview of Schema.org and Linked Data, examines the advantages and challenges of using RDF and Linked Data, looks at Schema.org in more detail, and discusses how Schema.org and Linked Data can be combined. The goals of the webinar are to illustrate the different design choices for identifying entities and describing structured data, integrating vocabularies, and incentives for publishing accurate data, as well as to help guide adoption of Schema.org and Linked Data approaches.

This document provides an overview of describing web resources using the Resource Description Framework (RDF). It discusses the basic concepts of RDF including resources, properties, statements, and the XML syntax used to represent them. It also covers RDF Schema which adds vocabulary for describing properties and classes of RDF resources, and provides a critical view of some aspects of RDF such as its use of binary predicates and treatment of properties.

This presentation was provided by Ashley Clark, Northeastern University, during a NISO Virtual Conference on the topic of data curation, held on Wednesday, August 31, 2016

This document provides an agenda and schedule for Monday's Linked Open Data class. The day includes introductions, sessions on introducing linked data and exploring use cases, breaks for discussion, and a concluding session on kicking off participant projects. Evening events include an outside lecture and networking social for graduate students.

The document discusses using linked open data and linked data principles for libraries. It covers key concepts like URIs, RDF triples, ontologies and vocabularies. It then outlines options for libraries to both consume and publish linked data, such as enriching existing catalog data by linking to external sources, creating new information aggregates, and publishing library holdings and metadata as linked open data. Challenges include a lack of common identifiers, FRBRization of existing data, and the need for content curation and new technical systems to fully realize the benefits of linked open data for libraries.

This document discusses different ways that humans can consume linked data on the web. It describes HTML browsers that can render RDFa embedded in web pages. It also discusses linked data browsers that allow users to view RDF triples in a tabular format. Faceted browsers provide a way to explore linked data through interactive facets. On-the-fly mashups dynamically combine data from multiple sources. The document encourages the development of new and innovative interfaces for interacting with linked data.

Libraries around the world have a long tradition of maintaining authority files to assure the consistent presentation and indexing of names. As library authority files have become available online, the authority data has become accessible -- and many have been published as Linked Open Data (LOD) -- but names in one library authority file typically had no link to corresponding records for persons and organizations in other library authority files. After a successful experiment in matching the Library of Congress/NACO authority file with the German National Library's authority file, an online system called the Virtual International Authority File was developed to facilitate sharing by ingesting, matching, and displaying the relations between records in multiple authority files. The Virtual International Authority File (VIAF) has grown from three source files in 2007 to more than two dozen files today. The system harvests authority records, enhances them with bibliographic information and brings them together into clusters when it is confident the records describe the same identity. Although the most visible part of VIAF is a HTML interface, the API beneath it supports a linked data view of VIAF with URIs representing the identities themselves, not just URIs for the clusters. It supports names for person, corporations, geographic entities, works, and expressions. With English, French, German, Spanish interfaces (and a Japanese in process), the system is used around the world, with over a million queries per day. Speaker Thomas Hickey is Chief Scientist at OCLC where he helped found OCLC Research. Current interests include metadata creation and editing systems, authority control, parallel systems for bibliographic processing, and information retrieval and display. In addition to implementing VIAF, his group looks into exploring Web access to metadata, identification of FRBR works and expressions in WorldCat, the algorithmic creation of authorities, and the characterization of collections. He has an undergraduate degree in Physics and a Ph.D. in Library and Information Science.

The document discusses using picture-driven computing as an assistive technology to improve accessibility. It describes using visual images instead of text inputs to allow indirect access for users with disabilities. The Sikuli platform is highlighted as a way to automate tasks by programming screenshots of graphical interfaces. Future work areas include more research on picture-driven approaches, evaluating Sikuli, and developing additional assistive technology scripts.

Come join us downstairs at the Proof Brewing Company for another excellent evening of inspiration! Rachael Moore, the front-end lead on the new remax.com, has kindly agreed to share the story and take a peek under the hood of this massive (and really nicely done) site. Among the likely topics of discussion are: Object-oriented CSS, CSS preprocessors, JavaScript frameworks, and the ins and outs of working with a distributed team.

Modern UI Component libraries influenced by Web Components will rely more heavily on package management than last generation UI Frameworks. In this 15 minute session we'll introduce package management for web graphical user interfaces, talk about the best package contents for a UI component, and some tactics for making smooth releases. For video, skip to 57 minutes, 13 seconds (57:13), http://www.youtube.com/watch?v=BhP86d5IiM4&t=57m13s

Linting, testing, distribution, deployment--and all the associated tooling and tracking. The learning curve on all this stuff can be pretty harsh for web UI developers. All the vocabulary. All the options. All the extra code. What does it all mean? And what, if anything, does your project need? In this talk I discuss web user interfaces at scale and the benefits of bringing more of DevOps culture to the UI space, combining introductory material with practical applications. Talk presented at CSSConf in June 2015.