<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
The basic unit in NIF is the nif:Context, so the document-level is covered, when the string in a nif:Context equals the content of a document. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
...<br>
<Alcoholism.txt#char=37028,<u></u>37043><br>
a nif:RFC5147String ;<br>
nif:beginIndex "37028" ;<br>
nif:endIndex "37043" ;<br>
itsrdf:taIdentRef <<a href="http://dbpedia.org/resource/Benzodiazepine" target="_blank">http://dbpedia.org/resource/<u></u>Benzodiazepine</a>> ;<br>
nif:referenceContext <Alcoholism.txt#char=0,91429> .<br></blockquote><div><br></div><div style>Just wondering why you don't use <Alcoholism.txt> when making assertions about the document as a whole rather than giving the entire character range as a qualifier. Presumably the same assertion would be true of <Alcoholism.txt#char=0,91427> too but if you are trying to encode document level meta-data and you have an identifier for the document, why not use it? </div>
<div style><br></div><div style>Steve</div><div> </div></div>-- <br>Department of Computing, Macquarie University<div><a href="http://web.science.mq.edu.au/~cassidy/" target="_blank">http://web.science.mq.edu.au/~cassidy/</a></div>
</div></div>