Make `legacyDataType` accessible?
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 712
- Avg merge
- 15h 41m
- Merged PRs (30d)
- 53
Description
### Version
5.4.0-SNAPSHOT (a1ca2b7c3d38263766f25a0ce1414292edc55ffe)
### Feature
In [jena-core/src/main/java/org/apache/jena/graph/NodeFactory.java](
https://github.com/apache/jena/blob/a1ca2b7c3d38263766f25a0ce1414292edc55ffe/jena-core/src/main/java/org/apache/jena/graph/NodeFactory.java#L265),
There is a line:
```java
/*package*/ static final boolean legacyLangTag = false;
```
There is currently no way for a library user to change this value.
For my use-case (an RDF Linter), it is very useful to set this to true.
I did so in code, installing the library from source locally, and then using it in the linter. That allows me to find issues with lang-tags in Turtle files, for example.
Would it be an option to set this field to public, so that I don't have to maintain a separate version of the library and keeping it up to date, just for this functionality?
### Are you interested in contributing a solution yourself?
Yes
Contributor guide
Research direction
Start in jena-core/src/main/java/org/apache/jena/graph/NodeFactory.java at the referenced legacyLangTag declaration. Review how this setting should be exposed to library users and verify that the resulting API supports the RDF linter use case without requiring a locally maintained Jena build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100