| THOMPSON,H.S., BEECH,D.,MALONEY, M., AND MENDELSOHN,N. 2001. XML schema part 1:structures. |
....exchanging information on the Web XML [6] is mostly concerned about syntax. However, syntax does not make sense without semantics, and many recent activities aim at adding more semantic capabilities to XML. Most notably, the XML Infoset [10] offers an abstract information model for XML; XML Schema [29] allows users to describe XML vocabularies, structures, and relationships; and XQuery [8] allows users to ask questions, manipulate, or reason about XML documents. As the W3C standard model for describing the semantics and reasoning about information on the Web RDF [18] RDF is mostly concerned ....
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML schema part 1: Structures. W3C Recommentation, May 2001. http://www.w3.org/TR/xmlschema-1/. 20
....use of XML in electronic data interchange, there is a similar need for the specification of keys to help in location data in an XML document and in enforcing semantic integrity constraints. Recently, key specifications have been proposed for the XML standard [11] XML Data [23] and XML Schema [39]. As discussed in more detail in [15] these proposals are both not sufficiently powerful in some areas and too powerful in other areas. They are not sufficiently powerful because they can neither express keys having a complex structure nor express scoped keys (called relative keys in [15, 13] ....
....proposals are both not sufficiently powerful in some areas and too powerful in other areas. They are not sufficiently powerful because they can neither express keys having a complex structure nor express scoped keys (called relative keys in [15, 13] They are too powerful because the proposal in [39] is based on the powerful language Xpath [19] and this allows key constraints to be specified which are not satisfiable. Also, it is desirable to be able to solve the implication problem for keys, i.e. deciding whether a set of key constraints logically implies another key constraint, since being ....
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. Xml schema part 1:structures. W3C Working Draft, http://www.w3.org/Tr/1998.
....required by a templating layer; 3. focus on an imperative programming model; and 4. utilize an XML data model pervasively to integrate seamlessly with Internet and Web standards. An ETL template must be well formed XML that is valid with respect to the language s XML Schema Definitions [38, 6]. By enforcing those requirements, we catch a large class of syntactic and A fifth design goal was to enable automatic translation of our legacy language into ETL. This paper focuses only on the essential language, and Section 3 mentions our migration to ETL a bit more. Figure 3: This ....
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML schema part 1: Structures. W3C Working Draft, November 1999. http://www.w3.org/TR/xmlschema-1.
....discussion can only cover the most basic concepts needed in the scope of this thesis. Many details had to be omitted for space reasons; the reader is referred to the official W3C Web site for more information, new developments and the full specification documents of the technologies presented here [3, 24, 31, 39, 143]. 2.5.1 THE EXTENSIBLE MARKUP LANGUAGE XML XML is a means to define new markup languages. Such a markup language structures documents into several sections. The sections of a document are called elements and contain text content and further nested document sections (elements) The hierarchy of ....
....logic) only require two contract concerns (structure and interface) The following subsections discuss both of these contract concerns in detail. 5.3.1 THE STRUCTURE CONTRACT CONCERN The structure contract concern is the heart of an XContract. It relies on the W3C XML Schema recommendation [24, 143] and defines both the structural and the datatype constraints. Depending on the type of the concern (inline vs. external) the schema document is either directly embedded in or only referenced by the structural concern. We do not present more information about the XML Schema recommendation here ....
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema Part 1: Structures. Technical report, World Wide Web Consortium, May 2001.
....In contrast, XML [7] is a core building block upon which other related technologies are being developed. This toolkit concept allows for more efficient development processes of according applications. For example, existing XML parsers can be used to develop XSLT [8] processors and XML Schema [9, 10, 11] based validators, since XSL and XML Schema themselves are XML compliant. XML Schemas can be defined and used by validating XML parsers to ensure XML data integrity. Specific XML compilers can be built as XSL stylesheets using any already existing XSLT processor. These advantages of existing ....
....XSL [8] is a quite powerful stylesheet language. e.g. it can be used to filter XML data, to correlate data from several documents, to generate statistics, or to create concise HTML pages or reports in other text based formats. The structure of management data can be expressed as XML Schemas [9, 10, 11]. This would allow, e.g. to ensure the integrity of configuration data documents through the use of a usual XML parser that checks whether the document is well formed and valid according to the XML Schema definition. High level management operations can be defined through WSDL and called via ....
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation, University of Edinburgh, Oracle, Lotus, May 2001.
....XW elements and attributes are de ned in namespace http: www.cs.uku.fi XW 2001. We normally use the pre x xw to denote this namespace. The way the result is described in XW through a template resembles that of XSLT. Element creation through xw:ELEMENT was borrowed from XSLT and XML Schema [18]. The types of elds supported in XW for binary input, expression of alternative parts through xw:CHOICE and occurrence indicators xw:minoccurs and xw:maxoccurs were also inspired by XML Schema. An XW wrapper has the root element xw:wrapper that encloses the actual wrapper description. The type ....
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn, editors. XML Schema Part 1: Structures. W3C Recommendation, May 2001.
....algorithm was not known a priori. A number of different algorithms were quickly implemented for comparison. Also, this enabled straightforward experimentation with mixing different differentiation modes, which has produced more efficient derivative code in some cases. We have selected XML [16, 17] for the abstract intermediate representation in part to remedy this problem. XML offers the following benefits in the context of AD tool development: Standard interface. XML is a W3C endorsed standard for document markup that is flexible enough to provide the infrastructure for component ....
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn, (eds.). Xml schema part 1: Structures. W3C, 5 2001.
....automatically build up by just assembling those of elementary constructors. The actual system contains the description of more than 40 constructors and 25 logics. DLML has been built around DTD because there was not much support for other schema languages in XML parsers. The XML Schema language [11] would ease the implementation of DLML by replacing the use of the RDESC macro for a class hierarchy (all the operators being defined in function of abstract classes concept and role whose possible instanciation would be determined by the current logic) 24 3 Transformations What can such a DTD ....
Henry Thompson, David Beech, Murray Maloney, and Noah Mendelsohn (eds.). XML Schema part 1: structures. Recommendation, W3C, 2001. http://www.w3.org/TR/xmlschema-1/. 29
....since the whole standard is too extensive. Besides MPEG 7 usage in the VEL allows qualitative access to the content of multimedia data by searching, filtering and applying information retrieval techniques as in [GD00] or [SS01] Declarations and definitions may have and be identified by names [TB01]. Several kinds of component have a target namespace, which is either absent or a namespace name, also as defined by XML namespaces [BB02] It serves to identify the namespace within which the association between the component and its name exists. In the case of declarations, this in turn ....
Thompson, H. S., Beech, D., Maloney, M., Mendelsohn, N.: XML Schema Part 1: Structures. W3C, http://www. w3. org/TR/xmlschema-1/ (2001).
....and exchanging data on the web has confirmed the central role of semistructured data. At the same time, XML has also redefined some of the ground rules. Perhaps the most important is that XML marks the return of the schema , in the form of Data Type Definition (DTD) and recently, XML Schema [19], both of which are used to constrain valid XML documents. Many information providers have published their databases on the web as semistructured data, and others are developing repositories for new applications. This makes it important to have a guide for designing good semistructured ....
H. S. Thompson, D. Beech, M. Maloney and N. Mendelsohn. XML Schema Part 1: Structures. Oct. 2000 http://www.w3.org/TR/xmlschema-1/.
....ned, since the whole standard is too extensive. Besides MPEG 7 usage in the VEL allows qualitative access to the content of multimedia data by searching, ltering and applying information retrieval techniques as in [GD00] or [SS01] Declarations and de nitions may have and be identi ed by names [TB01]. Several kinds of component have a target namespace, which is either absent or a namespace name, also as de ned by XML namespaces [BB02] It serves to identify the namespace within which the association between the component and its name exists. In the case of declarations, this in turn ....
Thompson, H. S., Beech, D., Maloney, M., Mendelsohn, N.: XML Schema Part 1: Structures. W3C, http://www.w3.org/TR/xmlschema-1/ (2001).
No context found.
THOMPSON,H.S., BEECH,D.,MALONEY, M., AND MENDELSOHN,N. 2001. XML schema part 1:structures.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. Xml schema part 1:structures. W3C Working Draft, http://www.w3.org/Tr/1998.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. M. (Editors). XML Schema Part 1: Structures. World Wide Web Consortium, May 2 2001. http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/.
No context found.
Thompson, H.S., Beech, D., Maloney, M., Mendelsohn, N.: Xml schema part 1: Structures. (W3C Recommendation 02 May 2001)
No context found.
Thompson, H. S., Beech, D., Maloney, M., and Mendelsohn, N., XML Schema Part 1: Structures, W3C Recommendation, www.w3.org/TR/xmlschema-1,May 2, 2001.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema part 1: Structures, May 2001. W3C Recommendation. http://www.w3.org/TR/xmlschema-1/.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation, May 2001. http://www.w3.org/TR/xmlschema-1.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML schema part 1: Structures. W3C Recommendation, May 2001.
No context found.
et al. H. S. Thompson. XML Schema Part 1: Structures. http://www.w3.org/TR/2000/CR-xmlschema-120001024 /.
No context found.
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. W3C Working Draft, February 2000.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. Technical report, W3C, 2001. http://www.w3.org/TR/xmlschema-1/.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, Noah Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation 2 May 2001.
No context found.
Henry S. Thompson, David Beech, Murray Maloney and Noah Mendelsohn, XML Schema Part 1: Structures, World Wide Web Consortium, 2001, available at http://www.w3.org/TR/xmlschema-1/ .
No context found.
Henry S. Thompson, David Beech, Murray Maloney and Noah Mendelsohn, XML Schema Part 1: Structures, World Wide Web Consortium, 2001. Available at http://www.w3.org/TR/xmlschema-1/.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. Technical report, W3C, 2001. http://www.w3.org/TR/xmlschema-1/.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation, May 2001.
No context found.
H.S.Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. 2001.
No context found.
Thompson, H.S., Beech, D., Maloney, M., Mendelsohn, N.: XML Schema Part 1: Structures. Technical report, World Wide Web Consortium (2002) W3C Recommendation.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema part 1: Structures, May 2001. W3C Recommendation. http://www.w3.org/TR/xmlschema-1/.
No context found.
H. S. Thompson, D. Beech, M. Maloney, N. M. et al., XML Schema Part 1: Structures, W3C Recommendation (2001).
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation, May 2001. http://www.w3.org/TR/xmlschema-1.
No context found.
Henri S. Thompson, David Beech, Murray Maloney, and N. Mendelsohn. XML Schema part 1: Structures. In W3C Recommendation, 2001.
No context found.
Thompson, H. S., D. Beech, M. Maloney and N. Mendelsohn, Xml schema part 1: Structures (2001.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, Noah Mendelsoh:. XML Schema Part 1: Structures. W3C Recommendation 2 May 2001, http://www.w3.org/TR/xmlschema-1/ 64
No context found.
Henri S. Thompson, David Beech, Murray Maloney, and N. Mendelsohn. XML schema part 1: Structures. W3C Recommendation, May 2001.
No context found.
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML schema part 1: Structures. W3C Recommentation, May 2001. http://www.w3.org/TR/xmlschema-1/.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema Part 1: Structures. World Wide Web Consortium, Recommendation RECxmlschema-1-
No context found.
H. Thompson, D. Beech, M. Maloney, N. Mendelsohn, Xml schema part 1: Structures, Recommendation, W3C, http://www.w3.org/TR/xmlschema-1/ (May 2001).
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn, editors. XML Schema Part 1: Structures. W3C Recommendation, World Wide Web Consortium, May 2001. Available online at http://www.w3.org/TR/2001/RECxmlschema -1-20010502/.
No context found.
H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn (Eds). Xml schema part 1: Structures. w3c recommendation, may 2001.
No context found.
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation 2 May 2001.
No context found.
H. S. THOMPSON, D. BEECH, M. MALONEY, AND N. MENDELSOHN, XML Schema part 1: Structures, May 2001. W3C Recommendation. http://www.w3.org/TR/xmlschema-1/.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn, editors. XML Schema Part 1: Structures.W3C Recommendation. World Wide Web Consortium (W3C), May 2001. http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/.
No context found.
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn (eds.). XML Schema Part 1 Structures. http://www.w3.org/TR/xmlschema-1, May 2001.
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema Part 1: Structures. Technical report, W3C, 2001. Available from http://www.w3.org/TR/ xmlschema-1.
No context found.
H. S. Thompson, D. Beech, M. Maloney, N. M. et al., XML Schema Part 1: Structures, W3C Recommendation (2001).
No context found.
H.S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML schema part 1: Structures, 2000. http://www.w3.org/TR/2000/WD-xmlschema-1-20000225/. 114
No context found.
Henry S. Thompson, David Beech, Murray Maloney, and Noah Mendelsohn. XML Schema Part 1: Structures. W3C Recommendation, World Wide Web Consortium (W3C), May 2001. www.w3.org/TR/xmlschema-1/. 112
No context found.
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn. XML Schema Part 1: Structures. W3C Working Draft, February 2000.
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC