Giter Site home page Giter Site logo

Comments (7)

proycon avatar proycon commented on May 28, 2024

The problem is frogging note/t and head/t I assume? If there's a node//s/t or head//s/t it should already work I reckon? I don't see what would change in FoLiA itself in any case though. Examining anything other than sentences is indeed a bit strange considering the whole thing is trained on sentences, but I guess allowing users to explicitly mention tags that could be treated as sentences (e.g. note/head) is a good idea.

from frog.

kosloot avatar kosloot commented on May 28, 2024

Well: Annotations may not directly be added to <head> nor <note>, so that IS a problem for FoLiA at the moment.

from frog.

proycon avatar proycon commented on May 28, 2024

Not? That would be strange indeed. But it should work already I think: https://github.com/proycon/folia/blob/master/schemas/folia.yml#L336 (and more inherited from AbstractStructureElement)

Edit: No token annotation under head/note makes sense, only makes sense for w.

from frog.

martinreynaert avatar martinreynaert commented on May 28, 2024

Not sure at all this is at all possible...

But should the user not be able to declare text in elements such as 'head' or 'note' as text, so that the tools recognize this as such and annotate accordingly?

This would allow the user to declare 'head' but not 'note' (or indeed vice versa should need be) as text and have it annotated.

My 2 cents, for now.

M.

from frog.

proycon avatar proycon commented on May 28, 2024

I think the conclusion is that this is not a Frog issue, but an ucto issue; Frog is right just to look at s. It's the task of ucto to provide s (sentence detection) and w (tokenisation) on any FoLiA structure element that can hold them (e.g. has them as ACCEPTED_DATA) and that does not already have deeper structure elements with text layers (t).

from frog.

kosloot avatar kosloot commented on May 28, 2024

added as LanguageMachines/ucto#23

from frog.

kosloot avatar kosloot commented on May 28, 2024

Ok, and ucto does what needs to be done, but assumes that the text content is correct.
This is a.o. dependent on proycon/folia#24
to summarize:
The textcontent of a Structure Element is a composition of the textcontents of the underlying elements (if present)

It is not the task of Frog or Ucto to enforce this.

from frog.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.