The Extensible Markup Language (XML) is a World Wide Web ConsortiumW3C-recommended general-purpose markup language for creating special-purpose markup languages. It is a simplified subset of Standard Generalized Markup LanguageSGML, capable of describing many different kinds of data. Its primary purpose is to facilitate the sharing of data across different systems, particularly systems connected via the Internet. Languages based on XML (for example, Resource Description FrameworkRDF, RSS (file format)RSS, MathML, XHTML, Scalable Vector GraphicsSVG, and cXML) are defined in a formal way, allowing programs to modify and validate documents in these languages without prior knowledge of their form.
History - By the mid-1990s some practitioners of SGML had gained experience with the then-new World Wide Web, and believed that SGML offered solutions to some of the problems the Web was likely to face as it grew. Jon Bosak argued that the W3C should sponsor an "SGML on the Web" activity. After some resistance he was authorized to launch that activity in mid-1996, albeit with little involvement by or support from the W3C leadership. Bosak was well-connected in the small community of people who had experience both in SGML and the Web. He received support in his efforts from Microsoft.XML was designed by an eleven-member Working Group supported by an (approximately) 150-member Interest Group. Technical debate took place on the Interest Group mailing list and issues were resolved by consensus or, when that failed, majority vote of the Working Group. James Clark (XML expert)James Clark served as Technical Lead of the Working Group, notably contributing the empty-element "" syntax and the name "XML". Other names that had been put forward for consideration included "MAGMA" (Minimal Architecture for Generalized Markup Applications), "SLIM" (Structured Language for Internet Markup) and "MGML" (Minimal Generalized Markup Language). The co-editors of the specification were originally Tim Bray and Michael Sperberg-McQueen. Halfway through the project Bray accepted a consulting engagement with Netscape Communications CorporationNetscape, provoking vociferous protests from Microsoft. Bray was temporarily asked to resign the editorship. This led to intense dispute in the Working Group, eventually solved by the appointment of Microsoft's Jean Paoli as a third co-editor.The XML Working Group never met face-to-face; the design was accomplished using a combination of email and weekly teleconferences. The major design decisions were reached in twenty weeks of intense work between July and November of 1996. Further design work continued through 1997, and XML 1.0 became a W3C Recommendation on February 10, 1998.XML 1.0 achieved the Working Group's goals of Internet usability, general-purpose usability, SGML compatibility, facilitation of easy development of processing software, minimization of optional features, legibility, formality, conciseness, and ease of authoring.Clarifications and minor changes were accumulated in published errata and then incorporated into a Second Edition of the XML 1.0 Recommendation on October 6, 2000. Subsequent errata was incoroporated into a Third Edition on February 4, 2004.Also published on the same day as XML 1.0 Third Edition was XML 1.1, a variant of XML that encourages more consistency in how characters are represented and relaxes restrictions on names, allowable characters, and end-of-line representations.Both XML 1.0 Third Edition and XML 1.1 are considered current versions of XML.
Features of XML - XML provides a text-based means to describe and apply a tree-based structure to information. At its base level, all information manifests as text, interspersed with markup that indicates the information's separation into a hierarchy of ''character data'', container-like ''elements'', and ''attributes'' of those elements. In this respect, it is similar to the LISP programming language's S-expressions, which describe tree structures wherein each node may have its own property list.The fundamental unit in XML is the ''character (computing)character'', as defined by the Universal Character Set. Characters are combined in certain allowable combinations to form an XML ''document''. The document consists of one or more ''entities'', each of which is typically some portion of the document's characters, codeencoded as a series of bits and stored in a text file.The ubiquity of text file authoring software (word processors) facilitates rapid XML document authoring and maintenance, whereas prior to the advent of XML, there were very few data description languages that were general-purpose, Internet protocol-friendly, and very easy to learn and author. In fact, most data interchange formats were proprietary, special-purpose, "binary" formats (based foremost on bit sequences rather than characters) that could not be easily shared by different software applications or across different computing platforms, much less authored and maintained in common text editors.By leaving the names, allowable hierarchy, and meanings of the elements and attributes open and definable by a customizable ''XML schemaschema'', XML provides a syntactic foundation for the creation of custom, XML-based markup languages. The general syntax of such languages is rigid — documents must adhere to the general rules of XML, assuring that all XML-aware software can at least read (''parse'') and understand the relative arrangement of information within them. The schema merely supplements the syntax rules with a set of constraints. Schemas typically restrict element and attribute names and their allowable containment hierarchies, such as only allowing an element named 'birthday' to contain 1 element named 'month' and 1 element named 'day', each of which has to contain only character data. The constraints in a schema may also include data type assignments that affect how information is processed; for example, the 'month' element's character data may be defined as being a month according to a particular schema language's conventions, perhaps meaning that it must not only be formatted a certain way, but also must not be processed as if it were some other type of data.In this way, XML contrasts with HTML, which has an inflexible, single-purpose vocabulary of elements and attributes that, in general, cannot be repurposed. With XML, it is much easier to write software that accesses the document's information, since the data structures are expressed in a formal, relatively simple way.XML makes no prohibitions on how it is used. Although XML is fundamentally text-based, software quickly emerged to abstraction (computer science)abstract it into other, richer formats, largely through the use of datatype-oriented schemas and object-oriented programming paradigms (in which the document is manipulated as an object). Such software might only treat XML as serialized text when it needs to transmit data over a network, and some software doesn't even do that much. Such uses have led to "binary XML", the relaxed restrictions of XML 1.1, and other proposals that run counter to XML's original spirit and thus garner an amount of criticism.
Strengths and weaknesses - Some features of XML that make it well-suited for data transfer are:
its simultaneously human-readablehuman- and machine-readable format;
it has support for Unicode, allowing almost any information in any human language to be communicated;
the ability to represent the most general computer science data structures: record (computer science)records, lists and tree data structuretrees;
the self-documenting format that describes structure and field names as well as specific values;
the strict syntax and parsing requirements that allow the necessary parserparsing algorithms to remain simple, efficient, and consistent.XML is also heavily used as a format for document storage and processing, both online and offline, and offers several benefits:
its robust, logically-verifiable format is based on international standards;
the hierarchyhierarchical structure is suitable for most (but not all) types of documents;
it manifests as plain text files, unencumbered by licenses or restrictions;
it is platform-independent, thus relatively immune to changes in technology;
it and its predecessor, SGML, have been in use since 1986, so there is extensive experience and software available.For certain applications, XML also has the following weaknesses:
Its syntax is fairly verbose and partially redundant. This can hurt human readability and application efficiency, and yields higher storage costs. It can also make XML difficult to apply in cases where bandwidth is limited, though compression can reduce the problem in some cases. This is particularly true for multimedia applications running on cell phones and PDAs which want to use XML to describe images and video.
Parsers should be designed to recursively handle arbitrarily nested data structures and must perform additional checks to detect improperly formatted or differently ordered syntax or data (this is because the markup is descriptive and partially redundant, as noted above). This causes a significant overhead for most basic uses of XML, particularly where resources may be scarce - for example in embedded systemembedded systems. Furthermore, additional security considerations arise when XML input is fed from untrustworthy sources, and resource exhaustion or stack overflows are possible.
Some consider the syntax to contain a number of obscure, unnecessary features born of its legacy of SGML compatibility. However, an effort to settle on a subset called "Minimal XML" led to the discovery that there was no consensus on ''which'' features were in fact obscure or unnecessary.
The basic parsing requirements do not support a very wide array of data types, so interpretation sometimes involves additional work in order to process the desired data from a document. For example, there is no provision in XML for mandating that "3.14159" is a floating-point number rather than a seven-character string. XML schemaXML schema languages add this functionality.
Modelling overlapping (non-hierarchical) data structures requires extra effort.
Mapping XML to the relational or object oriented paradigms is often cumbersome.
Some have argued that XML can be used as a data storage only if the file is of low volume, but this is only true given particular assumptions about architecture, data, implementation, and other issues.
Quick syntax tour - Here is an example of a simple recipe expressed using XML: Basic breadFlour ? Yeas t? Warm WaterS alt? Mix all ingredients together, and knead thoroughly.Cover with a cloth, and leave for one hour in warm room.Knead again, place in a tin, and then bake in the oven. The first line is the XML declaration: it is an optional line stating what version of XML is in use (normally version 1.0), and may also contain information about character encoding and external dependencies.The remainder of this document consists of nested ''element''s, some of which have ''attribute''s and ''content''. An element typically consists of two tags, a ''start tag'' and an ''end tag'', possibly surrounding text and other elements. The start tag consists of a name surrounded by angle brackets, like !"";? the end tag consists of the same name surrounded by angle brackets, but with a forward slash preceding the name, like !"".? The element's content is everything that appears between the start tag and the end tag, including text and other (child) elements. The following is a complete XML element, with start tag, text content, and end tag: Knead again, place in a tin, and then bake in the oven.In addition to content, an element can contain attributes — name-value pairs included in the start tag after the element name. Attribute values must always be quoted, using single or double quotes, and each attribute name should appear only once in any element. Flour In? this example, the ''ingredient'' element has two attributes: ''amount'', having value "3", and ''units,'' having value "cups". In both cases, at the markup level, the names and values of the attributes, just like the names and content of the elements, are just textual data — the "3" and "cups" are not a quantity and unit of measure, respectively, but rather are just character sequences that the document author may be using to ''represent'' those things.In addition to text, elements may contain other elements: Mix all ingredients together, and knead thoroughly.Cover with a cloth, and leave for one hour in warm room.Knead again, place in a tin, and then bake in the oven.In this case, the ''Instructions'' element contains three ''step'' elements. XML requires that elements be properly nested — elements may never overlap. For example, this is not well-formed XML, because the ''em'' and ''strong'' elements overlap:
Normal emphasized strong emphasized !strongroot element (alternatively called a ''document element''), so the following would also be a malformed XML document: Thing oneThing twoXML provides special syntax for representing an element with empty content. Instead of writing a start tag followed immediately by an end tag, a document may contain the empty element tag where a slash ''follows'' the element name. The following two examples are functionally equivalent: XML provides two methods for escaping (or simply representing) special characters: ''entity references'' and ''numeric character references''. An entity in XML is a named body of data, usually representing text, such as an unusual character. An entity reference is a placeholder for that entity, and consists of the entity's name preceded by an ampersand !("&")? and followed by a semicolon !(";<< /code>")? for the left angle bracket (<) and "amp" (referenced as !"&< ;/code>")? for the ampersand (&) itself, and it is possible to declare additional ones if desired. Aside from representing individual characters, reproducing chunks of boilerplate text is another common use for entities. Here is an example using a predeclared XML entity to escape the ampersand in the name "AT&T": !AT& ;TThe? full list of predeclared entities are
& (&)
< (<)
> (>)
' (')
" (") If more entities need to be declared, this is done in the document's ''XML#DTDDTD'', which is not demonstrated in this example, for brevity.Numeric character references look like entities, but instead of a name, they contain the "number sign#" character followed by a number between the ampersand and the semicolon. The number (in decimal or hexadecimal) represents a Unicode code point, and is typically used to represent characters that are not easily encodable, such as an Arabic character in a document produced on a European computer. The ampersand in the "AT&T" example could also be escaped like this (decimal 38 is the Unicode value for "&"): !AT 8;TThere? are many more rules necessary to be sure of writing well-formed XML documents, such as the exact characters allowed in an XML name, but this quick tour provides the basics necessary to read and understand many XML documents.
Correctness in an XML document - For an XML document to be correct, it must be:
Well-formed. A well-formed document conforms to all of XML's syntax rules. For example, if a non-empty element has an opening tag with no closing tag, it is not ''well-formed''. A document that is not well-formed is not considered to be XML; a parser is required to refuse to process it.
Valid. A valid document has data that conforms to a particular set of user-defined content rules that describe correct data values and locations. For example, if an element in a document is required to contain text that can be interpreted as being an integer numeric value, and it instead has the text "hello", is empty, or has other elements in its content, then the document is not ''valid''.
Well-formed documents - An XML document is text, which is a sequence of characters. The specification requires support for Unicode encodings UTF-8 and UTF-16 (UTF-32 is not mandatory). The use of other non-Unicode based encodings, such as ISO-8859, is admitted and is indeed widely used and supported.A well-formed document must conform to the following rules, among others:
One and only one root element exists for the document. However, the XML declaration, processing instructions, and comments can precede the root element.
Non-empty elements are delimited by both a start-tag and an end-tag.
Empty elements may be marked with an empty-element (self-closing) tag, such as !& lt;/code>.? This is equal to !&l t;/IAmEmpty>.< li> All attribute values are quoted, either single (') or double (") quotes. Single quotes close a single quote and double quotes close a double quote.
Tags may be nested but may not overlap. Each non-root element must be completely contained in another element.
The document complies to its character set definition. The charset is usually defined in the xml declaration but it can be provided by the transport protocol, such as HTTP. If no charset is defined, usage of a Unicode encoding is assumed, defined by the Unicode Byte Order Mark. If the mark does not exist, UTF-8 is the default.Element names are case-sensitive. For example, the following is a well-formed matching !pair:& lt;/code>? ... !whereas? this is !not:&l t;/code>? ... !The? careful choice of names for XML elements will convey the meaning of the data in the markup (computing)markup. This increases human readability while retaining the rigor needed for software parsing.Choosing meaningful names implies the semantics of elements and attributes to a human reader without reference to external documentation. However, this can lead to verbosity, which complicates authoring and increases file size.
Valid documents - An XML document that complies with a particular schema, in addition to being well-formed, is said to be valid.An XML schema is a description of a type of XML document, typically expressed in terms of constraints on the structure and content of documents of that type, above and beyond the basic constraints imposed by XML itself. A number of standard and proprietary XML schema languages have emerged for the purpose of formally expressing such schemas, and some of these languages are XML-based, themselves.Before the advent of generalised data description languages such as SGML and XML, software designers had to define special file formats or small languages to share data between programs. This required writing detailed specifications and special-purpose parsers and writers.XML's regular structure and strict parsing rules allow software designers to leave parsing to standard tools, and since XML provides a general, data model-oriented framework for the development of application-specific languages, software designers need only concentrate on the development of rules for their data, at relatively high levels of abstraction.Well-tested tools exist to validate an XML document "against" a schema: the tool automatically verifies whether the document conforms to constraints expressed in the schema. Some of these validation tools are included in XML parsers, and some are packaged separately.Other usages of schemas exist: XML editors, for instance, can use schemas to support the editing process.
DTD - The oldest schema format for XML is the Document Type Definition (DTD), inherited from SGML. While DTD support is ubiquitous due to its inclusion in the XML 1.0 standard, it is seen as limited for the following reasons:
It has no support for newer features of XML, most importantly namespaces.
It lacks expressivity. Certain formal aspects of an XML document cannot be captured in a DTD.
It uses a custom non-XML syntax, inherited from SGML, to describe the schema.
XML Schema - A newer XML schema language, described by the W3C as the successor of DTDs, is XML Schema, or more informally referred to in terms of the acronym and initialisminitialism for XML Schema instances, XSD (XML Schema Definition). XSDs are far more powerful than DTDs in describing XML languages. They use a rich datatypedatatyping system, allow for more detailed constraints on an XML document's logical structure, and are required to be processed in a more robust validation framework. Additionally, XSDs use an XML based format, which makes it possible to use ordinary XML tools to help process them, although WXS (W3C XML Schema) implementations require much more than just the ability to read XML.Criticisms of WXS include the following:
The specification is very large, which makes it difficult to understand and implement.
The XML-based syntax leads to verbosity in schema description, which makes XSDs harder to read and write.
RELAX NG - Another popular schema language for XML is RELAX NG. Initially specified by OASIS_(organization)OASIS, RELAX NG is now also an ISO international standard (as part of DSDL). It has two formats: an XML based syntax and a non-XML compact syntax. The compact syntax aims to increase readability and writability, but since there is a well-defined way to translate compact syntax to the XML syntax and back again by means of !James_Clark_(XML_expert) James Clark's thaiopensource.com - Trang conversion tool, the advantage of using standard XML tools is not lost. Compared to XML Schema, RELAX NG has a simpler definition and validation framework, making it easier to use and implement. It also has the ability to use any datatype framework on a plug-in basis; for example, a RELAX NG schema author can require values in an XML document to conform to definitions in XML Schema Datatypes.
Other schema languages - Some schema languages not only describe the structure of a particular XML format but also offer limited facilities to influence processing of individual XML files that conform to this format. DTDs and XSDs both have this ability; they can for instance provide attribute defaults. RELAX NG intentionally does not provide these facilities.
International and worldwide use - XML fully supports unicode character encodings in element names, attributes and data. Therefore the following is a perfectly well-formed XML document, even though it includes both Chinese and Russian characters: Данные< /俄语>
Displaying XML on the web - Extensible Stylesheet Language (XSL) is a supporting technology that describes how to format or transform the data in an XML document. The document is changed to a format suitable for browser display. The process is similar to applying a Cascading Style SheetsCSS to an HTML document for rendering.Without using CSS or XSL, a generic XML document is rendered as raw XML text by most web browsers. Browsers like Internet Explorer, Mozilla and Mozilla Firefox display it with 'handles' that allow parts of the structure to be expanded or collapsed with mouse-clicks. In order to style the rendering in a browser with CSS, the XML document must include a special reference to the !stylesheet::See? the CSS article Cascading Style !Sheets#Example_of_applying_CSS _to_.27plain.27_XMLfor an example of this in action.This is different from specifying a stylesheet in HTML, which uses the !? element.To specify a client-side XSL TransformationsXSL Transformation (XSLT), the following processing instruction is required in the !XML::Client-side? XSLT is not yet supported in Opera (web browser)Opera.The alternative is conversion of XML into HTML, PDF and other formats ''on the server''. Many Extensible Stylesheet Languagesuch processors exist, and the end-user then need not be aware of what has been going on 'behind the scenes'.See the XSLT article !XSL_Transformations#Examplefor an example of server-side XSLT in action.
XML extensions -
XPath It is possible to refer to individual components of an XML document using XPath. This allows stylesheets in (for example) Extensible Stylesheet LanguageXSL and XSLT to dynamically "cherry-pick" pieces of a document in any sequence needed in order to compose the required output.
XQuery is to XML what SQL programming languageSQL is to relational databases.
XML namespaces enable the same document to contain XML elements and attributes taken from different vocabularies, without any naming collisions occurring.
XML Signature defines the syntax and processing rules for creating digital signatures on XML content.
XML Encryption defines the syntax and processing rules for encryptionencrypting XML content.
XPointer is a system for addressing components of XML based internet media.
Processing XML files - Simple API for XMLSAX and DOM (XML API)DOM are Application programming interfaceAPIs widely used to process XML data. SAX is used for serial processing whereas DOM is used for random-access processing. Another form of XML Processing API is data binding, where XML data is made available as a strongly typed programming language data structure, in contrast to the DOM. Example data binding systems are the Java Architecture for XML Binding (JAXB) java.sun.com and the Strathclyde Novel Architecture for Querying XML (SNAQue) cis.strath.ac.uk.A filter in the Extensible Stylesheet Language (XSL) family can transform an XML file for displaying or printing.
XSL-FO is a declarative, XML-based page layout language. An XSL-FO processor can be used to convert an XSL-FO document into another non-XML format, such as PDF.
XSLT is a declarative, XML-based document transformation language. An XSLT processor can use an XSLT ''stylesheet'' as a guide for the conversion of the data tree represented by one XML document into another tree that can then be serialized as XML, HTML, plain text, or any other format supported by the processor.
XQuery is a W3C language for querying, constructing and transforming XML data.
XPath is a path expression language for selecting data within an XML file. XPath is a sublanguage of both XQuery and XSLT.The native file format of OpenOffice.org and AbiWord is XML. Some parts of Microsoft Office 11 will also be able to edit XML files with a user-supplied schema (but not a DTD), and on June 2, 2005 Microsoft announced that, by late 2006 all the files created by users of its Office suite of software will be formatted with web-centered XML specifications. There are dozens of other XML editors available.
Versions of XML - There are two current versions of XML. The first, ''XML 1.0'', was initially defined in 1998. It has undergone minor revisions since then, without being given a new version number, and is currently in its third edition, as published on February 4, 2004. It is widely implemented and still recommended for general use. The second, ''XML 1.1'', was initially published on the same day as XML 1.0 Third Edition. It contains features — some contentious — that are intended to make XML easier to use for certain classes of users (mainframe programmers, mainly). XML 1.1 is not very widely implemented and is recommended for use only by those who need its unique features.XML 1.0 and XML 1.1 differ in the requirements of characters used for element names, attribute names etc.: XML 1.0 only allows characters which are defined in Unicode 2.0, which includes most world scripts, but excludes scripts which only entered in a later Unicode version, such as Mongolian languageMongolian, Cambodian languageCambodian, Amharic, Burmese languageBurmese, etc..XML 1.1 only ''disallows'' certain control characters, which means that any other character can be used, even if it is notdefined in the current version of Unicode.It should be noted here that the restriction present in XML 1.0 only applies to element/attribute names: both XML 1.0 and XML 1.1 allow for the use of full Unicode in the content itself. Thus XML 1.1 is only needed if in addition to using a script added after Unicode 2.0 you also wish to write element and attribute names in that script.Other minor changes between XML 1.0 and XML 1.1 are that control characters are now allowed to be included but only when escaped, and two special Unicode line break characters are included, which must be treated as whitespace.XML 1.0 documents are well-formed XML 1.1 documents with one exception: XML documents that contain unescaped C0 and C1 control codes#C1 (ISO-8859 and unicode)C1 control characters are now malformed: this is because XML 1.1 requires the C1 control characters to be escaped with numeric character references.There are also discussions on an XML 2.0, although it remains to be seen if such will ever come about. XML-SW (SW for skunk works), written by one of the original developers of XML, contains some proposals for what an XML 2.0 might look like: elimination of DTDs from syntax, integration of namespaces, XML Base and XML Information Set (''infoset'') into the base standard.The World Wide Web Consortium also has a XML Binary Characterization Working Group doing preliminary research into use cases and properties for a binary encoding of the XML infoset. The working group is not chartered to produce any official standards. Since XML is by definition text-based, ITU-T and ISO are using the name ''asn1.elibel.tm.fr - Fast Infoset'' for their own binary infoset to avoid confusion (see ITU-T Rec. X.891 ISO/IEC 24824-1).
Patent status - In October 2005 the small company Scientigo publicly asserted that two of its patents, US patent5842213 and US patent6393426 , apply to the use of XML. The patents cover the transfer of "data in neutral forms", according to their applications, which were filed in 1997 and 1999. Scientigo CEO Doyal Bryant expressed a desire to "monetize" the patents but stated that the company was "not interested in having us against the world." He said that Scientigo was discussing the patents with several large corporations.news.com.comXML users and independent experts responded to Scientigo's claims with widespread skepticism and criticism. Some derided the company as a patent troll. Tim Bray described any claims that the patents covered XML as "ridiculous on the face of it"blogs.zdnet.com. Because there exists a large amount of prior art relating to XML, some legal experts believed it would be difficult for Scientigo to enforce its patents through litigation.Microsoft has also been accused of applying for patents that, if granted, could restrict the use of XML.news.com.com
See also -
XML schema languages: Document Type DefinitionDTD, XML Schema, RELAX NG, Document Schema Definition LanguagesDSDL
XML processing Application programming interfaceAPIs: DOM (XML API)DOM, Simple API for XMLSAX, E4X
Extensible Metadata Platform (XMP), used in graphics applications
Scalable Vector GraphicsSVG
ASN.1
WBXML
Serialization
List of general purpose markup languages
Comparison of general purpose markup languages
Comparison of layout engines (XML)
Single source publishing
Extensible Binary Meta Language
References -
Tim BrayBray, Tim (February 2005). "A conversation with Tim Bray: Searching for ways to tame the world’s vast stores of information." ''Association for Computing Machinery's Queue''. 3 (1). acmqueue.com - link
Changes Training Centre
Changes Training Centre (CTC) is a private post-secondary educational institution fully registered and accredited by the Private Career Training Institutions Association of British Columbia (PCTIA). Featuring Diploma programs in General Insurance, Accounting and Payroll, Management, Administration, and more. Certifications include PMCP, Real Estate, and CFP. Contact us at 604-852-1233, (toll free 1-877-852-1233) email info@changestraining.com or go to www.changestraining.com for more information. http://www.changestraining.com/
Music Notation
Information about music notation, musical notation formats, music fonts, audio to midi conversion, optical music recognition, music information retrieval and braille music http://www.music-notation.info/
Digital Time - New internet generation
Digital-Time is a leader in Macromedia Flash and Website design. Our services include web site development, design, multimedia, broadcast video, 3D, animation and corporate identity. We design and develop quality media solutions for a large spectrum of clients, and international partner, clients http://www.digitaltime.biz/
Landibase
Simple technology to develop www/internet/LAN oriented database applications using Java and C/C++, for Linux,Solaris,Windows. http://www.landibase.com/
Fanore Software
Specialising in agile programming, Fanore Software develop web and mobile solutions and have over 70 clients in the public and private sector. Servicing clients in the USA, UK and Ireland, we carry out research and development as well as proto-type development through to finished database powered applications. http://www.fanore.com/
L'internet Selon Ben
Annuaire de sites Internet pertinents, organisés par thèmes. Vous y trouverez des istes à connotation informatique (internet, programmation, réseau,...) ou non (immobilier, mp3, voyages, ...). http://www.touchon.net/
RMSource, Inc.
RMSource, Inc., is an information technology consulting firm that provides a complete range of strategic outsourcing services. We invite you to browse our web site, and contact us at 877.319.3051. http://www.rmsource.com/
Cut Optimization WoodWorks
Program to optimize rectangular cuts uf wood, glass, steel or plastic. Crosscutting (horizontal and/or vertical), edge-bandings, usage of oddments, printout of cutting-map and labels, XML/Excel Import, offer-printout http://woodworks.at/
OTIL: Observatoire du traitement informatique des langues et de l'inforoute
L'OTIL répertorie pour le compte de l'Organisation Internationale de la Francophonie les intervenants scientifiques, industriels et institutionnels, les projets, produits, services et ressources en ingénierie linguistique. Pays concernés: Afrique de l'Ouest (Bénin, Burkina Faso, Guinée, Mali, Mauritanie, Niger, Sénégal), Canada, Communauté Wallonie-Bruxelles (Belgique), France, Haïti, Madagascar, Maroc, Québec, République Centrafricaine, République Démocratique du Congo, Roumanie, Suisse. http://www.otil.org
Marco Skulschus - Book author and IT-consultant
Marco Skulschus works as a consultant for Comelio GmbH in Germany. His main fields of activity are databased analysis and reporting systems with C#.NET, Java and PHP. In his free-time he publishes books on subjects like XML and databases. http://www.marco-skulschus.de/
Digit Solutions
Digit Solutions is a software development, web design and web maintenance company based in Cape Town, South Africa. Digit Solutions specialises in the integration of varying technology, especially sports based. http://digitsolutions.co.za/
Tangra, Inc. - The art of software design and development
Tangra, Inc. is a software design and development firm specializing in design, architecture, development, and implementation of custom Web and Windows applications, database design, database migration/integration, database performance tuning and enhancement, Web and graphic design, and custom software solutions. http://www.tangrainc.com/
Roman Liturgy
You will find here all kind of information useful for preparing ceremonies of the Roman rite of the Catholic Church. This site is primarely dedicated to the Roman Rite currently in use since 1975. http://www.romanliturgy.org/
EC Wise, Inc.
A professional services technology company specializing in data integration, architecture and development http://www.ecwise.com/
Technology News and Literature
Technology News and Literature provides quality news reporting on the intersection of information technology, business, and public policy. The company, founded by Alan Kotok in April 2001, is based in Arlington, Virginia (just outside Washington, DC), at the hub of government and one of America's technology centers. TNL reports on actual events and happenings, filtering out the hype, fluff, rumor, and speculation. http://www.technewslit.com/
DeTeDe
DeTeDe is a leading company in document managing, web services , SGML and XML solutions. DeTeDe: Content Management & XML Integration http://www.detede.com/
X.Systems, Inc.
A small firm in VA with nearly 15 years experience in bringing automation to text content. From strategy to planning to development and implementation, we have supported a who's who of business and government since 1992. http://www.xsystems.com/
Ariamedia
Ariamedia is a strategic E-Business solutions provider located in Dallas, Texas. Through a multi-disciplinary approach, we create complex solutions leveraging powerful creative design, application development, and our suite of Conductor E-Business Products. http://www.ariamedia.com
XML Development
XML Development is a full-service web application development firm dedicated to delivering the highest standards of quality, technology and client satisfaction. http://www.xml-development.com/
The 4xtra Alliance
We are an agile developer offering project management, system design & development, support & training. We design & build systems & host websites for all business needs: groupware; content management; ERP; dealing-room & financial software; etc. http://www.4xtra.com/
Livescore provider
Livescore, live score, The highest odds tax free online bookmaker & the fastest real-time livescore provider. Highest sportsbook in online sports betting and offshore sports bets. Provide free live score and highest odds feeds for webmasters. Livescores feeds and highest odds feeds for your site in wap, rss, xml, txt, js, html, sms, wml, email2sms, emailTosms format. http://www.exactscores.com/
XML.com
XML.com, where the XML community shares XML development resources and solutions, features timely news, opinions, features, and tutorials; the Annotated XML specification created by Tim Bray; authoring tools, XML resources, interactive forums, and newsletters. Published by O'Reilly. http://www.xml.com/
World Wide Web Consortium
International industry consortium founded in 1994 whose purpose is to develop specifications, guidelines, software, and tools to promote the Internet's evolution and ensure its interoperability. http://www.w3.org/