DOCSLIB.ORG

Semantic Web Languages: RDF Vs. SOAP Serialisation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Semantic Web Languages: RDF Vs. SOAP Serialisation Semantic Web Languages: RDF vs. SOAP Serialisation Stefan Haustein University of Dortmund, Computer Science VIII, D-44221 Dortmund, Germany [email protected] AP just as a syntax enco ding of the ABSTRACT gestion is not to use SO RDF data mo del but to build a part of the Semantic Web Although RDF is considered the Semantic Web language, on SOAP serialisati on in the rst place. it may not b e the only one. SOAP serialisati on provides several advantages, esp ecially if the Semantic Web is not viding meta data for existing web pages, but just ab out pro 2. RDF EVOLUTION also ab out exchange of content that is machine-readabl e in The Resource Description Framework RDF [15] was the rst place. This pap er discusses some problems with originall y designed by the World Wide Web Consortium the RDF syntax and data mo del. RDF is compared to W3C as a meta-language for annotating existing web pages SOAP, and some SOAP advantages like b etter integration with additional machine-readable information. Atypical with existing standards and systems, improved readability, RDF applicatio n is the Platform for Internet Content Se- and industry supp ort are p ointed out. lection PICS [6], that is intended to annotate existing web resources with meta-data ab out e.g. the suitabili ty of the Keywords: SOAP Serialisati on, RDF, RDFS, Ob ject- content for children. Orientation Although RDF was originally designed for annotation of existing web pages only, it is currently widely considered hine-readable format for the Semantic Web and the 1. INTRODUCTION as mac DARPA Agent Meta Language DAML. What are the consequences if the term \Semantic Web" However, when using RDF as the primary information do es not just mean HTML with some meta-data, but also format, and not just for meta data annotation, some issues content that is machine-readable in the rst place, thus b e- arise. These problems are describ ed in detail in the following ing suitable for application s like software agent communica- sections. For an overview of additional general RDF issues tion? Although RDF is suitable for that purp ose, its syntax and inconsistencies , the reader is referred to [4] and [10]. and data mo del are clearly optimised for annotating exist- ing do cuments with meta data, describing existing web re- hine readable format. sources using a mac 3. RDF SYNTAX ISSUES In contrast to HTML, the exibili ty of XML allows stor- The requirement that RDF should b e usable for annotat- ing all relevant meta data in a machine-readable format ing existing pages with meta-data without breaking browser in the rst place. With the increasing separation of content compatibili ty for the actual content resulted in a syntax that and layout into XML and XSLT les, and the dynamic gen- is more complicated than necessary for plain RDF do cu- eration of XHTML, the need for a separate meta mo del ments. Also, several alternative syntax forms exist. All may decrease. Naturally, RDF is well suited for annotat- alternatives are semantically equivalent, but have di erent ing the generated HTML with information like PICS, but is e ects on the rendering pro cess in the browser that is used content annotation really all the Semantic Web is ab out? to view the do cument. This article discusses some serious issues concerning the The general RDF syntax consists of simple resource de- RDF syntax and data mo del when used as a primary ma- scriptions \prop erties" emb edded in a \description" ele- chine readable content format, instead of just adding meta- ment. In order to illustrate RDF and SOAP syntax alterna- data to existing HTML or XML pages. It presents SOAP tives, a FIPA 2000 Agent Platform description [14] is used as serialisati on as an alternative. In contrast to [16], the sug- a common example here, where the serialised instances are 1 taken from the Paris Agentcities no de ApDescription . Al- though the Paris no de Agent Platform Description consists , the corresp onding RDF serialisa- Permission to make digital or hard copies of all or part of this work for of four small ob jects only erb ose. personal or classroom use is granted without fee provided that copies are tion gure 1 b ecomes rather v not made or distributed for profit or commercial advantage and that copies rdf:Description elements are bear this notice and the full citation on the first page. To copy otherwise, to In the RDF example, the y their abbreviated form for improved republish, to post on servers or to redistribute to lists, requires prior specific already replaced b permission by the authors. 1 city.html, the ttp://www.agentcities.org/Cities/ pari s Semantic Web Workshop 2001 Hongkong, China see h y \Camel" syntax for compatibility Copyright by the authors. dashes are replaced b <ApDescription id="1"> <name>paris.agentcities.org</name> <dynamic>true</dynamic> <mobility>true</mobility> <transportProfile> <ApTransportDescription id="2"> <availableMtps> <rdf:Bag> <rdf:li> <MtpDescription id="3"> <mtpName>fipa.mts.mtp.iiop.std</mtpName> <addresses> <rdf:Bag> <rdf:li>iiop://leap.crm-paris.com:9000/paris.agentcities.org/acc</rdf:li> <rdf:li>iiopname://leap.crm-paris.com:9000/paris.agentcities.org/acc</rdf:li> </rdf:Bag> </addresses> </MtpDescription> </rdf:li> <rdf:li> <MtpDescription id="4"> <mtpName>fipa.mts.mtp.http.std</mtpName> <addresses> <rdf:Bag> <rdf:li>http://leap.crm-paris.com:8080/acc</rdf:li> </rdf:Bag> </addresses> </MtpDescription> </rdf:li> </rdf:Bag> </availableMtps> </ApTransportDescription> </transportProfile> </ApDescription> Figure 1: RDF Syntax Example readability. The example enco ding is not the only RDF en- co ding option, though. RDF allows several syntax variants: <ApDescription id="1"> <name>paris.agentcities.org</name> <dynamic>true</dynamic> <mobility>true</mobility> Resource description and typ e abbreviation: An <transportProfile> rdf:Description elementmay b e replaced byan <ApTransportDescription id="2"> element named like the typ e of the resource describ ed, ... also obsoleting a corresp onding rdf:type element. </ApTransportDescription> </transportProfile> In the example, the abbreviated form was already </ApDescription> used. All ob ject descriptions in the example could b e replaced by the corresp onding standard form. For example, is equivalentto <ApDescription id="1"> ... <ApDescription id="1"> </ApDescription> <name>paris.agentcities.org</name> <dynamic>true</dynamic> <mobility>true</mobility> <transportProfile resource="2" /> is equivalentto </ApDescription> <ApTransportDescription id="2"> ... <rdf:Description> </ApTransportDescription> <type resource="&fipaNS;ApDescription" /> ... </rdf:Description> The various RDF syntax options lead to two main prob- lems: XSLT and XML Schema compatibility problems and Obviously, the second variant adds ve extra elements problems with human readability. to the example co de. 3.1 XSLT Compatibility The Extensible Stylesheet Language Transformations Using attributes instead of elements: RDF elements XSLT were designed with the main goal of separating the may b e replaced by attributes if they o ccur only once content and layout of Web pages. The basic idea is to de- in their parent element, and contain only literal text sign the original page using an XML language. The XML without further substructures. For example, some of content is then converted to a \regular" XHTML page by the ApDescription sub-elements could b e replaced by an XSLT template. attributes: The various RDF enco ding options describ ed ab ove make development of XSLT templates for RDF dicult: In or- der to b e fully applicabl e to RDF, XSLT templates would <ApDescription id="1"> need to de ne a mapping covering all p ossible syntax alter- <name>paris.agentcities.org</name> natives. It would certainly b e p ossible to design relatively <dynamic>true</dynamic> simple XSLT templates for one concrete serialised form of <mobility>true</mobility> RDF. But then the XSLT transformation would b ecome ei- ... ther very fragile, or another pro cessing step converting any </ApDescription> RDF le to the form exp ected by the template would b e necessary. alentto is equiv 3.2 Human Readability Another problem with RDF is human-readabili ty. While one of the original ideas of XML is to provide some kind of <ApDescription id="1" compromise b etween machine and human-readabili ty, RDF name="paris.agentcities.org" is actually dicult to read for humans. Again, the main dynamic="true" mobility="true"> ... reason are the meta language ro ots of RDF. With the various </ApDescription> syntax options, it is even quite dicult to just see if two RDF do cuments are semantically equivalent. In order to read RDF do cuments, a human must b e familiar with all syntax variants of RDF. When RDF is used to annotate an existing HTML page, the situation b ecomes even worse since Nesting instead of linking Instead of referring to an ob- it is often dicult to di erentiate b etween RDF annotation ject using the rdf:resource attribute, the corresp ond- and actual content. In addition, the verb osity of RDF makes ing ob ject can b e emb edded into the predicate element. it dicult to read when compared to other XML languages In the original example, all ob jects are emb edded for or SOAP. b etter readability. tuitive mapping. 4. RDF DATA MODEL ISSUES The main problem is that there is no in All mappings have their own advantages and disadvantages, While it seems relatively simple to x the problems con- without one b eing clearly preferable to the others. More- cerning the RDF syntax, this is far more dicult for the over, except from the facets solution, which has the dis- RDF data mo del. advantage of extending RDFS, it is not p ossible to apply The RDF data mo del is very simple.
Load more

Recommended publications
  • Ontologies and Semantic Web for the Internet of Things - a Survey
    See discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/312113565 Ontologies and Semantic Web for the Internet of Things - a survey Conference Paper · October 2016 DOI: 10.1109/IECON.2016.7793744 CITATIONS READS 5 256 2 authors: Ioan Szilagyi Patrice Wira Université de Haute-Alsace Université de Haute-Alsace 10 PUBLICATIONS 17 CITATIONS 122 PUBLICATIONS 679 CITATIONS SEE PROFILE SEE PROFILE Some of the authors of this publication are also working on these related projects: Physics of Solar Cells and Systems View project Artificial intelligence for renewable power generation and management: Application to wind and photovoltaic systems View project All content following this page was uploaded by Patrice Wira on 08 January 2018. The user has requested enhancement of the downloaded file. Ontologies and Semantic Web for the Internet of Things – A Survey Ioan Szilagyi, Patrice Wira MIPS Laboratory, University of Haute-Alsace, Mulhouse, France {ioan.szilagyi; patrice.wira}@uha.fr Abstract—The reality of Internet of Things (IoT), with its one of the most important task in an IoT system [6]. Providing growing number of devices and their diversity is challenging interoperability among the things is “one of the most current approaches and technologies for a smarter integration of fundamental requirements to support object addressing, their data, applications and services. While the Web is seen as a tracking and discovery as well as information representation, convenient platform for integrating things, the Semantic Web can storage, and exchange” [4]. further improve its capacity to understand things’ data and facilitate their interoperability. In this paper we present an There is consensus that Semantic Technologies is the overview of some of the Semantic Web technologies used in IoT appropriate tool to address the diversity of Things [4], [7]–[9].
    [Show full text]
  • Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing
    RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing A collection of attributes and processing rules for extending XHTML to support RDF W3C Recommendation 14 October 2008 This version: http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014 Latest version: http://www.w3.org/TR/rdfa-syntax Previous version: http://www.w3.org/TR/2008/PR-rdfa-syntax-20080904 Diff from previous version: rdfa-syntax-diff.html Editors: Ben Adida, Creative Commons [email protected] Mark Birbeck, webBackplane [email protected] Shane McCarron, Applied Testing and Technology, Inc. [email protected] Steven Pemberton, CWI Please refer to the errata for this document, which may include some normative corrections. This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported - 1 - How to Read this Document RDFa in XHTML: Syntax and Processing into a user’s desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo’s creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing.
    [Show full text]
  • OWL 2 Web Ontology Language Quick Reference Guide
    OWL 2 Web Ontology Language Quick Reference W3C Proposed Recommendation 22 September Guide 2009 OWL 2 Web Ontology Language Quick Reference Guide W3C Proposed Recommendation 22 September 2009 This version: http://www.w3.org/TR/2009/PR-owl2-quick-reference-20090922/ Latest version: http://www.w3.org/TR/owl2-quick-reference/ Previous version: http://www.w3.org/TR/2009/WD-owl2-quick-reference-20090611/ (color-coded diff) Editors: Jie Bao, Rensselaer Polytechnic Institute Elisa F. Kendall, Sandpiper Software, Inc. Deborah L. McGuinness, Rensselaer Polytechnic Institute Peter F. Patel-Schneider, Bell Labs Research, Alcatel-Lucent Contributors: Li Ding, Rensselaer Polytechnic Institute Ankesh Khandelwal, Rensselaer Polytechnic Institute This document is also available in these non-normative formats: PDF version, Reference Card. Copyright © 2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. Page 1 of 15 http://www.w3.org/TR/2009/PR-owl2-quick-reference-20090922/ OWL 2 Web Ontology Language Quick Reference W3C Proposed Recommendation 22 September Guide 2009 This document provides a non-normative quick reference guide to the OWL 2 language.
    [Show full text]
  • The Application of Semantic Web Technologies to Content Analysis in Sociology
    THEAPPLICATIONOFSEMANTICWEBTECHNOLOGIESTO CONTENTANALYSISINSOCIOLOGY MASTER THESIS tabea tietz Matrikelnummer: 749153 Faculty of Economics and Social Science University of Potsdam Erstgutachter: Alexander Knoth, M.A. Zweitgutachter: Prof. Dr. rer. nat. Harald Sack Potsdam, August 2018 Tabea Tietz: The Application of Semantic Web Technologies to Content Analysis in Soci- ology, , © August 2018 ABSTRACT In sociology, texts are understood as social phenomena and provide means to an- alyze social reality. Throughout the years, a broad range of techniques evolved to perform such analysis, qualitative and quantitative approaches as well as com- pletely manual analyses and computer-assisted methods. The development of the World Wide Web and social media as well as technical developments like optical character recognition and automated speech recognition contributed to the enor- mous increase of text available for analysis. This also led sociologists to rely more on computer-assisted approaches for their text analysis and included statistical Natural Language Processing (NLP) techniques. A variety of techniques, tools and use cases developed, which lack an overall uniform way of standardizing these approaches. Furthermore, this problem is coupled with a lack of standards for reporting studies with regards to text analysis in sociology. Semantic Web and Linked Data provide a variety of standards to represent information and knowl- edge. Numerous applications make use of these standards, including possibilities to publish data and to perform Named Entity Linking, a specific branch of NLP. This thesis attempts to discuss the question to which extend the standards and tools provided by the Semantic Web and Linked Data community may support computer-assisted text analysis in sociology. First, these said tools and standards will be briefly introduced and then applied to the use case of constitutional texts of the Netherlands from 1884 to 2016.
    [Show full text]
  • Web Services Security Using SOAP, \Rysdl and UDDI
    Web Services Security Using SOAP, \rySDL and UDDI by Lin Yan A Thesis Submitted to the Faculty of Graduate Studies in Partial Fulfillment of the Requirements for the Degtee of MASTER OF SCIENCE Department of Electrical and Computer Engineering University of Manitoba Winnipeg, Manitoba, Canada @ Lin Yan, 2006 THE I]NTVERSITY OF MANITOBA FACULTY OF GRÄDUATE STUDIES COPYRIGHT PERMISSION Web Services Security Using SOAP, WSDL and IJDDI BY Lin Yan A Thesis/Practicum submitted to the Faculty ofGraduate Studies ofThe University of Manitoba in partial fulfillment of the requirement of the degree OF MASTER OF SCIENCE Lin Yan @ 2006 Permission has been granted to the Library ofthe University of Manitoba to lend or sell copies of this thesis/practicum' to the National Library of Canada to microfilm this thesis and to lend or sell copies of the film, and to University Microfitms Inc, to publish an abstract of this thesis/practicum, This reproduction or copy ofthis thesis has been made available by authority ofthe copyright orvner solely for the purpose of private study and research, and may only be reproduced and copied as permitted by copyright laws or with express rvritten authorization from the copyright owner. ABSTRACT The Internet is beginning to change the way businesses operate. Companies are using the Web for selling products, to find suppliers or trading partners, and to link existing applications to other applications. With the rise of today's e-business and e-commerce systems, web services are rapidly becoming the enabling technology to meet the need of commerce. However, they are not without problems.
    [Show full text]
  • SLA Information Technology Division Metadata for Video: Too Much
    3/1/2019 Metadata for Video: Too Much Content, Not Enough Information | SLA Information Technology Division Home About Us » Events » Sections » Enter search keyword SLA Information Technology Division Awards » Making Edgier Easier. We're IT! Current b/ITe (v31n5) » b/ITe Archives Virtual Events What’s New Categorized | Uncategorized Metadata for Video: Too Much Content, Not Enough Information Posted on 31 August 2012. by Wayne Pender, McGill University, 2012 Joe Ann Clifton Student Award Winner (Published September 1, 2012) Abstract Television news libraries have struggled with cataloguing, organizing and storing visual materials for efficient search and retrieval for years. This task has been complicated by the emergence of digital video and the exponential growth in the holdings of television news libraries. In parallel, the ability for non-professionals to shoot, edit and publish videos of increasing production value and complexity on the web has flooded the Internet with videos that appeal to a wide audience and subject interest. The present survey looks at the metadata protocols and practices in place for an internal audience in professional operations and on display for the general public on the Internet. The study finds that the lack of a common metadata schema can make much of the material inaccessible. Literature pertaining to this area is reviewed and future direction is discussed. http://it.sla1.org/2012/08/metadata/ 1/10 3/1/2019 Metadata for Video: Too Much Content, Not Enough Information | SLA Information Technology Division Keywords: metadata, video, XML, RDF, MXF, television, news, YouTube Paper Searching and retrieving visual content is problematic. The search for specific moving images on film and video has long been a task for television news professionals, but now with wide spread availability of video resources on the Internet it has become a task for anyone.
    [Show full text]
  • The Semantic Web: the Origins of Artificial Intelligence Redux
    The Semantic Web: The Origins of Artificial Intelligence Redux Harry Halpin ICCS, School of Informatics University of Edinburgh 2 Buccleuch Place Edinburgh EH8 9LW Scotland UK Fax:+44 (0) 131 650 458 E-mail:[email protected] Corresponding author is Harry Halpin. For further information please contact him. This is the tear-off page. To facilitate blind review. Title:The Semantic Web: The Origins of AI Redux working process managed to both halt the fragmentation of Submission for HPLMC-04 the Web and create accepted Web standards through its con- sensus process and its own research team. The W3C set three long-term goals for itself: universal access, Semantic Web, and a web of trust, and since its creation these three goals 1 Introduction have driven a large portion of development of the Web(W3C, 1999) The World Wide Web is considered by many to be the most significant computational phenomenon yet, although even by One comparable program is the Hilbert Program in mathe- the standards of computer science its development has been matics, which set out to prove all of mathematics follows chaotic. While the promise of artificial intelligence to give us from a finite system of axioms and that such an axiom system machines capable of genuine human-level intelligence seems is consistent(Hilbert, 1922). It was through both force of per- nearly as distant as it was during the heyday of the field, the sonality and merit as a mathematician that Hilbert was able ubiquity of the World Wide Web is unquestionable. If any- to set the research program and his challenge led many of the thing it is the Web, not artificial intelligence as traditionally greatest mathematical minds to work.
    [Show full text]
  • Schematron Overview Excerpted from Leigh Dodds’ 2001 XSLT UK Paper, “Schematron: Validating XML Using XSLT”
    Schematron: validating XML using XSLT Schematron Overview excerpted from Leigh Dodds’ 2001 XSLT UK paper, “Schematron: validating XML using XSLT” Leigh Dodds, ingenta ltd, xmlhack.com April 2001 Abstract Schematron [Schematron] is a structural based validation language, defined by Rick Jelliffe, as an alternative to existing grammar based approaches. Tree patterns, defined as XPath expressions, are used to make assertions, and provide user-centred reports about XML documents. Expressing validation rules using patterns is often easier than defining the same rule using a content model. Tree patterns are collected together to form a Schematron schema. Schematron is a useful and accessible supplement to other schema languages. The open-source XSLT implementation is based around a core framework which is open for extension and customisation. Overview This paper provides an introduction to Schematron; an innovative XML validation language developed by Rick Jelliffe. This innovation stems from selecting an alternative approach to validation than existing schema languages: Schematron uses a tree pattern based paradigm, rather than the regular grammars used in DTDs and XML schemas. As an extensible, easy to use, open source tool Schematron is an extremely useful addition to the XML developers toolkit. The initial section of this paper conducts a brief overview of tree pattern validation, and some of the advantages it has in comparison to a regular grammar approach. This is followed by an outline of Schematron and the intended uses which have guided its design. The Schematron language is then discussed, covering all major elements in the language with examples of their 1 of 14 Schematron: validating XML using XSLT usage.
    [Show full text]
  • Schema Declaration in Xml Document
    Schema Declaration In Xml Document Is Darin varying or propellant when cluck some suffusion motive melodically? When Anton interdepend his titters reap not gyrally enough, is Parsifal malnourished? Styled Winnie scollop confoundedly, he reincreasing his stopple very refreshfully. When a uri that they come back into account only applies when sales orders that document in order to the design Must understand attribute Should I define a global attribute that will indicate to implementation the criticality of extension elements? Create a DOM parser to use for the validation of an instance document. As such, the XML Schema namespace, and provides a mapping between NIEM concepts and the RDF model. It is a convention to use XSD or XS as a prefix for the XML Schema namespace, et al. XML documents have sufficient structure to guarantee that they can be represented as a hierarchical tree. Are expanded names universally unique? DOC format for easy reading. This site uses cookies. This schema fragment shows the definition of an association type that defines a relationship between a person and a telephone number. Furthermore, such as Adobe Acrobat Reader. In some cases, if any. The idea behind using URIs for namespace names are that URIs are designed to be unique and persistent. Note: The material discussed in this section also applies to validating when using the SAX parser. Finally, Relax NG Schema, even when the elements and attributes defined by Microsoft are present. The XML representation for assertions. Developers of domain schemas and other schemas that build on and extend the NIEM release schemas need to be able to define additional characteristics of common types.
    [Show full text]
  • Instruction for Using XML Notepad
    Using XML Notepad to Read, Edit, and Parse FGDC-CSDGM XML Metadata. Currently many tools exist that allow a user to work with XML metadata files. However, most of the main metadata creation/editing tools do not provide a means of validating a metadata record for compliance with the FGDC-CSDGM standard or its variants, such as the Biological Data Profile (BDP) standard. One of the most reliable ways to validate metadata files (that is, check files for completion and/or errors) is with the USGS Metadata Parser (MP) utilities. The MP tool and the other tools distributed in the package were developed by Peter Schweitzer and are freely available online (http://geology.usgs.gov/tools/metadata/tools/doc/mp.html). Once configured properly, MP can process metadata files and be used to produce a text file with a list of all errors found. A user can then use this list of errors to find and correct the problems using a text editor or the metadata editor of their choice. The challenge with this method is that finding and correcting the error within a metadata editor based solely on the error message from MP can be confusing and frustrating. Additionally, if there are many errors or complex problems to correct, the process will require multiple iterations of running MP and subsequently correcting errors in a metadata editor. All in all, the process can be fairly time consuming and onerous, especially for those without a detailed understanding of the FGDC-CSDGM standard. The methodology for metadata editing and validation described in this document tries to address some of these problems with an alternative approach.
    [Show full text]
  • Cisco XML Schemas
    CHAPTER 14 Cisco XML Schemas This chapter contains information about common XML schemas. The structure and allowable content of the XML request and response instances supported by the Cisco IOS XR XML application programming interface (API) are documented by means of XML schemas (.xsd files). The XML schemas are documented using the standard World Wide Web Consortium (W3C) XML schema language, which provides a much more powerful and flexible mechanism for describing schemas than can be achieved using Document Type Definitions (DTDs). The set of XML schemas consists of a small set of common high-level schemas and a larger number of component-specific schemas as described in this chapter. For more information on the W3C XML Schema standard, see this URL: http://www.w3.org/XML/Schema This chapter contains these sections: • XML Schema Retrieval, page 14-135 • Common XML Schemas, page 14-136 • Component XML Schemas, page 14-136 XML Schema Retrieval The XML schemas that belong to the features in a particular package are obtained as a .tar file from cisco.com. To retrieve the XML schemas, you must: 1. Click this URL to display the Downloads page: http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=268437899 Note Select Downloads. Only customer or partner viewers can access the Download Software page. Guest users will get an error. 2. Select Cisco IOS XR Software. 3. Select IOS XR XML Schemas. 4. Select the XML schema for your platform. Once untarred, all the XML schema files appear as a flat directory of .xsd files and can be opened with any XML schema viewing application, such as XMLSpy.
    [Show full text]
  • Modularization of XHTML in XML Schema Modularization of XHTML™ in XML Schema
    Modularization of XHTML in XML Schema Modularization of XHTML™ in XML Schema Modularization of XHTML™ in XML Schema W3C Working Draft - 22 March 2001 This version: http://www.w3.org/TR/2001/WD-xhtml-m12n-schema-20010322 (Single HTML file [p.1] , PostScript version, PDF version, ZIP archive, or Gzip’d TAR archive) Latest version: http://www.w3.org/TR/xhtml-m12n-schema Editors: Daniel Austin, Mozquito Technologies AG Shane McCarron, Applied Testing and Technology Copyright ©2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This document describes a methodology for the modularization of XHTML using XML Schema. Modularization of XHTML allows document authors to modify and extend XHTML in a conformant way. Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. This is the first public "Working Draft" of "Modularization of XHTML in XML Schema" for review by members of the W3C and other interested parties in the general public. It is a stand-alone document to ease its review. Once the methodology described in this document become mature, it will be integrated into a future document forthcoming from the HTML Working Group. This document is still in its early stage, and may be updated, replaced, or obsoleted by other documents at any time. Publication of this Working Draft does not imply endorsement by the W3C, and it is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress".
    [Show full text]