Holger,
my Christmas wish: could you put SPIN API on GitHub so we could have
SNAPSHOT builds, pull requests, issue tracker etc?
Happy holidays :)
On Tue, Dec 22, 2015 at 2:55 PM, Holger Knublauch wrote:
> On 22/12/2015 1:46 PM, Martynas Jusevičius wrote:
>>
>> I'm stuck
Unclear.
1/ 2.11.0 is old. Use a later version with JSON-LD built-in.
2/ You may need to use RDFDataMgr.
Not sure at 2.11.old whether Lang registration interacted with the Jena
RDFReaderFImpl.
3/ Not clear what you registered and how.
4/ Did you call RIOT.init()? Maybe needed.
Andy
On 22/12/15 12:46, Martynas Jusevičius wrote:
I'm stuck with this version because the latest SPIN API (1.4.0) is
using it and last I heard Holger said he's not planning an upgrade :/
Does it matter?
2.12.0 has JSON-LD.
I registered the writer like this:
Correct, I've registered only the writer but attempting to read
JSON-LD. That is because content negotiation is based on
RDFLanguages.getRegisteredLanguages() and therefore JSON-LD is
included in Accept headers.
I guess I will need to keep track of actual readable/writable types
separately in
On 22/12/2015 1:46 PM, Martynas Jusevičius wrote:
I'm stuck with this version because the latest SPIN API (1.4.0) is
using it and last I heard Holger said he's not planning an upgrade :/
By coincidence I just filed an ISSUE on our internal JIRA to upgrade our
whole TopBraid code base to Jena
Hey,
I have a situation where I register a new Lang (JSON-LD) in Jena
2.11.0 but I only have a Writer for it, not a Reader. How can I check
whether Reader exists for a certain Lang before doing the actual read?
Right now I get an exception:
com.hp.hpl.jena.shared.NoReaderForLangException: