DOCSLIB.ORG

Wikipedia, the Free Encyclopedia

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Create account Log in Article Talk Read Edit Search HTML From Wikipedia, the free encyclopedia For the use of HTML on Wikipedia, see Help:HTML in wikitext. Main page HyperText Markup Language (HTML) is HTML Contents the main markup language for displaying (HyperText Markup Language) Featured content web pages and other information that can Current events Filename .html, .htm be displayed in a web browser. extension Random article Donate to Wikipedia HTML is written in the form of HTML Internet media text/html elements consisting of tags enclosed in type Interaction angle brackets (like <html>), within the Type code TEXT Help web page content. HTML tags most Uniform Type public.html About Wikipedia commonly come in pairs like <h1> and Identifier Community portal </h1>, although some tags, known as Developed by World Wide Web Recent changes empty elements, are unpaired, for example Consortium & WHATWG Contact Wikipedia <img>. The first tag in a pair is the start Type of format Markup language Toolbox tag, the second tag is the end tag (they Extended from SGML are also called opening tags and closing Print/export tags). In between these tags web Extended to XHTML Languages designers can add text, tags, comments Standard(s) ISO/IEC 15445 Afrikaans and other types of text-based content. W3C HTML 4.01 Alemannisch The purpose of a web browser is to read W3C HTML5 (draft) اﻟﻌﺮﺑﯿﺔ HTML documents and compose them into Aragonés visible or audible web pages. The browser does not display the HTML tags, but uses the Azərbaycanca tags to interpret the content of the page. বাংলা Башортса HTML elements form the building blocks of all websites. HTML allows images and Беларуская objects to be embedded and can be used to create interactive forms. It provides a беларуская means to create structured documents by denoting structural semantics for text such (тарашкевіца) as headings, paragraphs, lists, links, quotes and other items. It can embed scripts in Български languages such as JavaScript which affect the behavior of HTML webpages. Boarisch Web browsers can also refer to Cascading Style Sheets (CSS) to define the Bosanski appearance and layout of text and other material. The W3C, maintainer of both the Brezhoneg HTML and the CSS standards, encourages the use of CSS over explicitly presentational Català HTML markup.[1] Чвашла Česky Contents [hide] Corsu 1 History Cymraeg 1.1 Origins Dansk 1.2 First specifications Deutsch 1.3 Version history of the standard Eesti 1.3.1 HTML version timeline Ελληνικά 1.3.2 HTML draft version timeline Español 1.3.3 XHTML versions Esperanto 2 Markup Euskara 2.1 Elements Element examples 2.1.1 ﻓﺎرﺳﯽ Føroyskt 2.1.2 Attributes Français 2.2 Character and entity references Frysk 2.3 Data types Furlan 2.4 Document type declaration Gaeilge 3 Semantic HTML Galego 4 Delivery 한국어 4.1 HTTP Հայերեն 4.2 HTML e-mail िहदी 4.3 Naming conventions Hornjoserbsce 4.4 HTML Application Hrvatski 5 Current variations Bahasa Indonesia 5.1 SGML-based versus XML-based HTML Interlingua 5.2 Transitional versus strict Íslenska 5.3 Frameset versus transitional Italiano 5.4 Summary of specification versions Hypertext features not in HTML 6 עברית Basa Jawa 7 WYSIWYG editors ქართული 8 See also Қазақша 9 References Kiswahili 10 External links Kurdî Кыргызча History [edit] Latgaļu Latviešu Origins [edit] Lëtzebuergesch In 1980, physicist Tim Berners-Lee, who was a contractor at Lietuvių CERN, proposed and prototyped ENQUIRE, a system for CERN Lumbaart The historic logo researchers to use and share documents. In 1989, Berners-Lee Magyar made by the W3C wrote a memo proposing an Internet-based hypertext system.[2] Македонски Berners-Lee specified HTML and wrote the browser and server മലയാളം software in the last part of 1990. In that year, Berners- मराठी Lee and CERN data systems engineer Robert Cailliau Bahasa Melayu collaborated on a joint request for funding, but the Монгол project was not formally adopted by CERN. In his personal notes[3] from 1990 he lists[4] "some of the Nederlands many areas in which hypertext is used" and puts an नपे ाल भाषा encyclopedia first. 日本語 norsk (bokmål) First specifications [edit] norsk (nynorsk) Олык марий The first publicly available description of HTML was a Oʻzbekcha document called "HTML Tags", first mentioned on the Internet by Berners-Lee in late 1991.[5][6] It describes ਪੰਜਾਬੀ 18 elements comprising the initial, relatively simple Tim Berners-Lee design of HTML. Except for the hyperlink tag, these Polski were strongly influenced by SGMLguid, an in-house Português SGML based documentation format at CERN. Eleven of these elements still exist in Qaraqalpaqsha HTML 4.[7] Română HyperText Markup Language is a markup language that web browsers use to interpret Русский and compose text, images and other material into visual or audible web pages. Default Shqip characteristics for every item of HTML markup are defined in the browser, and these Simple English characteristics can be altered or enhanced by the web page designer's additional use of Slovenčina CSS. Many of the text elements are found in the 1988 ISO technical report TR 9537 Slovenščina Techniques for using SGML , which in turn covers the features of early text formatting Soomaaliga languages such as that used by the RUNOFF command developed in the early 1960s ﮐﻮردی for the CTSS (Compatible Time-Sharing System) operating system: these formatting Српски / srpski commands were derived from the commands used by typesetters to manually format Srpskohrvatski / српскохрватски documents. However, the SGML concept of generalized markup is based on elements Suomi (nested annotated ranges with attributes) rather than merely print effects, with also the Svenska separation of structure and processing; HTML has been progressively moved in this Tagalog direction with CSS. ¾Á¢ú Berners-Lee considered HTML to be an application of SGML. It was formally defined as such by the Internet Engineering Task Force (IETF) with the mid-1993 publication of the ไทย first proposal for an HTML specification: "Hypertext Markup Language (HTML)" Internet- Тоик Draft by Berners-Lee and Dan Connolly, which included an SGML Document Type Türkçe Definition to define the grammar.[8] The draft expired after six months, but was notable Türkmençe for its acknowledgement of the NCSA Mosaic browser's custom tag for embedding in- Українська line images, reflecting the IETF's philosophy of basing standards on successful prototypes.[9] Similarly, Dave Raggett's competing Internet-Draft, "HTML+ (Hypertext اردو Tiếng Việt Markup Format)", from late 1993, suggested standardizing already-implemented [features like tables and fill-out forms.[10 ייִדיש Yorùbá After the HTML and HTML+ drafts expired in early 1994, the IETF created an HTML 粵 語 Working Group, which in 1995 completed "HTML 2.0", the first HTML specification Žemaitėška intended to be treated as a standard against which future implementations should be 中文 based.[9] Published as Request for Comments 1866, HTML 2.0 included ideas from the HTML and HTML+ drafts.[11] The 2.0 designation was intended to distinguish the new edition from previous drafts.[12] Further development under the auspices of the IETF was stalled by competing interests. Since 1996, the HTML specifications have been maintained, with input from commercial software vendors, by the World Wide Web Consortium (W3C).[13] However, in 2000, HTML also became an international standard (ISO/IEC 15445:2000). HTML 4.01 was published in late 1999, with further errata published through 2001. In 2004 development began on HTML5 in the Web Hypertext Application Technology Working Group (WHATWG), which became a joint deliverable with the W3C in 2008. Version history of the standard [edit] HTML version timeline [edit] HTML November 24, 1995 HTML and HTML5 HTML 2.0 was published as IETF RFC Dynamic HTML 1866 . Supplemental RFCs added XHTML capabilities: XHTML Basic November 25, 1995: RFC 1867 XHTML Mobile Profile and C-HTML (form-based file upload) Canvas element Character encodings May 1996: RFC 1942 (tables) Document Object Model Document Object Model August 1996: RFC 1980 (client- Brow ser Object Model side image maps) Font family January 1997: RFC 2070 HTML editor (internationalization) HTML element January 1997 HTML Frames HTML 3.2[14] was published as a W3C HTML5 Audio and HTML5 video Recommendation. It was the first HTML scripting Web brow ser engine version developed and standardized Tag soup exclusively by the W3C, as the IETF Quirks mode had closed its HTML Working Group in Style sheets September 1996.[15] Unicode and HTML HTML 3.2 dropped math formulas W3C and WHATWG entirely, reconciled overlap among Web colors various proprietary extensions and Web storage adopted most of Netscape's visual WebGL markup tags. Netscape's blink element Comparison of and Microsoft's marquee element were document markup languages omitted due to a mutual agreement w eb brow sers between the two companies.[13] A layout engines for markup for mathematical formulas HTML similar to that in HTML was not HTML5 standardized until 14 months later in HTML5 canvas MathML. HTML5 media December 1997 Non-standard HTML HTML 4.0[16] was published as a W3C XHTML (1.1) Recommendation. It offers three V · T · E · variations: Strict, in which deprecated elements are forbidden, Transitional, in which deprecated elements are allowed, Frameset, in which mostly only frame related elements are allowed; Initially code-named "Cougar",[17] HTML 4.0 adopted many browser-specific element types and attributes, but at the same time sought to phase out Netscape's visual markup features by marking them as deprecated in favor of style sheets. HTML 4 is an SGML application conforming to ISO 8879 – SGML.[18] April 1998 HTML 4.0[19] was reissued with minor edits without incrementing the version number.
Recommended publications
  • Beautiful Soup Documentation Release 4.4.0

    Beautiful Soup Documentation Release 4.4.0

    Beautiful Soup Documentation Release 4.4.0 Leonard Richardson Dec 24, 2019 Contents 1 Getting help 3 2 Quick Start 5 3 Installing Beautiful Soup 9 3.1 Problems after installation........................................9 3.2 Installing a parser............................................ 10 4 Making the soup 13 5 Kinds of objects 15 5.1 Tag .................................................... 15 5.2 NavigableString .......................................... 17 5.3 BeautifulSoup ............................................ 18 5.4 Comments and other special strings................................... 18 6 Navigating the tree 21 6.1 Going down............................................... 21 6.2 Going up................................................. 24 6.3 Going sideways.............................................. 25 6.4 Going back and forth........................................... 27 7 Searching the tree 29 7.1 Kinds of filters.............................................. 29 7.2 find_all() .............................................. 32 7.3 Calling a tag is like calling find_all() ............................... 36 7.4 find() ................................................. 36 7.5 find_parents() and find_parent() .............................. 37 7.6 find_next_siblings() and find_next_sibling() .................... 37 7.7 find_previous_siblings() and find_previous_sibling() .............. 38 7.8 find_all_next() and find_next() ............................... 38 7.9 find_all_previous() and find_previous() .......................
  • Introduction to HTML5

    Introduction to HTML5

    "Charting the Course ... ... to Your Success!" Introduction to HTML5 Course Summary Description HTML5 is not merely an improvement on previous versions, but instead a complete re-engineering of browser-based markup. It transforms HTML from a document description language to an effective client platform for hosting web applications. For the first time developers have native support for creating charts and diagrams, playing audio and video, caching data locally and validating user input. When combined with related standards like CSS3, Web Sockets and Web Workers it is possible to build ‘Rich Web Applications’ that meet modern usability requirements without resorting to proprietary technologies such as Flash and Silverlight. This course enables experienced developers to make use of all the features arriving in HTML5 and related specifications. During the course delegates incrementally build a user interface for a sample web application, making use of all the new features as they are taught. By default the course uses the Dojo Framework to simplify client-side JavaScript and delegates are presented with server-side code written in Spring MVC 3. Other technology combinations are possible if required. Topics Review of the Evolution of HTML Playing Audio and Video Better Support for Data Entry Hosting Clients in HTML5 Support for Drawing Images and Standards Related to HTML5 Diagrams Prerequisites Students should have experience of web application development in a modern environment such as JEE, ASP .NET, Ruby on Rails or Django. They must be very familiar with HTML4 and/or XHTML and the fundamentals of programming in JavaScript. If this is not the case then an additional ‘primer’ day can be added to the delivery.
  • Guidelines for the Preservation of Video Recordings IASA-TC 06

    Guidelines for the Preservation of Video Recordings IASA-TC 06

    Technical Committee Standards, Recommended Practices, and Strategies Guidelines for the Preservation of Video Recordings IASA-TC 06 Part B. Video Signal, Preservation Concepts, and Target Formats From IASA-TC 06, Edition 1 Revised version, 2019 B-1 Revised version, 2019 Guidelines for the Preservation of Video Recordings Table of Contents B.1 The Video Signal and Bitstreams: Format and Features B-6 B.1.1 Conventional video carriers and formatting B-6 B.1.1.1 Conventional video carriers and the video signal B-6 Sidebar: the noun video B-6 B.1.1.2 Conventional carriers compared to file-based video B-6 B.1.1.3 Broadcast standards and the formatting of video recordings B-7 B.1.2 Analogue video unpacked, part one: key features and variants B-8 B.1.2.1 Illusion of motion from a stream of still images B-9 B.1.2.2 Sound data is carried in parallel with picture data B-9 B.1.2.3 Picture data consists of sets of horizontal scan lines B-10 B.1.2.4 Horizontal lines of picture data may be interlaced B-11 B.1.2.5 Movies on film can be recorded as video B-11 B.1.2.6 Timing: video signal elements must be synchronized (RS-170) B-12 B.1.2.7 Range of picture brightnesses and blanking “brightness” B-14 B.1.3 Analogue video unpacked, part two: key features and variants continued B-16 B.1.3.1 Colour encoding for video on conventional carriers B-16 B.1.3.1.1 Composite video B-17 B.1.3.1.2 S-video B-18 B.1.3.1.3 Colour-difference component video B-18 Sidebar: colour and tonal specifications for digital video and related matters B-20 B.1.3.2 Ancillary data B-22
  • Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe

    Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe

    Weblint: Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe Abstract Weblint is a utility for checking the syntax and style of HTML pages. It was inspired by lint [15], which performs a similar function for C and C++ programmers. Weblint does not aspire to be a strict SGML validator, but to provide helpful comments for humans. The importance of quality assurance for web sites is introduced, and one particular area, validation of HTML, is described in more detail. The bulk of the paper is devoted to weblint: what it is, how it is used, and the design and implementation of the current development version. 1. Introduction The conclusion opens with a summary of the information and opinions given in this paper. A Web sites are becoming an increasingly critical part of selection of the lessons learned over the last four years how many companies do business. For many companies is given, followed by plans for the future, and related web sites are their business. It is therefore critical that ideas. owners of web sites perform regular testing and analysis, to ensure quality of service. 2. Web Site Quality Assurance There are many different checks and analyses which The following are some of the questions you should be you can run on a site. For example, how usable is your asking yourself if you have a web presence. I have site when accessed via a modem? An incomplete list of limited the list to those points which are relevant to similar analyses are given at the start of Section 2.
  • XML Signature/Encryption — the Basis of Web Services Security

    XML Signature/Encryption — the Basis of Web Services Security

    Special Issue on Security for Network Society Falsification Prevention and Protection Technologies and Products XML Signature/Encryption — the Basis of Web Services Security By Koji MIYAUCHI* XML is spreading quickly as a format for electronic documents and messages. As a consequence, ABSTRACT greater importance is being placed on the XML security technology. Against this background research and development efforts into XML security are being energetically pursued. This paper discusses the W3C XML Signature and XML Encryption specifications, which represent the fundamental technology of XML security, as well as other related technologies originally developed by NEC. KEYWORDS XML security, XML signature, XML encryption, Distributed signature, Web services security 1. INTRODUCTION 2. XML SIGNATURE XML is an extendible markup language, the speci- 2.1 Overview fication of which has been established by the W3C XML Signature is an electronic signature technol- (WWW Consortium). It is spreading quickly because ogy that is optimized for XML data. The practical of its flexibility and its platform-independent technol- benefits of this technology include Partial Signature, ogy, which freely allows authors to decide on docu- which allows an electronic signature to be written on ment structures. Various XML-based standard for- specific tags contained in XML data, and Multiple mats have been developed including: ebXML and Signature, which enables multiple electronic signa- RosettaNet, which are standard specifications for e- tures to be written. The use of XML Signature can commerce transactions, TravelXML, which is an EDI solve security problems, including falsification, spoof- (Electronic Data Interchange) standard for travel ing, and repudiation. agencies, and NewsML, which is a standard specifica- tion for new distribution formats.
  • HTML5 and the Open Web Platform

    HTML5 and the Open Web Platform

    HTML5 and the Open Web Platform Stuttgart 28 May 2013 Dave Raggett <[email protected]> The Open Web Platform What is the W3C? ● International community where Members, a full-time staff and the public collaborate to develop Web standards ● Led by Web inventor Tim Berners-Lee and CEO Jeff Jaffe ● Hosted by MIT, ERCIM, Keio and Beihang ● Community Groups open to all at no fee ● Business Groups get more staff support ● Technical Working Groups ● Develop specs into W3C Recommendations ● Participants from W3C Members and invited experts ● W3C Patent process for royalty free specifications 3 Who's involved ● W3C has 377 Members as of 11 May 2013 ● To name just a few ● ACCESS, Adobe, Akamai, Apple, Baidu, BBC, Blackberry (RIM), BT, Canon, Deutsche Telekom, eBay, Facebook, France Telecom, Fujitsu, Google, Hitachi, HP, Huawei, IBM, Intel, LG, Microsoft, Mozilla, NASA, NEC, NTT DoCoMo, Nuance, Opera Software, Oracle, Panasonic, Samsung, Siemens, Sony, Telefonica, Tencent, Vodafone, Yandex, … ● Full list at ● http://www.w3.org/Consortium/Member/List 4 The Open Web Platform 5 Open Web Platform ● Communicate with HTTP, Web Sockets, XML and JSON ● Markup with HTML5 ● Style sheets with CSS ● Rich graphics ● JPEG, PNG, GIF ● Canvas and SVG ● Audio and Video ● Scripting with JavaScript ● Expanding range of APIs ● Designed for the World's languages ● Accessibility with support for assistive technology 6 Hosted and Packaged Apps ● Hosted Web apps can be directly loaded from a website ● Packaged Web apps can be locally installed on a device and run without the need for access to a web server ● Zipped file containing all the necessary resources ● Manifest file with app meta-data – Old work on XML based manifests (Web Widgets) – New work on JSON based manifests ● http://w3c.github.io/manifest/ ● Pointer to app's cache manifest ● List of required features and permissions needed to run correctly ● Runtime and security model for web apps ● Privileged apps must be signed by installation origin's private key 7 HTML5 Markup ● Extensive range of features ● Structural, e.g.
  • Multilingual Aspects in Speech and Multimodal Interfaces

    Multilingual Aspects in Speech and Multimodal Interfaces

    Multilingual Aspects in Speech and Multimodal Interfaces Paolo Baggia Director of International Standards 1 Outline Loquendo Today Do we need multilingual applications? Voice is different from text? Current Solutions – a Tour: Speech Interface Framework Today Voice Applications Speech Recognition Grammars Speech Prompts Pronunciation Lexicons Discussion Points 2 Company Profile . Privately held company (fully owned by Telecom Italia), founded in 2001 as spin-off from Telecom Italia Labs, capitalizing on 30yrs experience and expertise in voice processing. Global Company, leader in Europe and South America for award-winning, high quality voice technologies (synthesis, recognition, authentication and identification) available in 30 languages and 71 voices. Multilingual, proprietary technologies protected Munich over 100 patents worldwide London . Financially robust, break-even reached in 2004, revenues and earnings growing year on year Paris . Offices in New York. Headquarters in Torino, Madrid local representative sales offices in Rome, Torino New York Madrid, Paris, London, Munich Rome . Flexible: About 100 employees, plus a vibrant ecosystem of local freelancers. 3 International Awards Market leader-Best Speech Engine Speech Industry Award 2007, 2008, 2009, 2010 2010 Speech Technology Excellence Award CIS Magazine 2008 Frost & Sullivan European Telematics and Infotainment Emerging Company of the Year Award Loquendo MRCP Server: Winner of 2008 IP Contact Center Technology Pioneer Award Best Innovation in Automotive Speech Synthesis Prize AVIOS- SpeechTEK West 2007 Best Innovation in Expressive Speech Synthesis Prize AVIOS- SpeechTEK West 2006 Best Innovation in Multi-Lingual Speech Synthesis Prize AVIOS- SpeechTEK West 2005 4 Do We Need Multilingual Applications? Yes, because … . We live in a Multicultural World . Movement of students/professionals, migration, tourism .
  • Improving E-Learning Environments for Pen and Multi-Touch Based Interaction a Study Case on Blog Tools and Mobile Devices

    Improving E-Learning Environments for Pen and Multi-Touch Based Interaction a Study Case on Blog Tools and Mobile Devices

    eLmL 2014 : The Sixth International Conference on Mobile, Hybrid, and On-line Learning Improving e-Learning Environments for Pen and Multi-touch Based Interaction A study case on blog tools and mobile devices André Constantino da Silva Heloísa Vieira da Rocha Institute of Computing (PG) Institute of Computing, NIED UNICAMP, IFSP UNICAMP Campinas, Brazil, Hortolândia, Brazil Campinas, Brazil [email protected] [email protected] Abstract — e-Learning environments are applications that use power to process Web pages. So, it is possible to access blog the Web infra-structure to support teaching and learning tools, read the messages, post new messages and write activities; they are designed to have good usability using a comments through mobile devices. But, it is important to desktop computer with keyboard, mouse and high resolution consider that these tools (and so their Web pages) are medium-size display. Devices equipped with pen and touch developed to be accessed by desktop computers equipped sensitive screen have enough computational power to render with keyboard, mouse and a medium size display; in your Web pages and allow users to navigate through the e-learning previous work we described that when a user interface environments. But, pen-based or touch sensitive devices have a designed for a set of interaction styles is accessed by a different input style; decreasing the usability of e-learning different set of interaction styles the users face interaction environments due the interaction modality change. To work on problems [5]. Another problem is that it is not possible to mobile contexts, e-learning environments must be improved to consider the interaction through pen and touch.
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • EAN.UCC XML Architectural Guide Version 1.0 July 2001

    EAN.UCC XML Architectural Guide Version 1.0 July 2001

    EAN·UCC System The Global Language of Business ® EAN.UCC XML Architectural Guide Version 1.0 July 2001 COPYRIGHT 2001, EAN INTERNATIONAL™ AND UNIFORM CODE COUNCIL, INC.Ô EAN.UCC Architectural Guide EAN·UCC System The Global Language of Business ® Table of Contents Document History........................................................................................................................ 4 1. Introduction............................................................................................................................ 5 1.1 Overview......................................................................................................................................................................... 5 1.1.1 Extensions in UML............................................................................................................................................... 5 1.1.1.1 Common Core Components ....................................................................................................................... 6 1.2 In A Nutshell: A Business Process Document......................................................................................................... 6 1.3 Other Related Documents ............................................................................................................................................ 7 2. Implementation Guidelines ..................................................................................................... 8 2.1 Schema Language ........................................................................................................................................................
  • XML for Java Developers G22.3033-002 Course Roadmap

    XML for Java Developers G22.3033-002 Course Roadmap

    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
  • World-Wide Web Proxies

    World-Wide Web Proxies

    World-Wide Web Proxies Ari Luotonen, CERN Kevin Altis, Intel April 1994 Abstract 1.0 Introduction A WWW proxy server, proxy for short, provides access to The primary use of proxies is to allow access to the Web the Web for people on closed subnets who can only access from within a firewall (Fig. 1). A proxy is a special HTTP the Internet through a firewall machine. The hypertext [HTTP] server that typically runs on a firewall machine. server developed at CERN, cern_httpd, is capable of run- The proxy waits for a request from inside the firewall, for- ning as a proxy, providing seamless external access to wards the request to the remote server outside the firewall, HTTP, Gopher, WAIS and FTP. reads the response and then sends it back to the client. cern_httpd has had gateway features for a long time, but In the usual case, the same proxy is used by all the clients only this spring they were extended to support all the within a given subnet. This makes it possible for the proxy methods in the HTTP protocol used by WWW clients. Cli- to do efficient caching of documents that are requested by ents don’t lose any functionality by going through a proxy, a number of clients. except special processing they may have done for non- native Web protocols such as Gopher and FTP. The ability to cache documents also makes proxies attrac- tive to those not inside a firewall. Setting up a proxy server A brand new feature is caching performed by the proxy, is easy, and the most popular Web client programs already resulting in shorter response times after the first document have proxy support built in.