Tamino XQuery User Guide - Software AG Documentation

More documents

Recommendations

Info

Text Retrieval Wildcard Characters In contrast to the maskcard character, which matches exactly one character, the wildcard character matches zero or more characters in a word. By default, the wildcard character is an asterisk "*". Consider the following query: let $text := text{"one, two"} return tf:containsAdjacentText($text, 1, "one", "*", "*") This query returns false, since tf:containsAdjacentText expects two word tokens adjacent to "one". If you use the default tokenizer, i.e. the white space-separated tokenizer, then the wildcard character is always the asterisk "*" (Unicode value U+002A). Using the Japanese Tokenizer If you use the Japanese tokenizer, all of the following characters are recognized as wildcard characters: Unicode Name ASTERISK ARABIC FIVE POINTED STAR ASTERISK OPERATOR HEAVY ASTERISK SMALL ASTERISK FULL WIDTH ASTERISK Code Value U+002A U+066D U+2217 U+2731 U+FE61 U+FF0A Note: In contrast to the standard white space-separated tokenizer, this definition of wildcard characters is fixed and cannot be changed. The Japanese tokenizer does not support wildcard characters in the middle of a word, since there are no explicit delimiter characters. So " * " will be treated as " *" adj " ". The example queries below focus on the contents of the patient/submitted/diagnosis nodes to show the effect of performing search operations with or without wildcard characters on segmentation of Japanese words. 100 XQuery User Guide
Text Retrieval 1. Contents Translation Segmentation Word Tokens Translation problems with the heart heart (physical) has problem 2. Contents Translation Segmentation Word Tokens Translation heart attack heart paralysis 3. Contents Translation Segmentation Word Tokens Translation heart disease heart disease 4. Contents Translation Segmentation Word Tokens Translation cardiovascular disease heart angio (cardiovascular) disease The following example queries all use the same query skeleton: for $a in input()/patient/submitted/diagnosis where return $a XQuery User Guide 101
Page 1 and 2:
Tamino XQuery User Guide Version 9.
Page 3 and 4:
Table of Contents Preface .........
Page 5:
Preface This document describes how
Page 9 and 10:
1 Sample bib This doctype describes
Page 11 and 12:
2 Sample reviews This doctype descr
Page 13 and 14:
3 Query Examples ■ Using Construc
Page 15 and 16:
Query Examples This section contain
Page 17 and 18:
Query Examples Explanation Again, a
Page 19 and 20:
Query Examples Explanation Building
Page 21 and 22:
Query Examples Explanation A join i
Page 23 and 24:
Query Examples Deleting Nodes The f
Page 25:
Query Examples Explanation For the
Page 29 and 30:
4 The Nuts and Bolts of XQuery ■
Page 31 and 32:
The Nuts and Bolts of XQuery (1, 2,
Page 33 and 34:
The Nuts and Bolts of XQuery Path E
Page 35 and 36:
The Nuts and Bolts of XQuery NodeTe
Page 37:
The Nuts and Bolts of XQuery Since
Page 40 and 41:
FLWOR Expressions Currently, there
Page 42 and 43:
FLWOR Expressions The order by and
Page 44 and 45:
Performing Update Operations In Tam
Page 46 and 47:
Performing Update Operations Renami
Page 48 and 49:
Performing Update Operations Schema
Page 50 and 51:
Performing Update Operations Note:
Page 52 and 53:
Performing Update Operations update
Page 55 and 56: 7 Calling XQuery through a Web Serv
Page 57 and 58: Calling XQuery through a Web Servic
Page 67 and 68: 8 CRUD Usage of a Tamino Doctype as
Page 69 and 70: CRUD Usage of a Tamino Doctype as a
Page 79: CRUD Usage of a Tamino Doctype as a
Page 82 and 83: Advanced Usage This chapter covers
Page 84 and 85: Advanced Usage declare function loc
Page 86 and 87: Advanced Usage declare namespace in
Page 88 and 89: Advanced Usage Defining a Custom Ou
Page 91 and 92: 10 Text Retrieval ■ Simple Text S
Page 93 and 94: Text Retrieval for $a in input()/pa
Page 95 and 96: Text Retrieval for $a in input()/re
Page 97 and 98: Text Retrieval Data on the Web 34.
Page 99 and 100: Text Retrieval In Tamino, you can u
Page 101 and 102: Text Retrieval ■ Location The att
Page 103 and 104: Text Retrieval perp whelp carnivore
Page 105: Text Retrieval In the context of pa
Page 109 and 110: Text Retrieval path separator is no
Page 111 and 112: III Related Information 105
Page 113 and 114: 11 Related Information ■ Internal
Page 115 and 116: Related Information ■ XQuery 1.0
Page 117 and 118: Index A atomization, 30 C character
show all

Tamino XQuery User Guide - Software AG Documentation

Create successful ePaper yourself

Delete template?

Save as template?