Difference between revisions of "OSIS 211 CR"
(1 bug, 2 FRs) |
David Haslam (talk | contribs) m (Changed levels by +1, added category) |
||
| Line 1: | Line 1: | ||
| − | = Bugs = | + | == Bugs == |
| − | == osisGenRegex bug == | + | === osisGenRegex bug === |
Currently that regex looks like [1], but it should looks like [2]: | Currently that regex looks like [1], but it should looks like [2]: | ||
| Line 16: | Line 16: | ||
| − | = Feature requests = | + | == Feature requests == |
| − | == Allow <transChange> within <w> == | + | === Allow <transChange> within <w> === |
An encoder ought to be ''allowed'' to put <transChange> on elements smaller than an orthographic word. If I'm translating an instance of "λόγος", but for some reason I believe that I should translate it as "words", I ought to be able to encode <w>word<transChange>s</transChange></w>. --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC) | An encoder ought to be ''allowed'' to put <transChange> on elements smaller than an orthographic word. If I'm translating an instance of "λόγος", but for some reason I believe that I should translate it as "words", I ought to be able to encode <w>word<transChange>s</transChange></w>. --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC) | ||
| − | == Add an element for morphology within <w> == | + | === Add an element for morphology within <w> === |
Necessary for encoding documents like MORPH (WLC + morphology), we need an element to embed within <w> to carry lexical information. I suggest calling it <m> and giving it all of the attributes found on <w>. --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC) | Necessary for encoding documents like MORPH (WLC + morphology), we need an element to embed within <w> to carry lexical information. I suggest calling it <m> and giving it all of the attributes found on <w>. --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC) | ||
| + | |||
| + | [[Category:OSIS]] | ||
Revision as of 17:54, 12 December 2010
Contents
Bugs
osisGenRegex bug
Currently that regex looks like [1], but it should looks like [2]:
[1] ((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_))*:)?([^:\s])+)
[2] ((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_)+)*:)?([^:\s])+)
(missing + right here ^)
So our document with the following element isn't valid because the string "Strong" cannot be more than 1 character long in the current schema: <w morph="robinson:N-NSF" lemma="lemma.Strong:βίβλος">βίβλος</w> --Osk 19:48, 5 November 2010 (UTC)
Feature requests
Allow <transChange> within <w>
An encoder ought to be allowed to put <transChange> on elements smaller than an orthographic word. If I'm translating an instance of "λόγος", but for some reason I believe that I should translate it as "words", I ought to be able to encode <w>word<transChange>s</transChange></w>. --Osk 19:48, 5 November 2010 (UTC)
Add an element for morphology within <w>
Necessary for encoding documents like MORPH (WLC + morphology), we need an element to embed within <w> to carry lexical information. I suggest calling it <m> and giving it all of the attributes found on <w>. --Osk 19:48, 5 November 2010 (UTC)
