Comments (3)
I've created a small unit test to reproduce the problem and can confirm it.
Currently the ResourceCollectionReaderBase class stores the original location
in the documentUri field. The issue can be fixed by storing the resolved URI in
the documentUri field and the resolved base URI in the baseUri field. I believe
that change does not break things for the users. However, the documentUri may
become quite different from the location passed into the TextReader. Possibly
there is another solution so that the documentUri still bears some resemblance
to the original location.
Original comment by richard.eckart
on 5 Sep 2011 at 6:54
from dkpro-core-asl.
Thinking about it, I believe it would be best not to insist on using the
original location as part of the documentUri, because that may lead to multiple
documents having the same documentUri. E.g. when resolving files from the
classpath, multiple files may be at the same classpath: location, but each one
will resolve to a separare jar: location.
Original comment by richard.eckart
on 5 Sep 2011 at 7:33
from dkpro-core-asl.
- Using resolved URI and resolved base URI to fill document metadata fields
- Added TextReader test case with space characters in path
---
rev 204
Original comment by richard.eckart
on 5 Sep 2011 at 7:56
- Changed state: Fixed
from dkpro-core-asl.
Related Issues (20)
- Question on StanfordCoreferenceResolver / grammatical dependencies HOT 8
- io.jwpl module cannot be built HOT 6
- Configurable punctuation and sentence boundary detection HOT 1
- Integrate Penn Discourse Treebank (PDTB) parser HOT 3
- Modules languagetool und decompounding use different versions of jwordsplitter HOT 10
- Upgrade to CoreNLP 3.5.1 HOT 1
- Add RTF Reader HOT 10
- Convert documentation to asciidoc
- StanfordCoreferenceResolver should copy dependencies from CAS instead of regenerating
- Integrate Stanford Dependency parser
- Add method to get output folder to DkproTestContext HOT 1
- Several Maven plugins not yet compatible with Java 7/8 language features HOT 4
- Improve TEI support HOT 1
- Support for constituents in TEI format HOT 3
- Add support for named entities to TEI HOT 2
- Possible bug if model location is set but language and mapping are not
- New "div" type for generic segmentation HOT 11
- Annotation types for speakers and direct/-indirect speech HOT 13
- For multiple files with same language code, only one is applied HOT 6
- Superseded by official GitHub migration
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dkpro-core-asl.