Ambiguity around annotation scopes
See original GitHub issueConsider the following line.
[a[] b []c]
Is this one annotation with the contents a[] b []c
? Or is it an item b
with two annotations a[
and ]c
? This ambiguity results from allowing square brackets inside annotations.
Another example:
[a [b]]
Is this
- an annotation with the contents
a [b]
, or - an item with contents
]
and an annotationa [b
?
In other words, which square bracket closes an annotation? The first one found, or the last one?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Dealing with Quantifier Scope Ambiguity in Natural Language ...
1.4.2 Scope annotation. In section 1.3, it was mentioned that a big challenge in dealing with QSA is the hand annotation of quantifier...
Read more >In Search of Ambiguity: A Three-Stage Workflow Design to ...
Ambiguity is an interaction between data instances and annotation guidelines; effectively, an ambiguous instance is a corner-case with respect to guidelines.
Read more >Chapter 6. Aspect Oriented Programming with Spring
Spring 2.0 introduces a simpler and more powerful way of writing custom aspects using either a schema-based approach or the @AspectJ annotation style....
Read more >Representing the effort in resolving ambiguous scope
Abstract. This work proposes a way to formally model online scope interpretation in terms of recent experimental results. Specifically, it attempts to ...
Read more >Constraining Scope Ambiguity in LFG+Glue - Stanford University
Abstract. A major strength of the Glue approach to semantic composition for LFG is that it accounts for quantifier scope ambiguity without the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe you could create an issue label “spec” for issues that discuss the margin specification.
Yeah it’s probably not too hard to implement, and the behavior seems like it would be the least surprising out of all the options.