Packaged Web Apps Widgets Packaging and XML Configuration Second EditionAbstract. This specification updates the Widget Packaging and XML Configuration, and addresses some errata found in the original recommendation. It also updates the name of the specification, to be more in vogue with industry trends towards the naming of this class of application. This specification standardizes a packaging format and metadata for a class of software. Unlike traditional user interface widgets e. HTML and then packaged for distribution. Examples range from. The. specification relies on PKWares Zip specification as the archive format, XML as a. The packaging format acts as a. The configuration document is an XML vocabulary. The steps for. processing a widget package describe the expected behavior and means of error handling. This specification is part of the Widgets family of specifications. Status of this Document This section describes the status of this document at the time of its. Other documents may supersede this document. A list of current W3. C. publications and the latest revision of this technical report can be found in the. W3. C technical reports index at. TR. This is the 2. November 2. 01. 2 Recommendation of the Widget Packaging and XML Configuration specification. This document is produced by the Web. File Manager Commanders. The Norton Commander is the most useful DOS program ever written. Symantec The makers of NC dropped the ball when Windows 95 arrived. Attempts were made to archive images in all public folders prior to the replacement of Webshots with Smile. Search and download your photos with your Webshots username. Installing and Running Cumulus. What operating systems does Cumulus run on 1. Where do I find the Cumulus installer 1. What do I need to get right when. A widget file extension is the text string that caseinsensitively matches the string. WGt. WgT, etc. are all valid. The podcast craze of the past several years shows no signs of slowing down, and while every armchair broadcaster with a voice recorder app is eager to get in the game. CYXCCgkurk/T780xIdFaII/AAAAAAAAADw/vwk-TEvcaxU/s1600/2_file_open.png' alt='Zip File Does Not Appear To Be A Valid Archive' title='Zip File Does Not Appear To Be A Valid Archive' />Applications WG, part of the Rich Web. Client Activity in the W3. C Interaction. Domain. This document has been reviewed by W3. C Members, by software developers, and by other W3. C groups and interested parties, and is endorsed by the Director as a W3. C Recommendation. It is a stable document and may be used as reference material or cited from another document. Where archive is a new or existing zip archive and inpath is a directory or file path optionally including wildcards. When given the name of an existing zip archive. Using the FOR command to copy files listed in a text file. W3. Cs role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. The public is encouraged to send comments to the Web. Apps Working Groups public mailing list public webappsw. This document was produced by a group operating under the 5 February 2. W3. C Patent. Policy. W3. C maintains a public list of any patent disclosures made in connection with the. An individual who has actual knowledge of a patent which the individual. Essential. Claims must disclose the information in accordance with section 6 of the. W3. C Patent Policy. Table of Contents. Introduction. 1. 1 Design Goals and Requirements. How This Document is Organized. Typographic Conventions. The Widget Family of Specifications. Conformance. 3 Definitions. Character Definitions. User Agents. 4. 1 Optional Aspects of the Zip Specification. Zip Archive. 5. 1 Compression Methods. Version of Zip Needed to Extract a File Entry. Zip Relative Paths. Interoperability Considerations. Widget Packages. 6. Invalid Widget Package. Files and Folders. Reserved File and Folder Names. Digital Signatures. Start Files. 6. 5. Custom Start File. Default Start Files. Icons. 6. 6. 1 Custom Icons. Default Icons. 6. Media Type. 6. 8 File Extension. Configuration Document. Example Configuration Document. Namespace. 7. 3 Proprietary Extensions. Types of Attributes. Global Attributes. The xml lang Attribute. The dir Attribute. Examples of Usage. The widget Element and its Attributes. The id Attribute. The version Attribute. The height Attribute. The width Attribute. The viewmodes Attribute. The defaultlocale attribute. Example of Usage. Example of Usage of the defaultlocale attribute 7. The name Element and its Attributes. The short Attribute. Example of Usage. The description Element and its Attributes. Example of Usage. The author Element and its Attributes. The href Attribute. The email Attribute. Example of Usage. The license Element and its Attributes. The href Attribute. Example of Usage. The icon Element and its Attributes. The src Attribute. The width Attribute. The height Attribute. Example of Usage. The content Element and its Attributes. The src Attribute. The type Attribute. The encoding Attribute. Example of Usage. The feature Element and its Attributes. The name Attribute. The required Attribute. Example of Usage. The param Element and its Attributes. The name Attribute. The value Attribute. Example of Usage. The preference Element and its Attributes. The name Attribute. The value Attribute. The readonly Attribute. Example of Usage. The span Element and its Attributes. Example of Usage. Internationalization and localization. Bidirectional text. Localization Model. Folder based localization. Cab Installer Windows Ce 6.0'>Cab Installer Windows Ce 6.0. Element Based Localization. Localization Examples. Simple Example. 8. Complex Example. 8. Fallback Behavior Example. Steps for Processing a Widget Package. Processing Rules. Rule for Verifying a Zip Archive. Rule for Extracting File Data from a File Entry. Rule for Finding a File Within a Widget Package. Rule for Determining Directionality. Rule for Getting a Single Attribute Value. Rule for Getting a List of Keywords From an Attribute. Rule for Verifying a File Entry. Rule for Getting Text Content. Rule for Getting Text Content with Normalized White Space. Rule for Parsing a Non negative Integer. Rule for Identifying the Media Type of a File. Rule for Deriving the user agent locales. Rule for Determining if a Potential Zip Archive is a Zip. Archive. Step 1 Acquire a Potential Zip Archive. Acquisition of a Potential Zip archive Labeled with a Media Type. Acquisition of Potential Zip Archive not Labeled with a Media. Type. Step 2 Verify the Zip Archive. Step 3 Set the Configuration Defaults. Step 4 Locate and Process the Digital Signature. Step 5 Derive the User Agents Locales. Step 6 Locate the Configuration Document. Step 7 Process the Configuration. Document. 9. 1. 1 Terminology Used in Processing Algorithm. Algorithm to Process a Configuration Document. Step 8 Locate the Start File. Step 9 Process the Default Icons. Appendix. Media Type Registration for applicationwidget. Linking To a Widget Package From a HTML Document. Table of Elements and Their Attributes. Acknowledgements. Normative References. Informative References. Introduction. This section is non normative. Widgets are full fledged client side applications that are authored using. Corel Photo Paint Windows Xp more. Web standards such as HTML and packaged for distribution. They are typically downloaded and. Web pages and run in a Web browser. Examples range from. Whatsapp Nokia C6-01. Widgets Landscape for more. This specification is intended to specify a part of the Web platform closely related to HTML. Design Goals and Requirements. This section is non normative. The design goals and requirements for this specification are documented in theWidgets Requirements document. This document addresses. Packaging and Configuration Document of the 3. April 2. 00. 9 Working Draft of the Widgets Requirements Document Packaging. Format see packaging format. Media. Type see the valid widget media type. File. Extension see widget file extension. Internal. Abstract Structure see Zip archive and widget. Reserved. Resource Names see reserved file names table. Addressing. Scheme see valid path. Multilingual. File Names see Zip relative path, particularly in respect to support for UTF 8. Localization. Guidelines see element based localization, folder based. Automatic. Localization see element based localization, folder based. Device. Independent Delivery all aspects of this document where developed with this. Data. Compression see the valid compression methods. Derive the Media Type of Resources see the rule for identifying the media type of a. Format and. Schema see configuration document, table of configuration. Widgets Relax NG Schema for the configuration. JAR file format Wikipedia. A JAR Java ARchive is a packagefile format typically used to aggregate many Java class files and associated metadata and resources text, images, etc. JAR files are archive files that include a Java specific manifest file. They are built on the ZIP format and typically have a. A JAR file allows Java runtimes to efficiently deploy an entire application, including its classes and their associated resources, in a single request. JAR file elements may be compressed, shortening download times. A JAR file may contain a manifest file, that is located at META INFMANIFEST. MF. The entries in the manifest file describe how to use the JAR file. For instance, a Classpath entry can be used to specify other JAR files to load with the JAR. The contents of a JAR file may be extracted using any standard decompression software, or the jar command line utility jar xf foo. SecurityeditDevelopers can digitally sign JAR files. In that case, the signature information becomes part of the embedded manifest file. The JAR itself is not signed, but instead every file inside the archive is listed along with its checksum it is these checksums that are signed. Multiple entities may sign the JAR file, changing the JAR file itself with each signing, although the signed files themselves remain valid. When the Java runtime loads signed JAR files, it can validate the signatures and refuse to load classes that do not match the signature. It can also support sealed packages, in which the Classloader will only permit Java classes to be loaded into the same package if they are all signed by the same entities. This prevents malicious code from being inserted into an existing package, and so gaining access to package scoped classes and data. The content of JAR files may be obfuscated to make reverse engineering more difficult. Executable JAR fileseditAn executable Java program can be packaged in a JAR file, along with any libraries the program uses. Executable JAR files have the manifest specifying the entry point class with Main Class my. Programs. My. Class and an explicit Class Path and the cp argument is ignored. Some operating systems can run these directly when clicked. The typical invocation is java jar foo. Native launchers can be created on most platforms. For instance, Microsoft Windows users who prefer having Windows EXE files can use tools such as JSmooth, Launch. J, Win. Run. 4J or Nullsoft Scriptable Install System to wrap single JAR files into executables. ManifesteditA manifest file is a metadata file contained within a JAR. It defines extension and package related data. It contains name value pairs organized in sections. If a JAR file is intended to be used as an executable file, the manifest file specifies the main class of the application. The manifest file is named MANIFEST. MF. The manifest directory has to be the first entry of the compressed archive. SpecificationseditThe manifest appears at the canonical location META INFMANIFEST. MF. 7 There can be only one manifest file in an archive and it must be at that location. The content of the manifest file in a JAR file created with version 1. Java Development Kit is the following. Manifest Version 1. The name is separated from its value by a colon. The default manifest shows that it conforms to version 1. The manifest can contain information about the other files that are packaged in the archive. Manifest contents depend on the intended use for the JAR file. The default manifest file makes no assumptions about what information it should record about other files, so its single line contains data only about itself. JAR files created only for the purpose of archiving do not use the MANIFEST. MF file. Most uses of JAR files go beyond simple archiving and compression and require special information in the manifest file. ApplicationseditIf an application is contained in a JAR file, the Java Virtual Machine needs to know the applications entry point. An entry point is any class with a public static void mainString args method. This information is provided in the Main Class header, which has the general form. Main Class com. My. Class. Name. In this example com. My. Class. Name. main executes at application launch. Package SealingeditOptionally, a package within a JAR file can be sealed, which means that all classes defined in that package are archived in the same JAR file. A package might be sealed to ensure version consistency among the classes in the software or as a security measure. To seal a package, a Name entry needs to appear, followed by a Sealed header, such as Name my. Companymy. PackageSealed true. The Name headers value is the packages relative pathname. Note that it ends with a to distinguish it from a filename. Any headers following a Name header, without any intervening blank lines, apply to the file or package specified in the Name header. In the above example, because the Sealed header occurs after the Name my. Companymy. Package header with no intervening blank lines, the Sealed header applies only to the package my. Companymy. Package. Package VersioningeditSeveral manifest headers hold versioning information. One set of headers can be assigned to each package. The versioning headers appear directly beneath the Name header for the package. This example shows all the versioning headers Name javautilSpecification Title Java Utility ClassesSpecification Version 1. Specification Vendor Sun Microsystems, Inc. Implementation Title java. Implementation Version build. Implementation Vendor Sun Microsystems, Inc. DependencieseditThe MANIFEST. MF file can be used to specify all the classes that must be loaded for an application to be able to run. Note that Class Path entries are delimited with spaces, not with the system path delimiter Class Path. Apache Ant ZipJAR supporteditThe Apache Ant build tool has its own package to read and write Zip and JAR archives, including support for Unixfilesystem extensions. The org. apache. tools. Apache Software Foundation license and is designed to be usable outside Ant. Related formatseditSeveral related file formats build on the JAR format WAR Web application archive files, also Java archives, store XML files, Java classes, Java. Server Pages and other objects for Web Applications. RAR resource adapter archive files not to be confused with the RAR file format, also Java archives, store XML files, Java classes and other objects for J2. EE Connector Architecture JCA applications. EAR enterprise archive files provide composite Java archives that combine XML files, Java classes and other objects including JAR, WAR and RAR Java archive files for Enterprise Applications. SAR service archive is similar to EAR. It provides a service. JAR files. APK Android Application Package, a variant of the Java archive format, is used for Android applications. PAR Plan ARchive supported by Eclipse Virgo. OSGi application server, allows the deployment of multi bundle OSGi applications as a single archive and provides isolation from other PAR based applications deployed in the same server. KAR Karaf ARchive supported by Apache Karaf OSGi application server, allows the deployment of multi bundle, multi feature OSGi applications. See alsoeditReferenceseditExternal linksedit.