2002
DOI: 10.1016/s0950-5849(02)00011-3
|View full text |Cite
|
Sign up to set email alerts
|

An approach to high-level language bindings to XML

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2003
2003
2005
2005

Publication Types

Select...
2
2

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 17 publications
0
4
0
Order By: Relevance
“…The SNAQue tool [40] provides a variant of data binding that does not take schemas into account. From an XML document and a programming language type, it extracts a program value.…”
Section: Techniques For General-purpose Languagesmentioning
confidence: 99%
“…The SNAQue tool [40] provides a variant of data binding that does not take schemas into account. From an XML document and a programming language type, it extracts a program value.…”
Section: Techniques For General-purpose Languagesmentioning
confidence: 99%
“…Elsewhere, we have shown that we could correctly implement the SNAQue architecture, and we did it for a canonical language core L. 3 In doing so, we followed a principle of generality that allows binding mechanisms for other typed languages to be derived directly from L.…”
Section: Formal Definition and Canonical Specificationmentioning
confidence: 99%
“…In the canonical binding mechanism, for example, the binding would require the projection of the following canonical type over d: and result in the identification of the following canonical value equivalent to d′: Our algorithm Ext takes an XML document d and a canonical type T and returns a canonical value v, which is extractable from d according to T. In particular, we have proved the soundness and completeness of Ext with respect to the canonical specification. 3…”
Section: Formal Definition and Canonical Specificationmentioning
confidence: 99%
“…It provides a loose tree-based structure well suited for semi-structured data [2,3]. XML's self-describing nature, human readable element names, and ability to reference external document specifications allows applications to exchange and dynamically interpret data without a shared set of assumptions, such as interface definitions via header files.…”
Section: Introductionmentioning
confidence: 99%