This document provides an overview of XLinks, which define linking between XML documents. It discusses that XLinks have two parts - XLink defines links between documents, while XPointer defines addressing within documents. The document then explores simple XLinks, which are similar to HTML links, including using XLink attributes and describing both local and remote resources. It also discusses extended XLinks and link behavior attributes that provide more functionality than HTML links.
School of Data - mapping company networksTony Hirst
The document provides instructions for summarizing corporate ownership data from OpenCorporates using the OpenRefine and Gephi tools. It explains how to download company relationship data from OpenCorporates in JSON format, import it into OpenRefine to clean and organize the data into a tabular format, then visualize the networks in Gephi. The goal is to analyze and display corporate ownership connections in a meaningful way.
School Of Data - mapping opencorporates networks using openrefine and GephiTony Hirst
This document provides a two-part recipe for mapping corporate networks from OpenCorporates data using OpenRefine and Gephi. It explains how to download ownership data from OpenCorporates, clean and structure it in OpenRefine, then import it into Gephi to visualize the network and relationships. Key steps include adding "/network.json?depth=2" to the company URL to grab its network data, structuring the data in OpenRefine with "Parent" and "Child" columns, then importing it into Gephi as an edges table to layout, color and analyze the network.
Anchors are special tags that create connections between documents using the <A> tag. Anchors contain hypertext references that appear as underlined hotspot text to link to other targets or documents when clicked. The href attribute specifies the target resource, with # used for internal links and file paths for external links. Relationships between linked documents are defined using rel and rev attributes to describe the directionality of the connection.
This document provides instructions for using OpenRefine to retrieve director information from OpenCorporates given a company ID or URL. It describes creating URLs to call the OpenCorporates API, parsing the JSON response to extract director details, formatting the data with delimiters, splitting it into rows for each director while copying related company fields, and renaming columns for clarity. The overall process transforms API data into a clean table of directors linked to their companies.
This document discusses corporate data and network visualizations. It provides examples of network maps showing the interconnections between companies in a corporate group like Royal Dutch Shell. These maps are generated from simple data sets listing connections between companies. The document explains that complex networks can be built from basic data and introduces Gephi as a tool for generating network visualizations from data files.
Mapping Corporate Networks With OpenCorporatesTony Hirst
This document discusses using open company data from OpenCorporates to map corporate networks and structures. It introduces the concept of mapping relationships between companies and directors to identify "corporate sprawls" - groups of companies connected by shared directors. The document demonstrates how to construct these maps by starting with seed companies and snowballing to find other connected companies. It shows how these maps can be analyzed and visualized, for example to identify important companies or directors. Further opportunities discussed include adding geographical and temporal dimensions to the analysis.
This document provides an overview of creating effective web pages. It defines HTML and describes how to plan and structure an HTML document using basic tags like headings, paragraphs, and lists. It also explains how to add images and links to a web page. The document examines tools for web site creation and optimization techniques like search engine submission and search engine optimization.
This document provides summaries of HTML tags and elements in 3 sentences or less. It covers common tags for document structure like <head>, <body>, and <html>. It also covers text formatting tags, multimedia tags, form elements, and interactive elements. The summaries are concise explanations of each element's purpose and basic usage.
School of Data - mapping company networksTony Hirst
The document provides instructions for summarizing corporate ownership data from OpenCorporates using the OpenRefine and Gephi tools. It explains how to download company relationship data from OpenCorporates in JSON format, import it into OpenRefine to clean and organize the data into a tabular format, then visualize the networks in Gephi. The goal is to analyze and display corporate ownership connections in a meaningful way.
School Of Data - mapping opencorporates networks using openrefine and GephiTony Hirst
This document provides a two-part recipe for mapping corporate networks from OpenCorporates data using OpenRefine and Gephi. It explains how to download ownership data from OpenCorporates, clean and structure it in OpenRefine, then import it into Gephi to visualize the network and relationships. Key steps include adding "/network.json?depth=2" to the company URL to grab its network data, structuring the data in OpenRefine with "Parent" and "Child" columns, then importing it into Gephi as an edges table to layout, color and analyze the network.
Anchors are special tags that create connections between documents using the <A> tag. Anchors contain hypertext references that appear as underlined hotspot text to link to other targets or documents when clicked. The href attribute specifies the target resource, with # used for internal links and file paths for external links. Relationships between linked documents are defined using rel and rev attributes to describe the directionality of the connection.
This document provides instructions for using OpenRefine to retrieve director information from OpenCorporates given a company ID or URL. It describes creating URLs to call the OpenCorporates API, parsing the JSON response to extract director details, formatting the data with delimiters, splitting it into rows for each director while copying related company fields, and renaming columns for clarity. The overall process transforms API data into a clean table of directors linked to their companies.
This document discusses corporate data and network visualizations. It provides examples of network maps showing the interconnections between companies in a corporate group like Royal Dutch Shell. These maps are generated from simple data sets listing connections between companies. The document explains that complex networks can be built from basic data and introduces Gephi as a tool for generating network visualizations from data files.
Mapping Corporate Networks With OpenCorporatesTony Hirst
This document discusses using open company data from OpenCorporates to map corporate networks and structures. It introduces the concept of mapping relationships between companies and directors to identify "corporate sprawls" - groups of companies connected by shared directors. The document demonstrates how to construct these maps by starting with seed companies and snowballing to find other connected companies. It shows how these maps can be analyzed and visualized, for example to identify important companies or directors. Further opportunities discussed include adding geographical and temporal dimensions to the analysis.
This document provides an overview of creating effective web pages. It defines HTML and describes how to plan and structure an HTML document using basic tags like headings, paragraphs, and lists. It also explains how to add images and links to a web page. The document examines tools for web site creation and optimization techniques like search engine submission and search engine optimization.
This document provides summaries of HTML tags and elements in 3 sentences or less. It covers common tags for document structure like <head>, <body>, and <html>. It also covers text formatting tags, multimedia tags, form elements, and interactive elements. The summaries are concise explanations of each element's purpose and basic usage.
This document discusses how to add inline images and embed audio/video on web pages. It describes the <img> and <embed> tags used to insert these elements. Key attributes for images include src, align, height, width, and alt, while attributes for embedded content include src, width, height, alt, autostart, volume, and controls. The document asks review questions about image file types and unsupported file formats for web pages.
XML and HTML have some key differences - XML provides user-definable tags while HTML has a defined set of tags for web display. XML is content-driven and end tags are essential, whereas HTML is format-driven and end tags are not always required. XML also requires quotes around attribute values and a slash in empty tags.
The document discusses an opportunity to own a telecommunications business through a large North American company that is expanding into new countries. It notes that the company is endorsed by Robert Kiyosaki and Donald Trump and was featured on Celebrity Apprentice. It asks if the reader would be interested in earning residual income every time people pay their phone bills and suggests attending a free business presentation to learn more about investing in this opportunity.
The document provides information on common file formats for images, audio, and video. For images, it discusses JPEG, GIF, PNG, and BMP formats. For audio, it covers MP3, WMA, WAV, MIDI, and CDA formats. And for video, it details WMV, 3GP, AVI, MP4, FLV, MOV, SWF, and ASF formats. Each file format is described in terms of its filename extension and key features.
This document provides instructions for adding hyperlinks in blog posts. It defines a hyperlink as highlighted text or images that link to other locations or files when clicked. It explains that hyperlinks allow text to transport the reader to another site or page. The document then provides step-by-step instructions for highlighting text and inserting the URL to create a hyperlink in Word documents or blog posts, making sure the link opens in a new window so readers return to the original site.
The document discusses HTML link tags, which allow users to jump to new documents or sections with a click. Link tags are written as <a href="url">Link Text</a> and can open the linked document in the same window or a new window depending on whether the target attribute is used. Images can also be used as links to provide a more visually interesting browsing experience than plain text links.
The document discusses different types of links in HTML, including page jumps within a document, links to other pages on the same site, and links to external websites. It covers how to create links using text, buttons, and images. Specific code examples are provided to demonstrate how to make internal page jumps within the document using anchors, link to other files on the same site, and link to external URLs. The document also explains some of the attributes used in link code like href, name, method, action, type, and value.
XPointers define an addressing scheme for individual parts of an XML document. Some key absolute location terms in XPointers are:
- root() - selects the root element of the document
- id() - selects the element with the given ID attribute value
- descendant() - selects descendants of a given element by depth and name
- following() - selects elements following another in document order
These location terms can be used in XPointers appended to URLs to precisely select a particular element or part of an XML document to link to.
XHTML is a markup language that provides structure and semantics to web pages. It is based on XML and is more strict than HTML. XHTML pages must have a document type definition, html and head tags, and a body where the visible content goes. Common XHTML tags include paragraphs, lists, links, images, and divisions to logically separate content. While XHTML provides structure, CSS is used to style pages and control visual presentation through rules that target specific XHTML elements.
XHTML is a markup language that provides structure and semantics to web pages. It is based on XML and is more strict than HTML. XHTML pages must have a document type definition, html and head tags, and a body where the visible content goes. Common XHTML tags include paragraphs, lists, links, images, and divisions to logically separate content. While XHTML provides structure, CSS is used to style pages and control visual presentation by defining rules for tags. CSS rules are defined in external style sheets to keep presentation separate from structure and content.
This document provides an overview of HTML including:
- What HTML is and where it originated from as a markup language.
- The basic syntax and structure of HTML documents including elements, attributes, nesting, and semantic markup.
- Key HTML elements like headings, links, and images and how to reference external resources.
- A brief history of HTML standards development from HTML to XHTML to HTML5.
This document is a group assignment submitted by 6 students from Assosa University in Ethiopia on May 26, 2013. It provides information on HTML, XHTML, XML, and summarizes key differences between these markup languages. HTML is for creating web pages, XHTML is a stricter version of HTML, and XML is a generic markup language that allows users to define their own tags for transporting and storing data.
The document summarizes XML Linking, which is developing specifications to enable more advanced hypertext functionality on the web. It examines goals and approaches, describes HTML linking limitations that XML Linking seeks to overcome, and surveys key specifications including XPath, XPointer, and XLink. These specifications aim to provide a standard way to address portions of resources, support external and bidirectional links, and separate linking structure from behavior.
Hypertext Markup Language (HTML) is the standard markup language used to create web pages. HTML uses tags like <h1> and </h1> to define headings, paragraphs, and other elements. A web browser can read HTML files and display them as web pages by interpreting the HTML tags but not displaying them. HTML describes the structure and layout of content on a website.
This document provides an overview of HTML and its evolution. It discusses:
1. The origins and purpose of HTML as a markup language used to annotate documents and control text layout.
2. Key changes and versions of HTML including XHTML for stricter syntax, and HTML5 which aims to make HTML a living language and improve backwards compatibility.
3. Semantic HTML elements that describe the structural meaning of content rather than presentation. This improves accessibility, searchability, and maintainability of documents.
4. The basic structure of HTML documents including the DOCTYPE, head, body, titles, and use of external stylesheets and scripts.
5. Common HTML elements like headings, paragraphs, links
The document provides an overview of HTML including:
1) A brief history of HTML from its origins in the 1960s through its standardization by the W3C in the late 1990s.
2) An explanation of HTML syntax including tags, elements, attributes, and nesting.
3) A discussion of semantic markup and its advantages over presentation-oriented markup.
4) A description of the basic structure of an HTML document including the DOCTYPE, html, head, and body elements.
5) A quick tour of common HTML elements like headings, paragraphs, links, and divisions.
XLink is an XML standard for creating hyperlinks within and between XML documents. It allows any XML element to act as a link and supports both simple and extended links defined outside linked files. XPointer uses XPath expressions to point to specific parts of an XML document, like a particular element, and allows for more precise targeting than regular HTML links. An example shows how XLink creates simple links between images using attributes like xlink:type, xlink:href, and xlink:show, while XPointer could link to a specific dog element using its XPath.
There are two types of hyperlinks: internal and external. An internal hyperlink links to other parts of the same webpage, and is created using the <A> tag. The HREF attribute specifies the destination within the webpage, and the HREF and NAME attributes must have the same value. Students learned about identifying hyperlinks and creating internal hyperlinks to navigate within a webpage. They were assigned an exercise to create internal links in an HTML file.
XML (Extensible Markup Language) is a universal standard for data representation that allows users to define their own tags. It is used to mark up data so it can be processed by computers, while HTML is used to display information to users. Key benefits of XML include simplicity, openness, extensibility, self-description, and separating content from presentation. XML documents have a tree structure and can be well-formed, meaning they follow basic syntax rules, or valid, meaning they conform to predefined structure rules using DTDs or schemas.
Lecture 4: A Short Introduction to the Semantic Web6500jmk4
The document discusses the Semantic Web and linked data. It explains that the Semantic Web aims to add meaning to the web by linking data using Resource Description Framework (RDF) triples that define relationships between subjects and objects. Each part of an RDF triple has a unique identifier, unlike hyperlinks which just connect objects without defining their relationship. The Semantic Web seeks to provide a more precise way of describing and linking information across the web through the use of RDF triples.
This presentation is about the Basic Concepts of XML EXtensible Markup Language. The importance of these concepts is explained in this presentation. XML is one of the popular Markup Languages today.
XML is a markup language that allows for the creation of structured documents. It is characterized by specific tags rather than generic tags, an infinite number of possible tags rather than a finite set, and structure rather than presentation. XML documents must be well-formed, following syntax rules for proper nesting and closing of tags. They may also be valid, referencing a DTD that defines the elements and attributes allowed. XML enables data exchange across different systems and self-describes the structure and meaning of data tags.
This document discusses how to add inline images and embed audio/video on web pages. It describes the <img> and <embed> tags used to insert these elements. Key attributes for images include src, align, height, width, and alt, while attributes for embedded content include src, width, height, alt, autostart, volume, and controls. The document asks review questions about image file types and unsupported file formats for web pages.
XML and HTML have some key differences - XML provides user-definable tags while HTML has a defined set of tags for web display. XML is content-driven and end tags are essential, whereas HTML is format-driven and end tags are not always required. XML also requires quotes around attribute values and a slash in empty tags.
The document discusses an opportunity to own a telecommunications business through a large North American company that is expanding into new countries. It notes that the company is endorsed by Robert Kiyosaki and Donald Trump and was featured on Celebrity Apprentice. It asks if the reader would be interested in earning residual income every time people pay their phone bills and suggests attending a free business presentation to learn more about investing in this opportunity.
The document provides information on common file formats for images, audio, and video. For images, it discusses JPEG, GIF, PNG, and BMP formats. For audio, it covers MP3, WMA, WAV, MIDI, and CDA formats. And for video, it details WMV, 3GP, AVI, MP4, FLV, MOV, SWF, and ASF formats. Each file format is described in terms of its filename extension and key features.
This document provides instructions for adding hyperlinks in blog posts. It defines a hyperlink as highlighted text or images that link to other locations or files when clicked. It explains that hyperlinks allow text to transport the reader to another site or page. The document then provides step-by-step instructions for highlighting text and inserting the URL to create a hyperlink in Word documents or blog posts, making sure the link opens in a new window so readers return to the original site.
The document discusses HTML link tags, which allow users to jump to new documents or sections with a click. Link tags are written as <a href="url">Link Text</a> and can open the linked document in the same window or a new window depending on whether the target attribute is used. Images can also be used as links to provide a more visually interesting browsing experience than plain text links.
The document discusses different types of links in HTML, including page jumps within a document, links to other pages on the same site, and links to external websites. It covers how to create links using text, buttons, and images. Specific code examples are provided to demonstrate how to make internal page jumps within the document using anchors, link to other files on the same site, and link to external URLs. The document also explains some of the attributes used in link code like href, name, method, action, type, and value.
XPointers define an addressing scheme for individual parts of an XML document. Some key absolute location terms in XPointers are:
- root() - selects the root element of the document
- id() - selects the element with the given ID attribute value
- descendant() - selects descendants of a given element by depth and name
- following() - selects elements following another in document order
These location terms can be used in XPointers appended to URLs to precisely select a particular element or part of an XML document to link to.
XHTML is a markup language that provides structure and semantics to web pages. It is based on XML and is more strict than HTML. XHTML pages must have a document type definition, html and head tags, and a body where the visible content goes. Common XHTML tags include paragraphs, lists, links, images, and divisions to logically separate content. While XHTML provides structure, CSS is used to style pages and control visual presentation through rules that target specific XHTML elements.
XHTML is a markup language that provides structure and semantics to web pages. It is based on XML and is more strict than HTML. XHTML pages must have a document type definition, html and head tags, and a body where the visible content goes. Common XHTML tags include paragraphs, lists, links, images, and divisions to logically separate content. While XHTML provides structure, CSS is used to style pages and control visual presentation by defining rules for tags. CSS rules are defined in external style sheets to keep presentation separate from structure and content.
This document provides an overview of HTML including:
- What HTML is and where it originated from as a markup language.
- The basic syntax and structure of HTML documents including elements, attributes, nesting, and semantic markup.
- Key HTML elements like headings, links, and images and how to reference external resources.
- A brief history of HTML standards development from HTML to XHTML to HTML5.
This document is a group assignment submitted by 6 students from Assosa University in Ethiopia on May 26, 2013. It provides information on HTML, XHTML, XML, and summarizes key differences between these markup languages. HTML is for creating web pages, XHTML is a stricter version of HTML, and XML is a generic markup language that allows users to define their own tags for transporting and storing data.
The document summarizes XML Linking, which is developing specifications to enable more advanced hypertext functionality on the web. It examines goals and approaches, describes HTML linking limitations that XML Linking seeks to overcome, and surveys key specifications including XPath, XPointer, and XLink. These specifications aim to provide a standard way to address portions of resources, support external and bidirectional links, and separate linking structure from behavior.
Hypertext Markup Language (HTML) is the standard markup language used to create web pages. HTML uses tags like <h1> and </h1> to define headings, paragraphs, and other elements. A web browser can read HTML files and display them as web pages by interpreting the HTML tags but not displaying them. HTML describes the structure and layout of content on a website.
This document provides an overview of HTML and its evolution. It discusses:
1. The origins and purpose of HTML as a markup language used to annotate documents and control text layout.
2. Key changes and versions of HTML including XHTML for stricter syntax, and HTML5 which aims to make HTML a living language and improve backwards compatibility.
3. Semantic HTML elements that describe the structural meaning of content rather than presentation. This improves accessibility, searchability, and maintainability of documents.
4. The basic structure of HTML documents including the DOCTYPE, head, body, titles, and use of external stylesheets and scripts.
5. Common HTML elements like headings, paragraphs, links
The document provides an overview of HTML including:
1) A brief history of HTML from its origins in the 1960s through its standardization by the W3C in the late 1990s.
2) An explanation of HTML syntax including tags, elements, attributes, and nesting.
3) A discussion of semantic markup and its advantages over presentation-oriented markup.
4) A description of the basic structure of an HTML document including the DOCTYPE, html, head, and body elements.
5) A quick tour of common HTML elements like headings, paragraphs, links, and divisions.
XLink is an XML standard for creating hyperlinks within and between XML documents. It allows any XML element to act as a link and supports both simple and extended links defined outside linked files. XPointer uses XPath expressions to point to specific parts of an XML document, like a particular element, and allows for more precise targeting than regular HTML links. An example shows how XLink creates simple links between images using attributes like xlink:type, xlink:href, and xlink:show, while XPointer could link to a specific dog element using its XPath.
There are two types of hyperlinks: internal and external. An internal hyperlink links to other parts of the same webpage, and is created using the <A> tag. The HREF attribute specifies the destination within the webpage, and the HREF and NAME attributes must have the same value. Students learned about identifying hyperlinks and creating internal hyperlinks to navigate within a webpage. They were assigned an exercise to create internal links in an HTML file.
XML (Extensible Markup Language) is a universal standard for data representation that allows users to define their own tags. It is used to mark up data so it can be processed by computers, while HTML is used to display information to users. Key benefits of XML include simplicity, openness, extensibility, self-description, and separating content from presentation. XML documents have a tree structure and can be well-formed, meaning they follow basic syntax rules, or valid, meaning they conform to predefined structure rules using DTDs or schemas.
Lecture 4: A Short Introduction to the Semantic Web6500jmk4
The document discusses the Semantic Web and linked data. It explains that the Semantic Web aims to add meaning to the web by linking data using Resource Description Framework (RDF) triples that define relationships between subjects and objects. Each part of an RDF triple has a unique identifier, unlike hyperlinks which just connect objects without defining their relationship. The Semantic Web seeks to provide a more precise way of describing and linking information across the web through the use of RDF triples.
This presentation is about the Basic Concepts of XML EXtensible Markup Language. The importance of these concepts is explained in this presentation. XML is one of the popular Markup Languages today.
XML is a markup language that allows for the creation of structured documents. It is characterized by specific tags rather than generic tags, an infinite number of possible tags rather than a finite set, and structure rather than presentation. XML documents must be well-formed, following syntax rules for proper nesting and closing of tags. They may also be valid, referencing a DTD that defines the elements and attributes allowed. XML enables data exchange across different systems and self-describes the structure and meaning of data tags.
XML is a markup language that defines rules for encoding documents in a human- and machine-readable format. It allows users to define their own elements and tags to structure data. Some key benefits of XML include its extensibility, ability to carry data independently of presentation, and status as a public standard. While XML provides structure and organization, it does not perform computations or specify how data should be displayed.
Html for beginners. A basic information of html for beginners. A more depth coverage of html and css will be covered in the future presentations. visit my sites http://technoexplore.blogspot.com and http://hotjobstuff.blogspot.com for some other important presentations.
Xml For Dummies Chapter 4 Adding Xhtml For The Webphanleson
XML For Dummies provides information on converting documents from HTML to XHTML by following XML syntax rules. It discusses the key differences between HTML and XML, and how XHTML combines aspects of both. The chapter emphasizes that XHTML documents must use XML syntax like closing all tags, properly nesting tags, using lowercase for all tags and attributes, and putting quotation marks around attribute values. It also stresses the importance of including a DOCTYPE declaration to enable validation and proper rendering of XHTML pages.
This document defines terms related to e-books and XML, including formats like EPUB, tags, schemas, and other technical aspects of digital publishing. It provides concise definitions for over 50 common terms in just a few sentences each, serving as a handy reference for those working with electronic books and documents marked up in XML.
This document defines terms related to e-books and XML. It provides concise definitions for over 50 key terms, including formats like ePub, DocBook and DTBook; standards like XML, XHTML and CSS; and concepts like digital rights management (DRM), metadata, and open access publishing. The full glossary contains over 100 terms and is available online on the AAUP Wiki.
Share point 2013 coding standards and best practices 1.0LiquidHub
This document provides coding standards and best practices for developing SharePoint applications. It discusses efficient use of SharePoint data and objects, including caching objects and handling multithreaded environments. Specific recommendations are given for working with folders, lists, and deleting multiple versions of list items. The document also covers writing applications that scale to large numbers of users and using SPQuery objects. Best practices for disposing objects, exception handling, and accessing web and site objects are also outlined.
The document outlines the SharePoint 2013 upgrade process from SharePoint 2010 in three main steps:
1. Prepare the 2010 and 2013 farms by gathering information, cleaning up 2010, and setting up 2013.
2. Upgrade databases by copying them from 2010 to 2013, upgrading service application databases, and creating web applications before upgrading content databases.
3. Upgrade sites by running health checks, creating an evaluation site, and upgrading site collections after verifying readiness.
SharePoint 2013 introduced new features like apps, social capabilities and improved search compared to SharePoint 2010. It moved to a new app model and deprecated sandbox solutions and visual upgrades. Several site templates were also removed like Document Workspace, Personalization Site and Meeting Workspaces to simplify template selection. Existing sites created with these templates will still function in SharePoint 2013 but may not be supported in future releases.
The document discusses new user interface features in SharePoint 2010, including the ribbon interface, status bar, notifications, dialog framework, improved page model, master pages, theming engine, and extensibility of these features. The ribbon replaces the command surfaces of SharePoint 2007 and can be customized. The status bar and notifications provide feedback without page reloads. Dialogs load pages within iframes to reduce page transitions. Sites function as collections of pages. Themes allow changing the look and feel by applying color and font changes defined in theme files.
Microsoft office-sharepoint-server-2007-presentation-120211522467022-2LiquidHub
The document discusses the challenges faced by information workers and how collaboration and content management technologies can help address them. It notes that information workers spend a significant amount of time on emails, searching for information, and coordinating work across different locations. New technologies aim to simplify working together, improve access to information and insights, securely manage content, and streamline business processes. The Microsoft Office System provides a platform to address these issues through features in SharePoint for documents, tasks, calendars, blogs, wikis, email integration, and more.
SharePoint 2010 allows users to tag list items, documents, pages, and external pages to help organize information using a flexible taxonomy system. Tags can be added to anything with a URL to help categorize and find content. Users can tag list items, documents, and SharePoint pages to add keywords and notes for categorization purposes.
This presentation provides an overview of FAST Search for SharePoint 2010. It discusses the server roles, single and multi-server deployments, SharePoint search service applications, visual and conversational search capabilities, user context, comparisons to SharePoint search, ways to extend search, and lessons learned. The presentation was delivered by Jacob Wilson from Bross Group.
This document provides guidance on deploying Microsoft Office SharePoint Server 2007 in a server farm environment. It discusses the following key points:
- Server farm deployments involve multiple dedicated servers and provide better performance and scalability than a single-server deployment.
- The deployment process involves three phases - deploying and configuring server infrastructure, creating and configuring Shared Services Providers (SSPs), and deploying and configuring SharePoint sites.
- Server farm topologies can range from a small configuration with two servers, to a large configuration with clustered database servers and multiple application and frontend servers.
- Proper planning is important before deployment, including acquiring necessary credentials and accounts, installing prerequisites, and config
This document provides instructions for database administrators to pre-install databases required by Microsoft Office SharePoint Server 2007 before beginning the installation or creation of a Shared Services Provider (SSP). It describes creating databases with the correct collation and owners, configuring SQL Server, and running commands to configure the databases and create the SSP.
This document provides guidance on deploying Microsoft Office SharePoint Server 2007 in a server farm environment. It discusses hardware and software requirements, installing SharePoint on the first server, adding additional servers to the farm, configuring a shared services provider, and creating site collections and SharePoint sites. It also covers optional steps like pre-installing databases, configuring single sign-on, and configuring the trace log for troubleshooting.
This document discusses backup strategies for Microsoft Office SharePoint Server (MOSS) 2007. It examines the native MOSS 2007 backup tools including the Recycle Bin, Central Administration backup, and command-line backup. It finds that the native tools lack automation, granularity, and robustness. The document then introduces AvePoint's DocAve software as a third-party backup solution. DocAve provides item-level backup and restore capabilities to address the shortcomings of the native MOSS 2007 backup tools.
How To Configure Email Enabled Lists In Moss2007 Rtm Using Exchange 2003LiquidHub
This document provides step-by-step instructions for configuring incoming email for document libraries in SharePoint 2007 using Exchange 2003. It describes setting up an organizational unit in Active Directory, installing the SMTP service on the SharePoint server, configuring incoming email settings in Central Administration, creating an email-enabled document library, and testing. Troubleshooting tips are also provided to address issues like duplicate emails or problems with attachments.
The Business Data Catalog (BDC) is a framework included with SharePoint Enterprise that allows integration of line-of-business systems like SAP and Oracle into SharePoint sites without requiring custom code. The BDC uses metadata to define entities, properties, and methods to retrieve read-only data from external systems using web services or SQL. Administrators import BDC metadata to create applications that provide out-of-the-box techniques for displaying and searching external data within SharePoint sites.
The Business Data Catalog (BDC) is a framework in SharePoint Server 2007 Enterprise Edition that allows integration of line-of-business systems and databases without custom coding. It uses metadata to define entities, methods, and associations for connecting to and retrieving read-only data from external systems via web services or ADO.NET. Administrators import BDC metadata to create applications that provide data to SharePoint sites using out-of-the-box web parts, columns, search, and profiles synchronization. Programmers can also access BDC entities through the object model.
This document provides demonstration steps for exploring document storage, management, and collaboration features in Windows SharePoint Services 3.0. It outlines steps to edit documents, create and add documents to libraries, apply version control, view version history, restore previous versions from the recycle bin, and edit task tracking lists. The demonstrations are organized into sections on document storage and management, collaboration technologies, and information management and communication.
This document provides an overview of Module 01 which introduces the Windows SharePoint Services 3.0 platform. It discusses common collaboration challenges organizations face, reasons solutions often fail, and how WSS addresses key business needs. The module contains two lessons - the first on WSS and collaboration challenges, the second on collaboration technologies in WSS like document storage, collaboration features, and information management.
This document describes steps to create a web service that inserts data into a SQL database, create an InfoPath form to submit data to the web service, and publish and deploy the InfoPath form. It includes:
1) Code for a C# web service that inserts student records into a database
2) Instructions for running the web service and testing it works
3) Steps to create an InfoPath form with controls to enter student data
4) Configuring the form to submit data to the web service using the URL
5) Publishing and saving the form so it can be used to insert records
Whats New In Microsoft Windows Share Point Services Feature WalkthroughLiquidHub
This document provides an overview and instructions for a lab on the new and enhanced features in Windows SharePoint Services (version 3). The lab consists of 9 exercises that cover topics such as site creation, administration, permissions, web parts, navigation, security, notifications, and Outlook integration. Completing the lab will help users learn about the updated features in WSS. The estimated time to complete all the exercises is 90 minutes using the MOSS computer.
Overviewofthe2007 Microsoft Office System Components RefreshLiquidHub
This document provides an overview of the 2007 Microsoft Office system components lab. The lab includes exercises that describe enhancements in Word 2007 and Excel 2007 for formatting documents and spreadsheets. It also describes new features in other Office 2007 applications like PowerPoint, Outlook, Access, and InfoPath. The lab uses three virtual machines - a domain controller, file server, and client system - and takes approximately 90 minutes to complete. Exercises in the lab guide students through tasks like applying styles, themes, and conditional formatting in Word and Excel to enhance documents and analyze data.
Organizingand Finding Resourceswith Office Share Point Server2007 RefreshLiquidHub
This document provides an overview and objectives for a Microsoft Virtual Labs exercise on organizing and finding resources with Office SharePoint Server 2007. The exercise includes 4 tasks that cover portal management, content targeting, personal SharePoint sites, and using the Colleagues Web Part. Learners will manage sites and libraries, create audiences, target content, configure user profiles and privacy settings on personal sites, and view colleague information. The lab utilizes 3 virtual machines - a domain controller, SharePoint server, and client computer.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Things to Consider When Choosing a Website Developer for your Website | FODUUFODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
XML Bible
1. 16
CHAPTER
XLinks
✦ ✦ ✦ ✦
X LL (eXtensible Linking Language) is divided into two
In This Chapter
parts, XLinks and XPointers. XLink, the XML Linking
Language, defines how one document links to another
XLinks versus
document. XPointer, the XML Pointer Language, defines how
HTML links
individual parts of a document are addressed. XLinks point to
a URI (in practice, a URL) that specifies a particular resource.
Simple links
This URL may include an XPointer part that more specifically
identifies the desired part or section of the targeted resource
Extended links
or document. This chapter explores XLinks. The next chapter
explores XPointers.
Out-of-line links
Extended link groups
XLinks versus HTML Links
How to rename
The Web conquered the more established gopher protocol for XLink attributes
one main reason: It was possible to embed hypertext links in
documents. These links could embed images or let the user
✦ ✦ ✦ ✦
to jump from inside one document to another document or
another part of the same document. To the extent that XML
is rendered into other formats such as HTML for viewing,
the same syntax HTML uses for linking can be used in XML
documents. Alternate syntaxes can be converted into
HTML syntax using XSL, as you saw in several examples
in Chapter 14.
However, HTML linking has limits. For one thing, URLs
are mostly limited to pointing out a single document. More
granularity than that, such as linking to the third sentence of
the 17th paragraph in a document, requires you to manually
insert named anchors in the targeted file. It can’t be done
without write access to the document to which you’re linking.
Furthermore, HTML links don’t maintain any sense of history
or relations between documents. Although browsers may track
the path you’ve followed through a series of documents, such
tracking isn’t very reliable. From inside the HTML, there’s no
way to know from where a reader came. Links are purely one
way. The linking document knows to whom it’s linking, but not
vice versa.
2. 572 Part IV ✦ Supplemental Technologies
XLL is a proposal for more powerful links between documents. It’s designed
especially for use with XML documents, but some parts can be used with HTML
files as well. XLL achieves everything possible with HTML’s URL-based hyperlinks
and anchors. Beyond this, however, it supports multidirectional links where the
links run in more than one direction. Any element can become a link, not just the
A element. Links do not even have to be stored in the same file as the documents
they link. Furthermore, the XPointer part (described in the next chapter) allows
links to arbitrary positions in an XML document. These features make XLL
more suitable not only for new uses, but for things that can be done only with
considerable effort in HTML, such as cross-references, footnotes, end notes,
interlinked data, and more.
I should warn you that at the time of this writing (spring, 1999), XLL is still undergo-
Caution
ing significant development and modification. Although it is beginning to stabilize,
some bits and pieces likely will change by the time you read this.
Furthermore, there are no general-purpose applications that support arbitrary
XLinks. That’s because XLinks have a much broader base of applicability than
HTML links. XLinks are not just used for hypertext connections and embedding
images in documents. They can be used by any custom application that needs to
establish connections between documents and parts of documents, for any rea-
son. Thus, even when XLinks are fully implemented in browsers they may not
always be blue underlined text that you click to jump to another page. They can be
that, but they can also be both more and less, depending on your needs.
Simple Links
In HTML, a link is defined with the <A> tag. However, just as XML is more flexible
with tags that describe elements, it is more flexible with tags that refer to external
resources. In XML, almost any tag can be a link. Elements that include links are
called linking elements.
Linking elements are identified by an xlink:form attribute with either the value
simple or extended. Furthermore, each linking element contains an href attribute
whose value is the URI of the resource being linked to. For example, these are three
linking elements:
<FOOTNOTE xlink:form=”simple” href=”footnote7.xml”>7</FOOTNOTE>
<COMPOSER xlink:form=”simple” inline=”true”
href=”http://www.users.interport.net/~beand/”>
Beth Anderson
</COMPOSER>
<IMAGE xlink:form=”simple” href=”logo.gif”/>
Notice that the elements have semantic names that describe the content they
contain rather than how the elements behave. The information that these elements
are links is included in the attributes of the tags.
3. 573
Chapter 16 ✦ XLinks
These three examples are simple XLinks. Simple XLinks are similar to standard
HTML links and are likely to be supported by application software before the more
complex (and more powerful) extended links, so I’ll begin with them. Extended links
are discussed in the next section.
In the FOOTNOTE example above, the link target attribute’s name is href. Its value
is the relative URL footnote7.xml. The protocol, host, and directory of this
document are taken from the protocol, host, and directory of the document in
which this link appears.
In the COMPOSER example above, the link target attribute’s name is href. The value
of the href attribute is the absolute URL http://www.users.interport.net/~beand/In
the third example above, which is IMAGE, the link target attribute’s name is href.
The value of the href attribute is the relative URL logo.gif. Again, the protocol,
host, and directory of this document are taken from the protocol, host, and
directory of the document in which this link appears.
If your document has a DTD, these attributes must be declared like any other. For
example, DTD declarations of the FOOTNOTE, COMPOSER, and IMAGE elements might
look like this:
<!ELEMENT FOOTNOTE (#PCDATA)>
<!ATTLIST FOOTNOTE
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
>
<!ELEMENT COMPOSER (#PCDATA)>
<!ATTLIST COMPOSER
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
>
<!ELEMENT IMAGE EMPTY>
<!ATTLIST IMAGE
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
>
With these declarations, the xlink:form attribute has a fixed value. Therefore it
does not need to be included in the instances of the elements, which you may now
write more compactly like this:
<FOOTNOTE href=”footnote7.xml”>7</FOOTNOTE>
<COMPOSER href=”http://www.users.interport.net/~beand/”>
Beth Anderson
</COMPOSER>
<IMAGE href=”logo.gif”/>
4. 574 Part IV ✦ Supplemental Technologies
Making an element a link element doesn’t impose any restriction on other attributes
or contents of an element. A link element may contain arbitrary children or other
attributes, always subject to the restrictions of the DTD, of course. For example,
here’s a more realistic declaration of the IMAGE element. Note that most of the
attributes don’t have anything to do with linking.
<!ELEMENT IMAGE EMPTY>
<!ATTLIST IMAGE
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
ALT CDATA #REQUIRED
HEIGHT CDATA #REQUIRED
WIDTH CDATA #REQUIRED
>
Descriptions of the Local Resource
A linking element may contain optional content-role and content-title
elements that provide extra information and further describe the purpose of the
link inside the document in which it appears. For example:
<AUTHOR href=”http://www.macfaq.com/personal.html”
content-title=”author of the page”
content-role=”whom to contact for questions about this page”>
Elliotte Rusty Harold
</AUTHOR>
The content-role and content-title attributes describe the local resource —
that is, the contents of the link element, which is Elliotte Rusty Harold in this
example. These attributes, however, do not describe the remote resource, which
is the document at http://www.macfaq.com/personal.html in this example.
Thus, this example says that Elliotte Rusty Harold has the title “author of the page”
and the role “whom to contact for questions about this page.” This does not neces-
sarily have any relation to the document that is found at http://www.macfaq.
com/personal.html.
The content-title attribute is generally used by an application reading the XML
to show a bit of extra information to the user, perhaps in the browser’s status bar
or via a tool tip, when the user moves the mouse over the linked element. However,
the application is not required to show this information to the user. It simply may
do so if it chooses.
The content-role attribute indicates the purpose of the linked element in the
document. The content-role attribute is similar to a processing instruction in
that it’s intended to pass data to the application reading the XML. It has no real
purpose as XML, though, and applications are free to ignore it.
Like all other attributes, content-title and content-role should be declared
in the DTD for all elements to which they belong. For example, this is a reasonable
declaration for the above AUTHOR element:
5. 575
Chapter 16 ✦ XLinks
<!ELEMENT AUTHOR (#PCDATA)>
<!ATTLIST AUTHOR
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
content-title CDATA #IMPLIED
content-role CDATA #IMPLIED
>
Descriptions of the Remote Resource
The link element may contain optional role and title attributes that describe the
remote resource, that is, the document or other resource to which the link points.
For example:
<AUTHOR href=”http://www.macfaq.com/personal.html”
title=”Elliotte Rusty Harold’s personal home page”
role=”further information about the author of this page”
content-title=”author of the page”
content-role=”whom to contact for questions about this page”>
Elliotte Rusty Harold
</AUTHOR>
The role and title attributes describe the remote resource, not the local element.
The remote resource in the above example is the document at http://www.macfaq.
com/personal.html. Thus, the above example says that the page at http://www.
macfaq.com/personal.html has the title “Elliotte Rusty Harold’s personal home
page” and the role “further information about the author of this page.” It is not
uncommon, though it’s not required, for the title to be the same as the contents
of the TITLE element of the page to which you are linking.
The application reading the XML might use these two attributes to show extra
information to the user. However, the application is not required to show this
information to the user or do anything with it.
The role attribute indicates the purpose of the remote resource (the one to which
it’s linked) in the linking document (the one from which it’s linked). For example, it
might distinguish between footnotes, endnotes, and citations.
As with all other attributes, the title and role attributes should be declared in
the DTD for all the elements to which they belong. For example, this is a reasonable
declaration for the above author element:
<!ELEMENT AUTHOR (#PCDATA)>
<!ATTLIST AUTHOR
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
content-title CDATA #IMPLIED
content-role CDATA #IMPLIED
title CDATA #IMPLIED
role CDATA #IMPLIED
>
6. 576 Part IV ✦ Supplemental Technologies
Link Behavior
Link elements can contain three more optional attributes that suggest to applications
how the remote resource is associated with the current page. These are:
1. show
2. actuate
3. behavior
The show attribute suggests how the content should be displayed when the link is
activated, for example, by opening a new window to hold the content. The actuate
attribute suggests whether the link should be traversed automatically or whether
a specific user request is required. The behavior attribute can provide detailed
information to the application about exactly how the link is to be traversed, such
as a time delay before the link is traversed. These are all application dependent,
however, and applications are free to ignore the suggestions.
The show Attribute
The show attribute has three legal values: replace, new, and embed.
With a value of replace when the link is activated (generally by clicking on it, at
least in GUI browsers), the target of the link replaces the current document in the
same window. This is the default behavior of HTML links. For example:
<COMPOSER href=”http://www.users.interport.net/~beand/”
show=”replace”>
Beth Anderson
</COMPOSER>
With a value of new, activating the link opens a new window in which the targeted
resource is displayed. This is similar to the behavior of HTML links when the
target attribute is set to _blank. For example:
<WEBSITE href=”http://www.quackwatch.com/” show=”new”>
Check this out, but don’t leave our site completely!
</WEBSITE>
Readers do not expect a new window to open after clicking a link. They expect that
Caution
when they click a link, the new page will load into the current window, unless they
specifically ask for the link to open in a new window.
Some companies are so self-important that they find it impossible to believe that
any user would ever want to leave their sites. Thus they “help” the readers by
opening new windows. Most of the time this only serves to confuse and annoy.
Don’t change the behavior users expect without a very good reason. The thin hope
that a reader might spend an additional two seconds on your site or view one
more page and see one more ad is not a good reason.
7. 577
Chapter 16 ✦ XLinks
With a value of embed, activating the link inserts the targeted resource into
the existing document. Exactly what this means is application dependent.
However, you can imagine it being used to provide client-side includes for
Web pages. For example, this element, rather than directly including individ-
ual elements for the members of a family, copies them out of the separate files
ThomasCorwinAnderson.xml, LeAnahDeMintEnglish.xml, JohnJayAnderson.xml,
and SamuelEnglishAnderson.xml.
<FAMILY ID=”f732”>
<HUSBAND href=”ThomasCorwinAnderson.xml” show=”embed”/>
<WIFE href=”LeAnahDeMintEnglish.xml” show=”embed”/>
<CHILD href=”JohnJayAnderson.xml” show=”embed”/>
<CHILD href=”SamuelEnglishAnderson.xml” show=”embed”/>
</FAMILY>
The result, after the links are traversed and their contents embedded in the FAMILY
element, is something like this:
<FAMILY ID=”f732”>
<PERSON ID=”p1035” SEX=”M”>
<NAME>
<GIVEN>Thomas Corwin</GIVEN>
<SURNAME>Anderson</SURNAME>
</NAME>
<BIRTH>
<DATE>24 Aug 1845</DATE>
</BIRTH>
<DEATH>
<PLACE>Mt. Sterling, KY</PLACE>
<DATE>18 Sep 1889</DATE>
</DEATH>
</PERSON>
<PERSON ID=”p1098” SEX=”F”>
<NAME>
<GIVEN>LeAnah (Lee Anna, Annie) DeMint</GIVEN>
<SURNAME>English</SURNAME>
</NAME>
<BIRTH>
<PLACE>Louisville, KY</PLACE>
<DATE>1 Mar 1843</DATE>
</BIRTH>
<DEATH>
<PLACE>acute Bright’s disease, 504 E. Broadway</PLACE>
<DATE>31 Oct 1898</DATE>
</DEATH>
</PERSON>
<PERSON ID=”p1102” SEX=”M”>
<NAME>
<GIVEN>John Jay (Robin Adair )</GIVEN>
<SURNAME>Anderson</SURNAME>
</NAME>
<BIRTH>
8. 578 Part IV ✦ Supplemental Technologies
<PLACE>Sideview</PLACE>
<DATE>13 May 1873</DATE>
</BIRTH>
<DEATH>
<DATE>18 Sep 1889 </DATE>
</DEATH>
</PERSON>
<PERSON ID=”p37” SEX=”M”>
<NAME>
<GIVEN>Samuel English</GIVEN>
<SURNAME>Anderson</SURNAME>
</NAME>
<BIRTH>
<PLACE>Sideview</PLACE>
<DATE>25 Aug 1871</DATE>
</BIRTH>
<DEATH>
<PLACE>Mt. Sterling, KY</PLACE>
<DATE>10 Nov 1919</DATE>
</DEATH>
</PERSON>
</FAMILY>
Although each of these PERSON elements exists in a separate file, the complete
FAMILY element is treated as though it was in one file.
Like all attributes in valid documents, the show attribute must be declared in a
<!ATTLIST> declaration for the DTD’s link element. For example:
<!ELEMENT WEBSITE (#PCDATA)>
<!ATTLIST WEBSITE
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
show (new | replace | embed) “new”
>
The actuate Attribute
A link element’s actuate attribute has two possible values: user and auto. The
value user, the default, specifies that the link is to be traversed only when and if
the user requests it. On the other hand, if the link element’s actuate attribute is set
to auto, the link is traversed any time one of the other targeted resources of the
same link element is traversed. This is useful for link groups (discussed below).
Like all attributes in valid documents, the actuate attribute must be declared in
the DTD in a <!ATTLIST> declaration for the link elements in which it appears. For
example:
<!ELEMENT WEBSITE (#PCDATA)>
<!ATTLIST WEBSITE
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
9. 579
Chapter 16 ✦ XLinks
show (new | replace | embed) “new”
actuate (user | auto) “user”
>
The behavior Attribute
The behavior attribute is used to pass arbitrary data in an arbitrary format to the
application reading the data. The application is expected to use this data to make
additional determinations about how the link behaves. For example, if you want
to specify that the sound file fanfare.au play when a link is traversed, you might
write this:
<COMPOSER xlink:form=”simple”
href=”http://www.users.interport.net/~beand/”
behavior=”sound: fanfare.au”>
Beth Anderson
</COMPOSER>
A Shortcut for the DTD
Because the attribute names and types are standardized, if you have more than one link ele-
ment in a document, often it’s convenient to make the attribute declarations a parameter
entity reference and simply repeat that in the declaration of each linking element. For example:
<!ENTITY % link-attributes
“xlink:form CDATA #FIXED ‘simple’
href CDATA #REQUIRED
behavior CDATA #IMPLIED
content-role CDATA #IMPLIED
content-title CDATA #IMPLIED
role CDATA #IMPLIED
title CDATA #IMPLIED
show (new | replace | embed) ‘new’
actuate (user | auto) ‘user’
behavior CDATA #IMPLIED”
>
<!ELEMENT COMPOSER (#PCDATA)>
<!ATTLIST COMPOSER
%link-attributes;
>
<!ELEMENT AUTHOR (#PCDATA)>
<!ATTLIST AUTHOR
%link-attributes;
>
<!ELEMENT WEBSITE (#PCDATA)>
<!ATTLIST WEBSITE
%link-attributes;
>
10. 580 Part IV ✦ Supplemental Technologies
However, this requires that the application reading the XML file understand that
a behavior attribute with the value sound: fanfare.au means the sound file
fanfare.au should play when the link is traversed. Most, probably all, applications
don’t understand this. However, they may use the behavior attribute as a
convenient place to store nonstandard information they do understand.
As with all attributes in valid documents, the behavior attribute must be declared in
the DTD for the link elements in which it appears. For example, the above COMPOSER
element could be declared this way:
<!ELEMENT COMPOSER (#PCDATA)>
<!ATTLIST COMPOSER
xlink:form CDATA #FIXED “simple”
href CDATA #REQUIRED
behavior CDATA #IMPLIED
>
Extended Links
Simple links behave more or less like the standard links you’re accustomed to from
HTML. Each contains a single local resource and a reference to a single remote
resource. The local resource is the link element’s contents. The remote resource is
the link’s target.
Extended links, however, go substantially beyond what you can do with an HTML
link to include multidirectional links between many documents and out-of-line links.
Extended links are identified by an xlink:form attribute with the value extended,
like this:
<WEBSITE xlink:form=”extended”>
The first capability of extended links is to point to more than one target. To allow
this, extended links store the targets in child locator elements of the linking
element rather than in a single href attribute of the linking element as simple
links do. For example:
<WEBSITE xlink:form=”extended”>Cafe au Lait
<locator href=”http://metalab.unc.edu/javafaq/”>
North Carolina
</locator>
<locator
href=”http://sunsite.univie.ac.at/jcca/mirrors/javafaq/”>
Austria
</locator>
<locator href=”http://sunsite.icm.edu.pl/java-corner/faq/”>
Poland
</locator>
<locator href=”http://sunsite.uakom.sk/javafaq/”>
11. 581
Chapter 16 ✦ XLinks
Slovakia
</locator>
<locator href=”http://sunsite.cnlab-switch.ch/javafaq/”>
Switzerland
</locator>
</WEBSITE>
Both the linking element itself, WEBSITE, in this example, and the individual
locator children may have attributes. The linking element only has attributes
that apply to the entire link andthe local resource, such as content-title and
content-role. The locator elements have attributes that apply to the particular
remote resource to which they link, such as role and title. For example:
<WEBSITE xlink:form=”extended” content-title=”Cafe au Lait”
content-role=”Java news”>
<locator href=”http://metalab.unc.edu/javafaq/”
title=”Cafe au Lait” role=”.us”/>
<locator
href=”http://sunsite.univie.ac.at/jcca/mirrors/javafaq/”
title=”Cafe au Lait” role=”.at”/>
<locator href=”http://sunsite.icm.edu.pl/java-corner/faq/”
title=”Cafe au Lait” role=”.pl”/>
<locator href=”http://sunsite.uakom.sk/javafaq/”
title=”Cafe au Lait” role=”.sk”/>
<locator href=”http://sunsite.cnlab-switch.ch/javafaq/”
title=”Cafe au Lait” role=”.ch”/>
</WEBSITE>
The actuate, behavior, and show attributes, if present, belong to the individual
locator elements.
In some cases, as in the above example, where the individual locators point to
mirror copies of the same page, remote resource attributes for individual locator
elements may be the same across the linking element. In this case, you can use
remote resource attributes in the linking element itself. These attributes apply to
each of the locator children that does not declare a conflicting value for the same
attribute. For example:
<WEBSITE xlink:form=”extended” content-title=”Cafe au Lait”
content-role=”Java news” title=”Cafe au Lait”>
<locator href=”http://metalab.unc.edu/javafaq/” role=”.us”/>
<locator
href=”http://sunsite.univie.ac.at/jcca/mirrors/javafaq/”
role=”.at”/>
<locator href=”http://sunsite.icm.edu.pl/java-corner/faq/”
role=”.pl”/>
<locator href=”http://sunsite.uakom.sk/javafaq/” role=”.sk”/>
<locator href=”http://sunsite.cnlab-switch.ch/javafaq/”
role=”.ch”/>
</WEBSITE>
12. 582 Part IV ✦ Supplemental Technologies
Another Shortcut for the DTD
If you have many link and locator elements, it may be advantageous to define the com-
mon attributes in parameter entities in the DTD, which you can reuse in different elements.
For example:
<!ENTITY % remote-resource-semantics.att
“role CDATA #IMPLIED
title CDATA #IMPLIED
show (embed|replace|new) #IMPLIED ‘replace’
actuate (auto|user) #IMPLIED ‘user’
behavior CDATA #IMPLIED”
>
<!ENTITY % local-resource-semantics.att
“content-title CDATA #IMPLIED
content-role CDATA #IMPLIED”
>
<!ENTITY % locator.att
“href CDATA #REQUIRED”
>
<!ENTITY % link-semantics.att
“inline (true|false) ‘true’
role CDATA #IMPLIED”
>
<!ELEMENT WEBSITE (locator*) >
<!ATTLIST WEBSITE
xlink:form CDATA #FIXED “extended”
%local-resource-semantics.att;
>
<!ELEMENT locator EMPTY>
<!ATTLIST locator
xlink:form CDATA #FIXED “locator”
%locator.att;
%link-semantics.att;
>
As always, in valid documents, the link elements and all their possible attributes
must be declared in the DTD. For example, the following declares the WEBSITE
and locator elements used in the above examples, as well as their attributes:
13. 583
Chapter 16 ✦ XLinks
<!ELEMENT WEBSITE (locator*) >
<!ATTLIST WEBSITE
xlink:form CDATA #FIXED “extended”
content-title CDATA #IMPLIED
content-role CDATA #IMPLIED
title CDATA #IMPLIED
>
<!ELEMENT locator EMPTY>
<!ATTLIST locator
xlink:form CDATA #FIXED “locator”
href CDATA #REQUIRED
role CDATA #IMPLIED
>
Out-of-Line Links
The links considered so far, both simple and extended, are inline links. Inline links,
such as the familiar A element from HTML, use the contents of the link element as
part of the document that contains the link. It is shown to the reader.
XLinks can also be out-of-line. An out-of-line link may not be present in any of
the documents it connects. Instead, the links are stored in a separate linking
document. For example, this might be useful to maintain a slide show where
each slide requires next and previous links. By changing the order of the slides
in the linking document, you can change the targets of the previous and next
links on each page without having to edit the slides themselves.
To mark a link as out-of-line, provide an inline attribute with the value false.
For example, the following simple, out-of-line link describes a Web site using an
empty element. An empty element has no content; in the case of a link it has no
local resource. Therefore, it should not have content-role or content-title
attributes that describe the local resource. It may have, as in this example, role
and title attributes that describe the remote resource.
<WEBSITE xlink:form=”simple” inline=”false”
href=”http://metalab.unc.edu/xml/”
title = “Cafe con Leche” role=”XML News”/>
Because all the links you’ve seen until now were inline links, they implicitly had
Note
inline attributes with the value true, the default.
Simple out-of-line links, as in the above example, are relatively rare. Much more
common and useful are out-of-line extended links, as shown below:
<WEBSITE xlink:form=”extended” inline=”false”>
<locator href=”http://metalab.unc.edu/javafaq/” role=”.us”/>
14. 584 Part IV ✦ Supplemental Technologies
<locator
href=”http://sunsite.univie.ac.at/jcca/mirrors/javafaq/”
role=”.at”/>
<locator href=”http://sunsite.icm.edu.pl/java-corner/faq/”
role=”.pl”/>
<locator href=”http://sunsite.uakom.sk/javafaq/” role=”.sk”/>
<locator href=”http://sunsite.cnlab-switch.ch/javafaq/”
role=”.ch”/>
</WEBSITE>
Something such as this might be stored in a separate file on a Web server in a
known location where browsers can find and query it to determine the nearest
mirror of a page they’re looking for. The out-of-line-ness, however, is that this
element does not appear in the document from which the link is activated.
This expands the abstraction of style sheets into the linking domain. A style sheet
is completely separate from the document it describes and yet provides rules
that modify how the document is presented to the reader. A linking document
containing out-of-line links is separated from the documents it connects, yet it
provides the necessary links to the reader. This has several advantages, including
keeping more presentation-oriented markup separate from the document and
allowing the linking of read-only documents.
Style sheets are much farther along than out-of-line links. There currently is no
Caution
general proposal for how you attach “link sheets” to XML documents, much less
how you decide which individual elements in a document are associated with
which links.
One obvious choice is to add an <?xml-linksheet?> processing instruction to
a document’s prolog to specify where the links are found. The link sheet itself
could use something akin to XSL select patterns to map links to individual XML
elements. The selectors could even become the value of the locator element’s
role attribute.
Extended Link Groups
An extended link group element contains a list of links that connect a particular
group of documents. Each document in the group is targeted by means of an
extended link document element. It is the application’s responsibility to understand
how to activate and understand the connections between the group members.
I feel compelled to note that application support for link groups is at best hypo-
Caution
thetical at the time of this writing. Although I can show you how to write such links,
their actual implementation and support likely is some time away. Some of the
details remain to be defined and likely will be implemented in vendor-specific fash-
ions, at least initially. Still, they hold the promise of enabling more sophisticated
linking than can be achieved with HTML.
15. 585
Chapter 16 ✦ XLinks
An Example
For example, I’ve put the notes for a Java course I teach on my Web site. Figure 16-1
shows the introductory page. This particular course consists of 13 classes, each of
which contains between 30 and 60 individual pages of notes. A table of contents is
then provided for each class. Each of the several hundred pages making up the
entire site has links to the previous document, the next document, and the table of
contents (Top link) for the week, as shown in Figure 16-2. Putting it all together, this
amounts to more than a thousand interconnections among this set of documents.
Figure 16-1: The introductory page for my class Web site
shows 13 weeks of lecture notes
The possible interconnections grow exponentially with the number of documents.
Every time a single document is moved, renamed, or divided into smaller pieces,
the links need to be adjusted on that page, on the page before it and after it in the
set, and on the table of contents for the week. Quite frankly, this is a lot more work
than it should be, and it tends to discourage necessary modifications and updates
to the course notes.
16. 586 Part IV ✦ Supplemental Technologies
Figure 16-2: One page of lecture notes displaying the
Previous, Next, and Top links
The sensible thing to do, if HTML supported it, would be to store the connections
in a separate document. Reorganization of the pages then could be performed by
editing that one document. HTML links don’t support this, but XLinks do. Instead
of storing the links inline in HTML files, they can be stored out-of-line in group
elements. For example:
<COURSE xlink:form=”group”>
<CLASS xlink:form=”document” href=”week1/index.xml”/>
<CLASS xlink:form=”document” href=”week2/index.xml”/>
<CLASS xlink:form=”document” href=”week3/index.xml”/>
<CLASS xlink:form=”document” href=”week4/index.xml”/>
<CLASS xlink:form=”document” href=”week5/index.xml”/>
<CLASS xlink:form=”document” href=”week6/index.xml”/>
<CLASS xlink:form=”document” href=”week7/index.xml”/>
<CLASS xlink:form=”document” href=”week8/index.xml”/>
<CLASS xlink:form=”document” href=”week9/index.xml”/>
<CLASS xlink:form=”document” href=”week10/index.xml”/>
<CLASS xlink:form=”document” href=”week11/index.xml”/>
<CLASS xlink:form=”document” href=”week12/index.xml”/>
<CLASS xlink:form=”document” href=”week13/index.xml”/>
</COURSE>
This defines the COURSE element as an extended link group, which consists of 13
extended link document elements, the CLASS elements.
17. 587
Chapter 16 ✦ XLinks
The steps Attribute
One thing an application may choose to do with a link group is preload all the
documents in the link group. These documents may contain link groups of their
own. For example, each of the CLASS elements above refers to one of the site’s table
of contents pages for a specific week, as shown in Figure 16-3. These documents
could then load. For example, the file week6/index.xml could contain this link group:
<CLASS xlink:form=”group”>
<SLIDE xlink:form=”document” href=”01.xml”/>
<SLIDE xlink:form=”document” href=”02.html”/>
<SLIDE xlink:form=”document” href=”06.html”/>
<SLIDE xlink:form=”document” href=”12.html”/>
<SLIDE xlink:form=”document” href=”13.html”/>
<SLIDE xlink:form=”document” href=”16.html”/>
<SLIDE xlink:form=”document” href=”17.html”/>
<SLIDE xlink:form=”document” href=”19.html”/>
<SLIDE xlink:form=”document” href=”21.html”/>
<SLIDE xlink:form=”document” href=”22.html”/>
<SLIDE xlink:form=”document” href=”24.html”/>
</CLASS >
Figure 16-3: A table-of-contents page showing the first
week’s lecture notes
18. 588 Part IV ✦ Supplemental Technologies
Now suppose one of these documents refers back to the original document. This
might trigger an infinite regression, with the same documents repeatedly loading
until the application runs out of memory. To prevent this, the group element may
contain a steps attribute that specifies the number of levels to recursively follow
link groups. For example, to specify that preloading shouldn’t go deeper than three
levels from the current document, write:
<group xlink:form=”group” steps=”3”>
To be honest, I’m not sure how important this is. It’s not hard for an application to
Note
note when it’s already followed a document and not process the document a sec-
ond time. I suspect it is better to place the requirement for preventing recursion
with the XML processor rather than the page author.
The steps attribute can be used to limit the amount of preloading that occurs. For
instance, in the class notes example, it’s unlikely that any person is going to read
the entire set of course notes in one sitting, though perhaps he or she may want to
print or copy all of them. In any case, by setting the steps attribute to 1, you can
limit the depth of the traversal to simply the named pages rather than the several
hundred pages in the course.
As always, these elements and their attributes must be declared in the DTD of any
valid document in which they appear. In practice, the xlink:form attribute is fixed
so that it need not be included in instances of the element. For example:
<!ELEMENT CLASS (document*)>
<!ATTLIST CLASS
xlink:form CDATA #FIXED “group”
steps CDATA #IMPLIED
>
<!ELEMENT SLIDE EMPTY>
<!ATTLIST SLIDE
xlink:form CDATA #FIXED “document”
href CDATA #REQUIRED
>
Renaming XLink Attributes
XLinks are built around the ten attributes discussed in the previous sections. They
are listed below.
xlink:form
href
steps
title
role
content-title
content-role
show
19. 589
Chapter 16 ✦ XLinks
actuate
behavior
It is far from inconceivable that one or more of these attributes will already be used
as an attribute name in a particular XML application. The title attribute seems
particularly likely to be taken. The only one that really shouldn’t be used for other
purposes is xlink:form.
The XLink specification anticipates this problem and allows you to rename
the XLink attributes to something more convenient using the xml:attributes
attribute. This attribute is declared in an <!ATTLIST> declaration in the DTD as a
fixed attribute with type CDATA and a value that’s a whitespace-separated list of
pairs of standard names and new names.
This is exactly the problem that namespaces (discussed in Chapter 18) were
Note
designed to solve. I would not be surprised to see this entire mechanism deleted
in a future draft of XLL and replaced with a simple namespace prefix such as
xlink:.
For example, the link elements shown in this chapter look a little funny because the
standard names are all lowercase while this book’s convention is all uppercase. It’s
easy enough to change the XLink attributes to uppercase with a declaration such
as this:
<!ELEMENT WEBSITE (#PCDATA)>
<!ATTLIST WEBSITE
xlink:form CDATA #FIXED “simple”
xml:attributes CDATA #FIXED
“href HREF show SHOW actuate ACTUATE”
HREF CDATA #REQUIRED
SHOW CDATA (new | replace | embed) “new”
ACTUATE CDATA (user | auto) user
>
Now you can rewrite the WEBSITE example in this more congruous form:
<WEBSITE HREF=”http://www.microsoft.com/” SHOW=”new”>
Check this out, but don’t leave our site completely!
</WEBSITE>
The above ATTLIST declaration only changes the attributes of the WEBSITE
element. If you want to change them the same way in multiple other examples,
the easiest approach is to use a parameter entity:
<!ENTITY LINK_ATTS
‘xlink:form CDATA #FIXED “simple”
xml:attributes CDATA #FIXED
“href HREF show SHOW actuate ACTUATE”
HREF CDATA #REQUIRED
SHOW CDATA (new | replace | embed) “new”
ACTUATE CDATA (user | auto) “user”’
20. 590 Part IV ✦ Supplemental Technologies
>
<!ELEMENT WEBSITE (#PCDATA)>
<!ATTLIST WEBSITE %LINK_ATTS;>
<!ELEMENT COMPOSER (#PCDATA)>
<!ATTLIST COMPOSER %LINK_ATTS;>
<!ELEMENT FOOTNOTE (#PCDATA)>
<!ATTLIST FOOTNOTE %LINK_ATTS;>
Summary
In this chapter, you learned about XLinks. In particular you learned:
✦ XLinks can do everything HTML links can do and quite a bit more, but they
aren’t supported by current applications.
✦ Simple links behave much like HTML links, but they are not restricted to a
single <A> tag.
✦ Link elements are identified by xlink:form and href attributes.
✦ Link elements can describe the local resource with content-title and
content-role attributes.
✦ Link elements can describe the remote resource they’re linking to with title
and role attributes.
✦ Link elements can use the show attribute to tell the application how the
content should be displayed when the link is activated, for example, by
opening a new window.
✦ Link elements can use the behavior attribute to provide the application with
detailed, application dependent information about exactly how the link is to
be traversed.
✦ Link elements can use the actuate attribute to tell the application whether
the link should be traversed without a specific user request.
✦ Extended links can include more than a single URI in a linking element.
Currently, it’s left to the application to decide how to choose between
different alternatives.
✦ An extended link group element contains a list of links that connect a
particular group of documents.
✦ You can use the xml:attributes attribute in the DTD to rename the standard
XLink attributes such as href and title.
In the next chapter you see how XPointers can be used to link not only to remote
documents, but to very specific elements in remote documents.
✦ ✦ ✦