2003
DOI: 10.1007/3-540-36556-7_7
|View full text |Cite
|
Sign up to set email alerts
|

Adaptive XML Shredding: Architecture, Implementation, and Challenges

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2004
2004
2013
2013

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 11 publications
0
2
0
Order By: Relevance
“…When a user requests to materialize a view, VIREX maps the XML document and stores its content in the relational database. This process is referred to as shredding [20,18,44] and involves the steps outlined next in Algorithm 1 shown in Fig. 5.…”
Section: Materializing Xml Views As Relational Datamentioning
confidence: 99%
“…When a user requests to materialize a view, VIREX maps the XML document and stores its content in the relational database. This process is referred to as shredding [20,18,44] and involves the steps outlined next in Algorithm 1 shown in Fig. 5.…”
Section: Materializing Xml Views As Relational Datamentioning
confidence: 99%
“…For instance, if an application employing a relational database wants to publish [12,16] (scenario 1) some of its data to make it available to an application using a semi-structured database (based on XML), the data should be first extracted with a relational query, such as a SQL query. In the other direction, if the application using a semi-structured database wants to shred [20] (scenario 2) some of its data to enrich a relational database, the data should be first extracted with a query over XML, for example with XPath or XQuery. The same query languages can be used to extract semi-structured data before shredding it into a graph database, based on RDF (scenario 3).…”
Section: Introductionmentioning
confidence: 99%