Closed TomazErjavec closed 4 years ago
Absolutely.
Could you do me a favor and paste some examples for each of these in this thread. We can then look at each of them and include them in the documentation when we revive them in the schema.
-- Belgrade Center for Digital Humanities http://humanistika.org
31 окт. 2019 г., в 12:10, Tomaž Erjavec notifications@github.com написал(а):
I just noticed that Lex0 disallows a number of elements from the TEI header which are rather useful, e.g.
(can't do without it!), (to say something about the project that enabled the work done), (e.g. for taxonomies), (to document tools used), and maybe others. Could these be de-removed?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DARIAH-ERIC/lexicalresources/issues/68?email_source=notifications&email_token=ABIPEB7FQHK4X5TENZODXDLQRK4IZA5CNFSM4JHIIJ5KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HVXR3BQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIPEB6NHOBSVOGPXGD73LTQRK4IZANCNFSM4JHIIJ5A.
Absolutely.
Thanks @ttasovac, good to hear that.
Could you do me a favor and paste some examples for each of these in this thread. We can then look at each of them and include them in the documentation when we revive them in the schema.
I think it is easiest if I point you to the resource I was working on when I noticed this: http://nl.ijs.si/et/tmp/kas/BiTerm/kas-biterm.test.xml, which is a draft of a automatically extracted list of bilingual term candidates from a corpus. So, the examples are the elements in the header that are commented out, which I had to do so I could validate the file.
PS: and in case there are some comments on the structure of the entries, I am of course happy to receive them!
I clearly agree. I can implement this as we agree on one element after the other. Let us start with <availability>
: a clear no-brainer, but we need to add <licence>
(otherwise, we only have <p>
there). Green light?
Belgrade Center for Digital Humanities http://humanistika.org
31 окт. 2019 г., в 12:20, laurentromary notifications@github.com написал(а):
I clearly agree. I can implement this as we agree on one element after the other. Let us start with
: a clear no-brainer, but we need to add (otherwise, we only have there). Green light?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DARIAH-ERIC/lexicalresources/issues/68?email_source=notifications&email_token=ABIPEBYCLHRBPKF7YRPPLSTQRK5QXA5CNFSM4JHIIJ5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXMDNY#issuecomment-548323767, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIPEBYKMDZ6GZZYFSXW63LQRK5QXANCNFSM4JHIIJ5A.
<projectDesc>
is already there, but for some reason - even if it does generates a RelaxNG that looks OK - the element does not actually show in <encodingDesc>
. There is bug and I have not managed to find out where yet...
<projectDesc>
is already there, but for some reason - even if it does generates a RelaxNG that looks OK - the element does not actually show in<encodingDesc>
. There is bug and I have not managed to find out where yet...
I'd really like to see encodingDesc/tagsDecl
and especially encodingDesc/tagsDecl/rendition
up and running. The fact that it's missing may be related to the bug you mentioned, @laurentromary.
Hurray, I have found the bug! It was <p>
missing: the element is required at various places in some header sub-components content models.
I could now add <tagsDecl>
and <rendition>
as suggested by @xlhrld if there is no objection from the group.
I could now add
<tagsDecl>
and<rendition>
as suggested by @xlhrld if there is no objection from the group.
👍
Done. Please check and close when OK.
I just noticed that Lex0 disallows a number of elements from the TEI header which are rather useful, e.g.
<availability>
(can't do without it!),<projectDesc>
(to say something about the project that enabled the work done),<classDecl>
(e.g. for taxonomies),<appInfo>
(to document tools used), and maybe others.Could these be de-removed?