Deploy GitHub pages

docs/index.html

@@ -4381,6 +4381,6 @@
 tei_teidata.xpath = text<a href="#index.xml-eg-d33e35043" class="anchorlink">⚓</a></pre></td></tr><tr><td class="wovenodd-col1"><span xml:lang="en" lang="en" class="label">Note</span></td><td class="wovenodd-col2"><p>Any XPath expression using the syntax defined in <a class="link_ref" href="https://www.tei-c.org/release/doc/tei-p5-doc/en/html/BIB.html#XSLT2">6.2.</a>.</p><p>When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the <a class="link_ref" href="https://owasp.org/www-community/attacks/XPATH_Injection">article at OWASP</a>.</p></td></tr></table></div></div></div></section></div><!--Notes in [TEI]--><div class="notes"><div class="noteHeading">Notes</div><div class="note" id="Note1"><span class="noteLabel">1 </span><div class="noteBody">Note that this is a illustrative example, i.e. a valid ParlaMint corpus would also need certain attributes to be defined on the illustrated elements. This holds for all the examples in this section.</div> <a class="link_return" title="Go back to text" href="#Note1_return">↵</a></div><div class="note" id="Note2"><span class="noteLabel">2 </span><div class="noteBody">Note that parliaments also have unaffiliated (or independent) MPs, that can either belong to a special <span class="q">‘unaffiliated’</span> parliamentary group or don't belong to any parliamentary group. For the former, they are simply not affiliated to any parliamentary group. For the latter, an <span class="q">‘unaffiliated’</span> parlimentaryGroup organisation must be created, and such MPs are affiliated with it as members.</div> <a class="link_return" title="Go back to text" href="#Note2_return">↵</a></div><div class="note" id="Note3"><span class="noteLabel">3 </span><div class="noteBody">The typical situation is that the organisation somebody is affiliated with is specificed as a organisation, using the <a class="link_ref" href="#TEI.org" title="&lt;org&gt;">&lt;org&gt;</a> element (cf. the Section on <a class="link_ref" href="#sec-orgs" title="Organisations">Organisations</a>) but if this is not the case, using <a class="link_ref" href="#TEI.orgName" title="&lt;orgName&gt;">&lt;orgName&gt;</a> directly in the <a class="link_ref" href="#TEI.affiliation" title="&lt;affiliation&gt;">&lt;affiliation&gt;</a> is an alternative encoding.</div> <a class="link_return" title="Go back to text" href="#Note3_return">↵</a></div><div class="note" id="Note4"><span class="noteLabel">4 </span><div class="noteBody">Note that, according to TEI, a label should not appear in a state element in case this element contains subordinate state elements. In other words, this label makes the current encoding of ParlaMint corpora invalid according to TEI. This should be corrected in a future release.</div> <a class="link_return" title="Go back to text" href="#Note4_return">↵</a></div><div class="note" id="Note5"><span class="noteLabel">5 </span><div class="noteBody">Note that, in general, the utterance can also be split in the middle of a sentence, which brings with it problems for automatic linguistic processing, as, ideally, the parts should be first joined, and only then processed.</div> <a class="link_return" title="Go back to text" href="#Note5_return">↵</a></div><div class="note" id="Note6"><span class="noteLabel">6 </span><div class="noteBody">These are typically tagset developed and used for specific languages and can be found in the XPOS column of CoNLL-U files, which is the native format for UD treebanks.</div> <a class="link_return" title="Go back to text" href="#Note6_return">↵</a></div><div class="note" id="Note7"><span class="noteLabel">7 </span><div class="noteBody">Note that the example is rendered in three lines, however, the correct encoding in the corpus is actually in a single line, without any spaces between the elements, as otherwise the new line and indenting spaces are actually a part of the word <span class="q">‘abyste’</span>.</div> <a class="link_return" title="Go back to text" href="#Note7_return">↵</a></div><div class="note" id="Note8"><span class="noteLabel">8 </span><div class="noteBody">Because <a class="link_ref" href="#TEI.name" title="&lt;name&gt;">&lt;name&gt;</a> and <a class="link_ref" href="#TEI.phr" title="&lt;phr&gt;">&lt;phr&gt;</a> can give conflicting markup (i.e. crossing tags) the current script annotates phrases only where they are not related to names, i.e. not only conflicting markup, but also nestings of phr/name and name/phr are forbidden and such MWEs are not retained in the XML. Furthermore, due to a bug in the script, phrases adjecent to names are also not retained. We hope to introduce a better script and encoding in the future.</div> <a class="link_return" title="Go back to text" href="#Note8_return">↵</a></div></div><div class="stdfooter autogenerated"><div class="footer"><!--standard links to project, institution etc--><a class="plain" href="https://github.com/clarin-eric/parla-clarin">Home</a> </div><address>Tomaž Erjavec, [email protected], Matyáš Kopp, [email protected] and Andrej Pančur, [email protected]. Date: 2023-11-06<br/><!--
 	  Generated from index.xml using XSLT stylesheets version 7.55.0a
 	       based on http://www.tei-c.org/Stylesheets/
-	       on 2023-11-07T06:44:50Z.
+	       on 2023-11-07T06:46:38Z.
 	       SAXON HE 10.3.
 		 --></address></div></body></html>