DOCSLIB.ORG

HTML 4.01 Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

HTML 4.01 Specification HTML 4.01 Specification W3C Proposed Recommendation This version: http://www.w3.org/TR/1999/PR-html40-19990824 (plain text [786Kb], gzip’ed tar archive of HTML files [367Kb], a .zip archive of HTML files [400Kb], gzip’ed Postscript file [740Kb, 387 pages], a PDF file [3Mb]) Latest version: http://www.w3.org/TR/html40 Previous version: http://www.w3.org/TR/1998/REC-html40-19980424 Editors: Dave Raggett <[email protected]> Arnaud Le Hors <[email protected]> Ian Jacobs <[email protected]> Copyright © 1997-1999 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This specification defines the HyperText Markup Language (HTML), version 4.0 (subversion 4.01), the publishing language of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML, HTML 4.01 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4.01 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4.01 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879] [p.351] . 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. 1 24 Aug 1999 14:47 HTML 4.01 Specification This document is a revised version of the 4.0 Recommendation first released on 18 December 1997 and then revised 24 April 1998 Changes since the 24 April version [p.312] are not just editorial in nature. There have been some changes to the DTDs, for example. On 24 August 1999, this document enters a Proposed Recommendation review period. From that date until 22 September 1999, W3C Advisory Committee representatives are encouraged to review this specification and return comments in their completed ballots to [email protected]. Please send any comments of a confidential nature in separate email to [email protected], which is visible to the Team only. No sooner than 14 days after the end of the review period, the Director will announce the document’s disposition: it may become a W3C Recommendation (possibly with minor changes), it may revert to Working Draft status, or it may be dropped as a W3C work item. Publication as a Proposed Recommendation does not imply endorsement by the W3C membership. This is still a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite W3C Proposed Recommendation as other than "work in progress." W3C recommends that user agents and authors (and in particular, authoring tools) produce HTML 4.01 documents rather than HTML 3.2 documents (see [HTML32] [p.354] ). For reasons of backwards compatibility, W3C also recommends that tools interpreting HTML 4.01 continue to support HTML 3.2 and HTML 2.0 as well. This document has been produced as part of the W3C HTML Activity. The goals of the HTML Working Group (members only) are discussed in the HTML Working Group charter (members only). A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR. Public discussion on HTML features takes place on [email protected]. Please report errors in this document to [email protected]. 24 Aug 1999 14:47 2 HTML 4.01 Specification Quick Table of Contents 1. About the HTML 4.01 Specification . 15. 2. Introduction to HTML 4.01 . 21. 3. On SGML and HTML . 29. 4. Conformance: requirements and recommendations . 39. 5. HTML Document Representation - Character sets, character encodings, and entities . 43. 6. Basic HTML data types - Character data, colors, lengths, URIs, content types, etc. 51. 7. The global structure of an HTML document - The HEAD and BODY of a document . 61. 8. Language information and text direction - International considerations for text 79. 9. Text - Paragraphs, Lines, and Phrases . 89. 10. Lists - Unordered, Ordered, and Definition Lists . 103. 11. Tables . 111. 12. Links - Hypertext and Media-Independent Links . 145. 13. Objects, Images, and Applets . 159. 14. Style Sheets - Adding style to HTML documents . 183. 15. Alignment, font styles, and horizontal rules . 195. 16. Frames - Multi-view presentation of documents . 205. 17. Forms - User-input Forms: Text Fields, Buttons, Menus, and more . 219. 18. Scripts - Animated Documents and Smart Forms . 251. 19. SGML reference information for HTML - Formal definition of HTML and validation . 261. 20. SGML Declaration of HTML 4.01 . 263. 21. Document Type Definition . 265. 22. Transitional Document Type Definition . 279. 23. Frameset Document Type Definition . 297. 24. Character entity references in HTML 4.01 . 299. A. Changes . 311. B. Performance, Implementation, and Design Notes . 331. References . 351. Index of Elements . 357. Index of Attributes . 361. Index . 375. 3 24 Aug 1999 14:47 HTML 4.01 Specification Full Table of Contents 1. About the HTML 4.01 Specification . 15. 1. How the specification is organized . 15. 2. Document conventions . 16. 1. Elements and attributes . 17. 2. Notes and examples . 17. 3. Acknowledgments . 17. 1. Acknowledgments for the current revision . 18. 4. Copyright Notice . 18. 2. Introduction to HTML 4.01 . 21. 1. What is the World Wide Web? . 21. 1. Introduction to URIs . 21. 2. Fragment identifiers . 22. 3. Relative URIs . 22. 2. What is HTML? . 23. 1. A brief history of HTML . 23. 3. HTML 4.0 . 24. 1. Internationalization . 24. 2. Accessibility . 24. 3. Tables . 25. 4. Compound documents . 25. 5. Style sheets . 26. 6. Scripting . 26. 7. Printing . 26. 4. Authoring documents with HTML 4.01 . 26. 1. Separate structure and presentation . 27. 2. Consider universal accessibility to the Web . 27. 3. Help user agents with incremental rendering . 27. 3. On SGML and HTML . 29. 1. Introduction to SGML . 29. 2. SGML constructs used in HTML . 30. 1. Elements . 30. 2. Attributes . 31. 3. Character references . 32. 4. Comments . 32. 3. How to read the HTML DTD . 33. 1. DTD Comments . 33. 2. Parameter entity definitions . 33. 3. Element declarations . 34. Content model definitions . 35. 4. Attribute declarations . 36. DTD entities in attribute definitions . 37. 24 Aug 1999 14:47 4 HTML 4.01 Specification Boolean attributes . 38. 4. Conformance: requirements and recommendations . 39. 1. Definitions . 39. 2. SGML . 41. 3. The text/html content type . 41. 5. HTML Document Representation - Character sets, character encodings, and entities . 43. 1. The Document Character Set . 43. 2. Character encodings . 44. 1. Choosing an encoding . 44. Notes on specific encodings . 45. 2. Specifying the character encoding . 45. 3. Character references . 47. 1. Numeric character references . 47. 2. Character entity references . 48. 4. Undisplayable characters . 49. 6. Basic HTML data types - Character data, colors, lengths, URIs, content types, etc. 51. 1. Case information . 51. 2. SGML basic types . 52. 3. Text strings . 52. 4. URIs . 53. 5. Colors . 53. 1. Notes on using colors . 54. 6. Lengths . 54. 7. Content types (MIME types) . 55. 8. Language codes . 55. 9. Character encodings . 55. 10. Single characters . 55. 11. Dates and times . 56. 12. Link types . 56. 13. Media descriptors . 58. 14. Script data . 59. 15. Style sheet data . 59. 16. Frame target names . 59. 7. The global structure of an HTML document - The HEAD and BODY of a document . 61. 1. Introduction to the structure of an HTML document . 61. 2. HTML version information . 62. 3. The HTML element . 63. 4. The document head . 63. 1. The HEAD element . 63. 2. The TITLE element . 64. 5 24 Aug 1999 14:47 HTML 4.01 Specification 3. The title attribute . 65. 4. Meta data . 65. Specifying meta data . 66. The META element . 66. Meta data profiles . 69. 5. The document body . 70. 1. The BODY element . 71. 2. Element identifiers: the id and class attributes . 73. 3. Block-level and inline elements . 74. 4. Grouping elements: the DIV and SPAN elements . 75. 5. Headings: The H1, H2, H3, H4, H5, H6 elements . 76. 6. The ADDRESS element . 78. 8. Language information and text direction - International considerations for text 79. 1. Specifying the language of content: the lang attribute . 79. 1. Language codes . 80. 2. Inheritance of language codes . 81. 3. Interpretation of language codes . 81. 2. Specifying the direction of text and tables: the dir attribute . 82. 1. Introduction to the bidirectional algorithm . 82. 2. Inheritance of text direction information . 83. 3. Setting the direction of embedded text . 84. 4. Overriding the bidirectional algorithm: the BDO element . 85. 5. Character references for directionality and joining control . 87. 6. The effect of style sheets on bidirectionality . 88. 9. Text - Paragraphs, Lines, and Phrases . 89. 1. White space . 89. 2. Structured text . 90. 1. Phrase elements: EM, STRONG, DFN, CODE, SAMP, KBD, VAR, CITE, ABBR, and ACRONYM . 90. 2. Quotations: The BLOCKQUOTE and Q elements . 92. Rendering quotations . 93. 3. Subscripts and superscripts: the SUB and SUP elements . 94. 3. Lines and Paragraphs . 94. 1. Paragraphs: the P element . 95. 2. Controlling line breaks . 95. Forcing a line break: the BR element . 96. Prohibiting a line break . 96. 3. Hyphenation . 96. 4. Preformatted text: The PRE element . 97. 5. Visual rendering of paragraphs . 98. 4. Marking document changes: The INS and DEL elements . 99. 10. Lists - Unordered, Ordered, and Definition Lists . 103. 1. Introduction to lists . 103. 24 Aug 1999 14:47 6 HTML 4.01 Specification 2. Unordered lists (UL), ordered lists (OL), and list items (LI) . 104. 3. Definition lists: the DL, DT, and DD elements .
Recommended publications
  • Using Emergent Team Structure to Focus Collaboration

    Using Emergent Team Structure to Focus Collaboration

    Using Emergent Team Structure to Focus Collaboration by Shawn Minto B.Sc, The University of British Columbia, 2005 A THESIS SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF Master of Science The Faculty of Graduate Studies (Computer Science) The University Of British Columbia January 30, 2007 © Shawn Minto 2007 ii Abstract To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration specialized tools are being integrated into development environments. Although these tools facilitate collaboration, they do not foster it. The problem is that the tools require the developers to maintain a list of other developers with whom they may wish to communicate. In any given situation, it is the developer who must determine who within this list has expertise for the specific situation. Unless the team is small and static, maintaining the knowledge about who is expert in particular parts of the system is difficult. As many organizations are beginning to use agile development and distributed software practices, which result in teams with dynamic membership, maintaining this knowledge is impossible. This thesis investigates whether emergent team structure can be used to support collaboration amongst software developers. The membership of an emergent team is determined from analysis of software artifacts. We first show that emergent teams exist within a particular open-source software project, the Eclipse integrated development environment. We then present a tool called Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We validated this approach to support collaboration by applying our ap• proach to historical data gathered from the Eclipse project, Firefox and Bugzilla and comparing the results to an existing heuristic for recommending experts that produces a list of experts based on the revision history of individual files.
  • XML a New Web Site Architecture

    XML a New Web Site Architecture

    XML A New Web Site Architecture Jim Costello Derek Werthmuller Darshana Apte Center for Technology in Government University at Albany, SUNY 1535 Western Avenue Albany, NY 12203 Phone: (518) 442-3892 Fax: (518) 442-3886 E-mail: [email protected] http://www.ctg.albany.edu September 2002 © 2002 Center for Technology in Government The Center grants permission to reprint this document provided this cover page is included. Table of Contents XML: A New Web Site Architecture .......................................................................................................................... 1 A Better Way? ......................................................................................................................................................... 1 Defining the Problem.............................................................................................................................................. 1 Partial Solutions ...................................................................................................................................................... 2 Addressing the Root Problems .............................................................................................................................. 2 Figure 1. Sample XML file (all code simplified for example) ...................................................................... 4 Figure 2. Sample XSL File (all code simplified for example) ....................................................................... 6 Figure 3. Formatted Page Produced
  • 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 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.
  • Semantic Web

    Semantic Web

    Semantic Web Ing. Federico Chesani Corso di Fondamenti di Intelligenza Artificiale M a.a. 2009/2010 7 Maggio 2010 Outline 1. Introduction a) The map of the Web (accordingly to Tim Berners-Lee) b) The current Web and its limits c) The Semantic Web idea d) Few examples of Semantic Web applications 2. Semantic Information (a bird’s eye view) a) Semantic Models b) Ontologies c) Few examples 3. Semantic Web Tools a) Unique identifiers -URI b) XML c) RDF and SPARQL d) OWL 4. Semantic Web: where are we? a) Problems against the success of SW proposal b) Critics against SW c) Few considerations d) Few links to start with The Web Map (by Berners-Lee) ©Tim Berners-Lee, http://www.w3.org/2007/09/map/main.jpg About the content Knowledge Representation Semantic Web Web The Web 1.0 … • Information represented by means of: – Natural language – Images, multimedia, graphic rendering/aspect • Human Users easily exploit all this means for: – Deducting facts from partial information – Creating mental asociations (between the facts and, e.g., the images) – They use different communication channels at the same time (contemporary use of many primitive senses) The Web 1.0 … • The content is published on the web with the principal aim of being “human-readable” – Standard HTML is focused on how to represent the content – There is no notion of what is represented – Few tags (e.g. <title>) provide an implicit semantics but … • … their content is not structured • … their use is not really standardized The Web 1.0 … We can identify the title by means of its representation (<h1>, <b>) … … what if tomorrow the designer changes the format of the web pages? <h1> <!-- inizio TITOLO --> <B> Finanziaria, il voto slitta a domani<br> Al Senato va in scena l&#039;assurdo </B> <!-- fine TITOLO --> </h1> The Web 1.0 … • Web pages contain also links to other pages, but ..
  • CSS 2.1) Specification

    CSS 2.1) Specification

    Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification W3C Editors Draft 26 February 2014 This version: http://www.w3.org/TR/2014/ED-CSS2-20140226 Latest version: http://www.w3.org/TR/CSS2 Previous versions: http://www.w3.org/TR/2011/REC-CSS2-20110607 http://www.w3.org/TR/2008/REC-CSS2-20080411/ Editors: Bert Bos <bert @w3.org> Tantek Çelik <tantek @cs.stanford.edu> Ian Hickson <ian @hixie.ch> Håkon Wium Lie <howcome @opera.com> Please refer to the errata for this document. This document is also available in these non-normative formats: plain text, gzip'ed tar file, zip file, gzip'ed PostScript, PDF. See also translations. Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance. CSS 2.1 builds on CSS2 [CSS2] which builds on CSS1 [CSS1]. It supports media- specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. It also supports content positioning, table layout, features for internationalization and some properties related to user interface. CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented.
  • Defining Data with DTD Schemas

    Defining Data with DTD Schemas

    06_067232797X_ch03.qxd 10/18/05 9:41 AM Page 43 HOUR 3 Defining Data with DTD Schemas Computers are not intelligent. They only think they are. —Unknown One thing XML aims to solve is human error. Because of XML’s structure and rigidity as a language, there isn’t much room for error on the part of XML developers. If you’ve ever encountered an error at the bank (in their favor!), you can no doubt appreciate the significance of errors in critical computer systems. XML is rapidly being integrated into all kinds of computer systems, including financial systems used by banks. The rigidity of XML as a markup language will no doubt make these systems more robust. The facet of XML that allows errors to be detected is the schema, which is a construct that allows XML developers to define the format and structure of XML data. This hour introduces you to schemas, including the two major types that are used to define data for XML documents. The first of these schema types, DTDs, is examined in detail in this hour, while the latter is saved for a later lesson. This hour explores the inner workings of DTDs and shows you how to create DTDs from scratch. In this hour, you’ll learn . How XML allows you to create custom markup languages . The role of schemas in XML data modeling . The difference between the types of XML schemas . What constitutes valid and well-formed documents . How to declare elements and attributes in a DTD . How to create and use a DTD for a custom markup language Creating Your Own Markup Languages Before you get too far into this hour, I have to make a little confession.
  • Document Type Definition: Structure

    Document Type Definition: Structure

    Introduction to XML: DTD Jaana Holvikivi Document type definition: structure Topics: – Elements – Attributes – Entities – Processing instructions (PI) – DTD design Jaana Holvikivi 2 DTD <!– Document type description (DTD) example (part) --> <!ELEMENT university (department+)> <!ELEMENT department (name, address)> <!ELEMENT name (#PCDATA)> <!ELEMENT address (#PCDATA)> • Document type description, structural description • one rule /element – name – content • a grammar for document instances • ”regular clauses" • (not necessary) Jaana Holvikivi 3 DTD: advantages • validating parsers check that the document conforms to the DTD • enforces logical use of tags • there are existing DTD standards for many application areas – common vocabulary Jaana Holvikivi 4 Well-formed documents • An XML document is well-formed if – its elements are properly nested so that it has a hierarchical tree structure, and all elements have an end tag (or are empty elements) – it has one and only one root element – complies with the basic syntax and structural rules of the XML 1.0 specification: • rules for characters, white space, quotes, etc. – and its every parsed entity is well-formed Jaana Holvikivi 5 Validity • An XML-document is valid if – it is well-formed – it has an attached DTD (or schema) – it conforms to the DTD (or schema) • Validity is checked with a validating parser, either – the whole document at once (”batch") – interactively Jaana Holvikivi 6 Document type declaration Shared <!DOCTYPE catalog PUBLIC ”-//ORG_NAME//DTD CATALOG//EN"> - flag(-/+) indicates
  • Brackets Third Party Page (

    Brackets Third Party Page (

    Brackets Third Party Page (http://www.adobe.com/go/thirdparty) "Cowboy" Ben Alman Copyright © 2010-2012 "Cowboy" Ben Alman Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. The Android Open Source Project Copyright (C) 2008 The Android Open Source Project All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Liste Des Propriétés CSS

    Liste Des Propriétés CSS

    A Liste des propriétés CSS Voici la liste des propriétés CSS telles que décrites dans les documents de la norme CSS 2 (http://www.w3.org/TR/1998/REC-CSS2-19980512/propidx.html). Ceci incorpore donc notamment les propriétés déjà présentes en CSS 1. Tableau A–1 Index des propriétés CSS Nom de la propriété Valeurs Explications azimuth angle, left-side, far-left, Détermine la direction d'origine du son en left, center-left, center, média aural. Les navigateurs actuels ne center-right, right, far-right, gérant pas encore les restitutions vocales, on right-side, behind, leftwards, utilise pour cela des logiciels spécialisés. La rightwards, inherit plupart ne prennent pas encore en charge CSS. background Raccourci pour background-color, background-image, background-repeat, background-attachment, background-position. background- scroll, fixed, inherit Fige une image d'arrière-plan insérée avec attachment background-image. Celle-ci ne défile plus avec le contenu de l'élément auquel elle est appliquée. background-color couleur, transparent, inherit Définit la couleur de fond d'un élément. © Groupe Eyrolles, 2005 Sites et ressources 254 ANNEXES Tableau A–1 Index des propriétés CSS (suite) Nom de la propriété Valeurs Explications background-image URL, none, inherit Affiche une image d'arrière-plan pour l'élé- ment (ou la page dans le cas de la balise body). Par défaut, l'image sera répétée en damier (ou papier peint) à partir du coin supé- rieur gauche de l'élément. background- pourcentage, longueur, top, center, Positionne une image d'arrière-plan définie position bottom, left, right, inherit avec background-image. Propriété géné- ralement utilisée en l'absence de répétition (background-repeat).
  • XHTML+Rdfa 1.1 - Third Edition Table of Contents

    XHTML+Rdfa 1.1 - Third Edition Table of Contents

    XHTML+RDFa 1.1 - Third Edition Table of Contents XHTML+RDFa 1.1 - Third Edition Support for RDFa via XHTML Modularization W3C Recommendation 17 March 2015 This version: http://www.w3.org/TR/2015/REC-xhtml-rdfa-20150317/ Latest published version: http://www.w3.org/TR/xhtml-rdfa/ Implementation report: http://www.w3.org/2010/02/rdfa/wiki/CR-ImplementationReport Previous version: http://www.w3.org/TR/2014/PER-xhtml-rdfa-20141216/ Previous Recommendation: http://www.w3.org/TR/2013/REC-xhtml-rdfa-20130822/ Editor: Shane McCarron, Applied Testing and Technology, Inc., [email protected] Please check the errata for any errors or issues reported since publication. This document is also available in these non-normative formats: XHTML+RDFa, Diff from Previous Recommendation, Postscript version, and PDF version The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2015 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply. Abstract RDFa Core 1.1 [RDFA-CORE [p.61] ] defines attributes and syntax for embedding semantic markup in Host Languages. This document defines one such Host Language. This language is a superset of XHTML 1.1 [XHTML11-2e [p.61] ], integrating the attributes as defined in RDFa Core 1.1. This document is intended for authors who want to create XHTML Family documents that embed rich semantic markup. - 1 - Status of This Document XHTML+RDFa 1.1 - Third Edition Status of This Document This section describes the status of this document at the time of its publication.
  • Fuzzy GML Modeling Based on Vague Soft Sets

    Fuzzy GML Modeling Based on Vague Soft Sets

    International Journal of Geo-Information Article Fuzzy GML Modeling Based on Vague Soft Sets Bo Wei 1,2,*, Qingqing Xie 1,2, Yuanyuan Meng 1,2 and Yao Zou 1,2 1 Guangxi Key Laboratory of Spatial Information and Geomatics, Guilin University of Technology, 12, Jiangan Road, Guilin 541004, China; [email protected] (Q.X.); [email protected] (Y.M.); [email protected] (Y.Z.) 2 College of Geomatics and Geoinformation, Guilin University of Technology, 12, Jiangan Road, Guilin 541004, China * Correspondence: [email protected]; Tel.: +86-773-589-5911 Academic Editors: Zhao-Liang Li, Jose A. Sobrino and Wolfgang Kainz Received: 18 October 2016; Accepted: 5 January 2017; Published: 11 January 2017 Abstract: The Open Geospatial Consortium (OGC) Geography Markup Language (GML) explicitly represents geographical spatial knowledge in text mode. All kinds of fuzzy problems will inevitably be encountered in spatial knowledge expression. Especially for those expressions in text mode, this fuzziness will be broader. Describing and representing fuzziness in GML seems necessary. Three kinds of fuzziness in GML can be found: element fuzziness, chain fuzziness, and attribute fuzziness. Both element fuzziness and chain fuzziness belong to the reflection of the fuzziness between GML elements and, then, the representation of chain fuzziness can be replaced by the representation of element fuzziness in GML. On the basis of vague soft set theory, two kinds of modeling, vague soft set GML Document Type Definition (DTD) modeling and vague soft set GML schema modeling, are proposed for fuzzy modeling in GML DTD and GML schema, respectively. Five elements or pairs, associated with vague soft sets, are introduced.
  • Graduate Project GML and Complex Features 21-E4dc1/020 2/66 19/10/2001 -2A16-DED4.Doc

    Graduate Project GML and Complex Features 21-E4dc1/020 2/66 19/10/2001 -2A16-DED4.Doc

    final version 3BCFDC10 version final Graduate Project GML and Complex Features -2A16-DED4.doc 19/10/2001 2/66 Franklin Monteiro 16 August 2001 <author> Franklin Monteiro <e-mail> [email protected] <department> Information Systems, Database <period> January 2001 – August 2001 <mentors> Drs. C.W. Quak (GISt) Dr. A.N.W. Dahanayake <professor> Prof.dr. W. Gerhardt <supervisor> Prof.dr.ir. P.J.M. van Oosterom (GISt) GML and Complex Features Preface Preface 3BCFDC10-2A16-DED4.docversion 19/10/2001 i/66 final This report is the result of the graduate project “GML and Complex Features” which has been performed at the department of Geodesy, section GIS-technology (GIS-t) of the faculty of Civil Engineering and Geosciences, in the final stage of the study Technical Informatics (specialization department Information Systems, section Databases) at the Delft University of Technology. The author offers special thanks to the supervisors, co-workers of the section GIS-t and to others who have contributed to the realization of this graduation. A special word of thanks in particular to A. Dahanayake, W. Quak, W. Gerhardt, P. van Oosterom and T. Tijssen. Franklin Monteiro i GML and Complex Features Abstract Abstract 3BCFDC10-2A16-DED4.doc version 19/10/2001 ii/66 final Geographic Information Systems (GIS) are information systems that centre on geographic data, that is data related to a location on earth. In GISs geographic information usually is abstracted to features (geographic classes). The features are the units of geographic information. Developments in the GIS technology have indicated that connections between the GISs are required and a network of GISs over the internet is considered.