OpenLLM-France/wikimedia huggingface dataset:
# XQuery/Loading data
## Motivation

You want to load your data into a native XML database (deserialization).

## Methods

There are several methods available. The one you use depends on the number of files you want to load and the loading rules.

### Use the web browser user interface

* ideal for a quick single file upload

### Use a IDE tool such as oXygen

* just right click on any collection and select "Import file" or "Import Folders"

### Use a WebDAV client

* ideal for bulk loads
* also allows you to move, copy and rename collections and files
* some IDE's like oXygen also have a WebDAV client built-in
Accessed through the http://localhost:8080/exist/webdav/db URL
List of WebDAV clients
* Built-in MAC WebDAV client
* Transmit for the MAC
* Windows WebDAV client
eXist WebDAV documentation http://www.exist-db.org/exist/apps/doc/webdav.xml

### Use the Java client

* the client has a tool to add files as well as to restore a backup

### Use an XQuery program

* Use the HTTP client GET to get a remote XML file and store it in the database
* Use the ft-client (FTP, SFTP etc.)

### Use an Apache Ant script

Many native XML databases have a set of Apache Ant scripts for doing things such as:
* bulk loading data
* creating collections
* setting permissions
* executing an XQuery
* running a backup
* restoring a backup file
These are usually the consistent and allow filtering of files as you load.
A sample ant "loader" is listed here: http://en.wikibooks.org/wiki/Apache_Ant/Store_XML_data
Note that some XQuery scripts that are loaded into the database collections may require post-installations steps to make them executable by some users.

## References

* eXist documentation page on uploading files: http://exist-db.org/exist/apps/doc/uploading-files.xml
# XQuery/Limiting Child Trees
## Motivation

You have a tree of data and you want to limit the results to a given level of a tree.

## Sample Data

Assume we have an org chart that has the following structure:
# XQuery/List OWL Classes
## Motivation

You want a simple XQuery program that will extract all the OWL classes from an OWL file that is coded using RDF.

## Method

We will start by just selecting all the classes in the file that have an name. In this example the names are stored in the rdf:ID attribute of the class like the following:
For our example we will use the wine ontology Used in the W3C OWL Guide:
Our XQuery will specifically get all the RDF tags with the "owl:Class" element in the file.
Here is a simple XQuery that returns all the Classes in the wine ontology. To you this script you can load it into a collection such as /db/apps/owl/views/classes.xq and the RDF data files can be loaded into /db/apps/owl/data
/db/apps/owl/views/classes.xq

## Sample Results

The results will be an HTML file with a ordered list:

## Other Tools

There are several other tools for working with OWL files that are very useful. One is to list all of the properties in an OWL file or list all the properties of a class. These reports can then be used to load the class or property into an XForms application for editing/versioning/workflow and approval.
# XQuery/Login and Logout
## Motivation

You want to log users into the system and log them out.

## Method

We will use the following functions to create login and logout forms:

### Logging In

To login we need to first create a new session and then use this session to store our login information:
This changes the effective user executing the current query and stores that user information into the HTTP session, so subsequent queries within the same session will also execute with the same user rights. Note that you must use "true" as the fourth argument to the login function.

### Logging Out

To log a user out use:
as well as session:clear will remove the user binding from the session, which means that the next call to the query will run as guest. However, the currently executing query will still use the old non-guest user until it completes.
In this example we have both call to xdb:login as guest and session:invalidate. We want to do both, clear the session for future queries as well as reset the current user for the rest of the query.

## Timeout setting

You can also change the default timeout setting by changing the Jetty configuration file here:
By default the configuration files sets the session timeout to 30 minutes:
Note:
In the future there may be xmldb:logout function which combines both steps. Another approach could be to handle the login/ logout within a controller.xql and thus separate it from the main query.
# Motivation

Sometimes you have many records or instances in a collection and you want to limit the amount of data returned by a query.

# Strategy
## Limiting Records in a Document

If you are limiting records in a large XML document you can do this by adding a predicate to the end of your for loop:

## Using Subsequence to Limit Results

The following query retrieves only the first 10 documents, in sequential document order, contained within a collection.
Where:
Note that the second argument is the item to start at and the third is the total number of items to return. It is NOT the last item to return.

## Sorting Before Limiting Results

Note that usually you will want to get the first N documents based on some sorting criteria, for example people that have a last name that start with the letter "A". So the first thing you must do is create a list of nodes that have the correct order and then get the first N records from that list. This can usually be done by creating a temporary sequence of sorted items as a separate FLWOR expression.

## Getting the Next N Rows

After you fetch the first N items from your sequence you frequently want to get the next N rows. To do this you will need to add buttons to your report for "Previous N Records" and "Next N Records". Those buttons will pass parameters to your XQuery telling where to start and how many records to fetch.
To do this you will need to call your own script with different parameters on the URL. To keep track of the URL you can use the get-url function that comes with eXist. For example:
If your query was run from http:/localhost:8080/exist/rest/db/apps/user-manager/views/list-people.xq this is the string that would be returned.
We will also get two parameters from the URL for the record to start at and the number of records to fetch:
Now we will create two HTML buttons that allow us to get next N records or the previous N records.
# Trainz/references/HKeys-WIN

Trainz/refs/Hotkeys,Windows This page is a redirect from a Wikibooks Trainz page which either has been moved, or renamed, or a colloquial term or abbreviation with coverage on the targeted page receiving redirected links.
# Trainz/formats

Back to the Top
* Fundamentals for Trainz Trainees
* TOC | Beginnings | Fun | AM&C | Creation | InBook Refs | ORP Refs:  • Index • Containers • Kinds • Tags | Appendixes  • Vers
Glossary :
HKeys-CM :
HKeys-DVR :
HKeys-SUR :
HKeys-WIN :
Mouse use :
Notations :
The follow articles describe the format of various user-editable files used within the Trainz environment.
When creating files for use with Trainz, care should be taken to follow the specified format accurately. Even if a particular deviation from the documented format is permitted by the current game and tools, it may become disallowed in future versions as loaders are updated and validation techniques are improved.

## Reading N3V File Formats

If you develop software which reads these file formats, you should accept and ignore minor deviations where feasible, in order to future-proof your software. Base your file reader on the documented format, not the particulars of the current Trainz implementation. It is likely that implementation-specific details will change between Trainz versions, whereas the file formats are typically extended but not often replaced.

## Writing Binary Files

There exist a number of binary file formats which are produced by N3V or by N3V-provided utilities and which are not formally documented. We strongly recommend that third-party developers do not write directly to these formats. N3V does not support any such tools or any files created by these tools. Reading from these undocumented binary formats is considered harmless but unsupported.

## Copy Protection

The use of an N3V binary file format should not be considered as a strong protection mechanism against snooping or modification except where specifically stated otherwise by N3V. Custom binary file formats are used to allow high-performance access to data from within the game environment. Security and obfuscation are neither primary not secondary goals for these formats, and N3V may provide mechanisms which convert from the binary formats back into "common" formats without prior notice. It should be noted that the technical capability of reverse-engineering the contents of a file does not equate to the legal right to modify or distribute said file. Before modifying someone else's content, please seek the permission of the creator. If you are in any doubt as to your rights in this area, please seek advice from a legal professional.
# Trainz/containers/volume container

Back to the Top
* Trainz Annotated References
* TOC | Beginnings | Fun | AM&C | Creation | InBook Refs | ORP Refs:  • Index • Containers • Kinds • Tags | Appendixes  • Vers
Glossary :
HKeys-CM :
HKeys-DVR :
HKeys-SUR :
HKeys-WIN :
Mouse use :
Notations :
The Volume container is a top-level config.txt file entry used by Enginespec and Steam Enginespec assets.

## Supported Tags

The Volume container supports the following tags. Each tag is show here with its default value.
| volume { | |
| scale | 1.0 |
| trainbrakepipe | 0.2 |
| epreservoirpipe | 0.2 |
| no3pipe | 0.2 |
| no4pipe | 0.2 |
| auxreservoir | 0.0384678 |
| autobrakecylinder | 0.00969387 |
| vacuumbrakepipe | 0.0 |
| vacuumbrakereservoir | 0.0 |
| vacuumbrakecylinder | 0.0 |
| mainreservoir | 1.0 |
| equaliser | 0.5 |
| independantbrakecylinder | 0.0103239 |

#### scale

    Type: Decimal
    Desc: multiplies volume by given value, generally leave this setting.

#### trainbrakepipe

    Type: Decimal
    Desc: brake pipe volume.

#### epreservoirpipe

    Type: Decimal
    Desc: For electro pneumatic braking - not currently in use, generally leave this setting.

#### no3pipe

    Type: Decimal
    Desc: Independent brake pipe.

#### no4pipe

    Type: Decimal
    Desc: Bail pipe - not currently in use, generally leave this setting.

#### auxreservoir

    Type: Decimal
    Desc: Auxiliary reservoir volume.

#### autobrakecylinder

    Type: Decimal
    Desc: Brake cylinder volume.

#### vacuumbrakepipe

    Type: Decimal
    Desc: For vacuum braking - not currently in use, generally leave this setting.

#### vacuumbrakereservoir

    Type: Decimal
    Desc: For vacuum braking - not currently in use, generally leave this setting.

#### vacuumbrakecylinder

    Type: Decimal
    Desc: For vacuum braking - not currently in use, generally leave this setting.

#### mainreservoir

    Type: Decimal
    Desc: Main reservoir volume.

#### equaliser

    Type: Decimal
    Desc: Equalising reservoir volume.

#### independantbrakecylinder

    Type: Decimal
    Desc: Loco brake cylinder volume.
# Trainz/references
## This page is a Soft redirection page

    (once the old page title)
... a 'Link Trap' for pages connecting to this page title which has been recently (2015-0817) moved.   Pardon us for the inconvenience of an additional click! ∅
Thanks,
The management
# Ukrainian

| III | This is a Category III Language. |
You are welcome to study one of the most beautiful languages in the world, descendant of language of ancient sacred Slavic texts, Principality of Rus, language of Cossacks - free people by the will of God known all over the world and of modern Ukrainian (Ukrainian Cossack) nation, state and society.
Please remember, the main secrets in quick learning of every language—freedom of mind and constant training, using and speaking it. If you want to learn our language - read, write, listen, make friends with us and soon you will become the real Cossack, free-minded man of the world—one of us. :) Don't worry to pronounce or say in your own way, to use mixed language—we, Ukrainians often also use it and we like to talk and make friends with people from all parts of our world despite their language skills, because we believe that all humanity is one big community of friends, or in our language—real Cossacks. :)
Such sites as Wikipedia in Ukrainian and Google Translate (one of the best translators in the modern world) will be a great help for you, especially during first time.

## Content
### Introduction

* Ukrainian/History

### Ukrainian language reference and parts of speech

* Alphabet and Pronunciation
* Grammar
* Words
* Simple Sentences
* Complex Sentences
* Common Phrases
* Parallel English-Ukrainian and Ukrainian-English Texts

### Ukrainian Culture

* Naming
* History
* Religion

### Authors & Contributors

* Authors & Contributors
# Uim/Usage

uim | Introduction | Installation | Setup | Usage | Configuration | Support | Manuals | Development License
    See the Setup page for instructions on setting the default conversion engine.
Uim follows accepted standards in keyboard command settings so if you have previously used and input method, uim should have a similar feel. To turn it on, just hit <shift><space> and, assuming that you've set up a default one, you can start typing in your favorite language.
The default keyboard commands can be also configured to fit your preferences.

## Entering text

When you turn the default input method on, you start writing into the . Some conversion engines will commit the text as you type (e.g. Hangul) while others will display it until you begin interactive conversion which is needed for languages such as Chinese and Japanese which have many homophones (different words that sound the same).
Interactive conversion is started by hitting the space bar. The conversion engine will break the preedit up into segments and display candidates for each one. You can choose between the candidates by running through the list using the <up> or <down> keys, or by entering the number displayed next to the candidate. The <left> and <right> keys allow you to go between segments.
Once you have chosen among the candidates for each segment, you can commit the preedit by hitting the <return> key (<Enter>).

## Keyboard commands

Pretty much everything regarding uim can be controlled using keyboard commands.

## Toolbars

    Please refer to the toolbar setup section for information on how to set up your toolbar.
The toolbar may display a number of buttons. These show the state of the input method and which modes the conversion engine supports. When uim is off, this will only be the uim logo.
When uim has been started, the button furthest to the left will be the conversion engine selector and it will display the presently active conversion engine. Press it get a list of available conversion engines.
Note: Installing the conversion engines isn't enough to make them available. You will have to choose the available ones in the preference tool.

## Conversion modes

Each conversion engine can run in various modes that can be changed on the fly. Below you will find an overview of these. Please see the conversion engine pages for documentation.
Simple conversion rules require only an on/off switch. Conversion engines serving more complex character sets and languages will probably offer further settings. Through these a user may, for example, choose the character set used for input, or a different keyboard layout.
The conversion modes are displayed and easily controlled through the toolbar.

## User dictionaries

There is a dictionary tool that can create user customized dictionaries (at least) for Anthy.
# Ukrainian/Glossary

Some examples of most common words in English transliteration:
| Ukrainian in Cyrillic | Latin Letters (pronunciation help) | English Equivalent |
| Так | Tak | yes |
| Ні | Ni | no |
Personal pronouns:
| Ukrainian in Cyrillic | Latin Letters (pronunciation help) | English Equivalent |
| Я | Ya | I |
| Ти | Ty | You (singular/personal - thee.) |
| Він | Vin | He |
| Вона | Vona | She |
| Воно | Vono | It |
| Ми | My | we |
| Ви | Vy | you (pl.) |
| Вони | Vony | they |
і - i - and; або - abo - or; але - ale - but; чи - chy - whether; щоби / аби - shchoby / aby - in order to.
Phrases
Дякую - Diakuyu - thanks
Будь ласка - Bud' laskah - please
Ласкаво просимо - Laskavo prosymo - welcome
Добрий день - Dobryj den' - Good day
Добрий ранок - Dobryj ranok - Good morning
Добрий вечір - Dobryj vechir - Good evening
Привіт - Pryvit - Hi, hello
До побачення - Do pobachennya - Goodbye (Less formal - buvaj/buvajteh (pl.))
Proposing to do something
Давай ...! - Davaj [verb] - Let's [verb] - E.g.: Давай вип'ємо (davaj vyp'jemo) - let's have a drink.
Agreeing
Давай <proposition phrase>? - Davaj! - OK
E.g.: Q: Davaj vyp'jem (ukr.)? - Do you care for a drink ? A: Davaj! - OK
Disagreeing
Не треба - Ne'ah treb'ah - (Let's) don't do it (I don't want/need it)
E.g.: Q: {Any dubious proposition or unwanted soliciting} A:Не треба (Ne'ah treb'ah)
Days
Понеділок - Ponedilok - Monday
Вівторок - Vivtorok - Tuesday
Середа - Sereda - Wednesday
Четвер - Chetver - Thursday
П'ятниця - P'yatnytsya - Friday
Субота - Subota - Saturday
Неділя - Nedilya - Sunday
Вчора - Vchora - Yesterday
Сьогодні - Syogodni - Today
Завтра - Zavtra - Tomorrow
Numbers
Один - odyn - 1
Два - dvah - 2
Три - tryh - 3
Чотири - chotyryh - 4
П'ять - p'yat - 5
Шість - shyst' - 6
Сім - sym - 7
Вісім - visym - 8
Дев'ять - dev'jat' - 9
Десять - des'jat' - 10
Одинадцять - odynadtsyat' - 11
Дванадцять - dvanadtsyat' - 12
Двадцять - dvadtsyat' - 20
Verbs:
Кохати, я кохаю - Kokhaty / Ya kokhayu - to love / I love
Сподіватися, я сподіваюся - Spodivatysya / Ya spodivayus' - to hope / I hope
Чекати, я чекаю - Chekaty / Ya chekayu - to wait / I wait
Йти, я йду - Yty (ity) / Ya ydu - to go / I go
Давати, я даю - Davaty / Ya dayu - to give / I give
Їсти, я їм - Yisty / Ya yim - to eat / I eat
Сидіти, я сиджу - Sydity / Ya sydzhu - to seat / I seat
Червоніти, я червонію - Chervonity / Ya chervoniyu - to get red, to blush / I get red, to blush
Colors:
Білий, біла - Bilyj (masc.) / Bila (fem.) - white
Зелений, зелена - Zelenyj / zelena- green
Чорний, чорна - Chornyj / chorna - black
Жовтий, жовта - Zhovtyj / zhovta - yellow
Коричневий, коричнева - Korychnevyj / korychneva - brown
Синій, Синя - Synij / synia - dark blue
Блакитний, блакитна - Blakytnyj / blakytna - light blue
Червоний, червона- chervonyj/ chervona- red
Світлий, світла- svitlyj/ svitla- light
Темний, темна- temnyj/ temna- dark
Сірий, сіра- siryj/ sira- grey
# Ukrainian/Common Phrases
## Ukrainian (Slavic)

Note: adjectives have different forms when describing feminine, masculine or neuter nouns.
| Translation | Phrase | IPA | pronunciation | Literally |
| Ukrainian | українська, f. український, m. українське, n. | /uˌkraˈjinˌs$^j$ka/ /uˌkraˈjinˌs$^j$kɪj/ /uˌkraˈjinˌs$^j$kɛ/ | ooh-kra-YEEN-ska ooh-kra-YEEN-skiy ooh-kra-YEEN-ske | |
| hello | привіт | /prɪˈvit/ | pri-VEET | “greetings” |
| good-bye | до побачення | /do poˈbaˌtʃenˌn$^j$a/ | doh po-BAH-chen-nyah | “until seeing” |
| please | будь ласка | /bud$^j$ ˈlaˌska/ | bood LA-ska | “be kind” |
| thank you | дякую | /ˈdjakuju/ | DYA -koo-yoo |
# World of Dinosaurs/Basal vs Derived

The terms "basal" and "derived" are relative. They only make sense if you provide the context - what clade are you talking about?
Examples:
* Coelophysis is a derived tetrapod, but it's a basal dinosaur.
* Archeopteryx is a derived dinosaur, but it's a basal bird.
Come up with your own examples. Within any clade of animals, what is a good example of a basal animal? What is a good example of a derived animal?
# World of Dinosaurs/Coelophysis
## Basics

Coelophysis means "Hollow Form".
Coelophysis lived during the Triassic Period.

## Anatomy

* Long slender skull
* Stands on elongated toes
* reduction in number of digits
* Upright stance on rear legs
* long neck and tail

## Phylogeny

Coelophysis is a theropod.
All theropods are dinosaurs.
All dinosaurs are amniotes and all dinosaurs are tetrapods.

## Biomechanics

Coelophysis jaws act much like a lever, making it more suited for a slashing motion.

## Fossil Record

Coelophysis are mainly found in New Mexico.

## Ecology

Coelophysis lived in an environment with fish, based on remains found in fossilized stomachs.
Grasses and flowers had not evolved yet.

## Biogeography

Coelophysis most likely lived in a dry, desert-like environment.
# World of Dinosaurs/Barosaurus
## Basics

Barosaurus means "Heavy Lizard".
Barosaurus lived during the Jurassic Period

## Anatomy

Barosaurus is a large plant-eating dinosaur.
It had a long tail and a small head.
It was about 66-88 feet long.

## Phylogeny

Barosaurus is a sauropod.
All sauropods are dinosaurs.
All dinosaurs are amniotes and all dinosaurs are tetrapods.

## Biomechanics

Based on the way Barosaurus necks are constructed, they might not have raised them, but rather swept them around the ground.

## Fossil Record

They are found in Utah and South Dakota.

## Ecology

Ferns, shrubs, and trees would have been common, but flowering plants, fruit trees, or grass were NOT around yet!
Barosaurus co-existed with Allosaurus as well as other sauropods.

## Biogeography

Rocks from the Jurassic period indicate hotter, wetter conditions than we experience on Earth today.
Rocks do not show signs of ice caps near the poles, of traveling ice-bergs, or other signs of "ice house" conditions.
Barosaurus lived in a semi-arid, seasonal floodplain. The super-continent Pangea was splitting up throughout the Jurassic Period, adding volcanic activity, particularly along the west coast, and warm, seasonally-variable habitats.
# World of Dinosaurs/Camarasaurus
## Basics

Camarasaurus means "Chambered Lizard".
Camarasaurus lived during the Jurassic Period.

## Anatomy

They have quadrupedal posture.
Their leg bones are thick like the pillars of a suspension bridge.
It has hollow chambers in its vertebrae, hence the name "Chambered Lizard".
It had chisel shaped teeth that helped it eat plants.

## Phylogeny

Camarasaurus is a sauropod.
All sauropods are dinosaurs.
All dinosaurs are amniotes and all dinosaurs are tetrapods.

## Biomechanics

Camarasaurus had a much stronger bite force than earlier saurodomorphs such as Plateosaurus which helps illustrate that Camarasaurus is a derived sauropod.
It may have weighed up to 20 tons.

## Fossil Record

Camarasaurus is found in Utah, New Mexico, and Nevada.

## Ecology

Camarasaurus co-existed with Allosaurus, a meat-eating dinosaur.
Ferns, shrubs, and trees would have been common, but flowering plants, fruit trees, or grass were NOT around yet!

## Biogeography

Rocks from the Jurassic period indicate hotter, wetter conditions than we experience on Earth today.
Rocks do not show signs of ice caps near the poles, of traveling ice-bergs, or other signs of "ice house" conditions.
The super-continent Pangea was splitting up throughout the Jurassic Period, adding volcanic activity, particularly along the west coast, and warm, seasonally-variable habitats.