<?xml version="1.0" encoding="UTF-8"?>
<competence xmlns="http://www.competencetools.eu/ecotool/competence"
	xmlns:dcterms="http://purl.org/dc/terms/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xml:lang="en"> 
<dcterms:identifier>http://www.example.com/abilities/winemaking/123</dcterms:identifier>
<dcterms:contributor>Simon Grant</dcterms:contributor>
<dcterms:contributor>Chiara Carlino</dcterms:contributor>
<dcterms:creator>Frederick Taylor</dcterms:creator>
<dcterms:created>2012-01-20T17:00:00.000+00:00</dcterms:created>
<definition xml:lang="en">
	<shortDescription>
		<actionVerb>Fill, label and pack</actionVerb>
		<complement>wine</complement>
	</shortDescription>
	<fullDescription><div xmlns="http://www.w3.org/1999/xhtml">
<p>Filling, labelling and packing wine may involve operating relevant specialist machinery.</p>
<ul>
<li>For large wine producers, the process will be largely automated, and the competence will involve extensive knowledge of the operation of the automatic machinery.</li>
<li>For small wine producers, each process may be separate and done manually, either by one person or by a team working together.</li>
</ul>
<p>In all cases, a person with this overall competence will take responsibility for ensuring that the wine is correctly labelled, and the labels on the wine corresponds to the label on the packs; and for ensuring that the whole process complies with relevant health and safety and trading standards regulations.</p>
</div></fullDescription>
</definition>
<definition xml:lang="it">
	<shortDescription>
		<actionVerb>Riempire, etichettare e impacchettare</actionVerb>
		<complement>il vino</complement>
	</shortDescription>
	<fullDescription>Riempire, etichettare e impacchettare il vino può richiedere l'uso di macchinari specialistici. Per produttori di vino su larga scala, il progesso sarà in gran parte automatizzato e la competenza includerà un'ampia conoscenza dell'operatività dei macchinari. Per piccoli produttori, ogni processo potrebbe essere separato e compiuto manualmente, da una persona o da una squadra. In ogni caso, una persona con questa competenza complessiva avrà la responsabilità di assicurarsi che il vino sia correttamente etichettato e che le etichette sul vino corrispondano a quelle sui pacchi; sarà inoltre responsabile di assicurarsi che l'intero processo si svolga in osservazione dei regolamenti standard di sicurezza salute e commercio.</fullDescription>
</definition>
<contextIdentifier>http://www.example.com/abilities/winemaking</contextIdentifier>
<!-- the following classification information is represented semantically equivalent to Atom, but with different syntax.
As Atom has no XSD, Atom attributes are redefined as elements here.
Other XML bindings are possible -->
<category>
	<term>11.02</term>
	<scheme>NACE</scheme>
	<label>Manufacture of wine from grape</label>
</category>
<category>
	<term>http://aims.fao.org/aos/agrovoc/c_8405</term>
	<scheme>http://aims.fao.org/aos/agrovoc/c_7644</scheme>
	<label>Winemaking</label>
</category>
<category>
	<term>http://aims.fao.org/aos/agrovoc/c_25770</term>
	<scheme>http://aims.fao.org/aos/agrovoc/c_330919</scheme>
	<label>Winemaking equipment</label>
</category>
<!-- ideally the scheme values should be IRIs, when canonical IRIs are available, and where more information about the scheme (including its common name) is available through the IRI. Clear agreements are needed between different parties exchanging information about whether a term is an extension to a IRI or a IRI in its own right. Both are potentially workable. Labels in different languages should be available through the IRI. -->
<relation>
	<relationship>eloc:isNecessaryPartOf</relationship>
	<otherIRI>http://www.example.com/abilities/winemaking/1</otherIRI>
</relation>
<relation>
	<relationship>skos:exactMatch</relationship>
	<otherIRI>http://www.example.fr/vinification/123</otherIRI>
</relation>
<attributedLevel>
	<levelScheme>ISCED</levelScheme>
	<levelID></levelID> <!-- in this case the label is the same as the number, so not needed, but this is not always the case -->
	<levelNumber>3</levelNumber>
</attributedLevel>
<!-- this example XML is intended to conform with the latest Application Profile of the eCOTOOL Competence Model -->
</competence>
