Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
@ajs6f ah, OK, thank you. So I'll do it shortly
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/139
@fpservant, No, using that button, you can send a patch for the page now,
but it will not be applied until the trigger is pulled to republish the docs
pages. That will happen for the release.
---
If
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
@afs thanks to you.
> What should I link to to say "it's new - read this"?
good question. I think that the best is to link to the sample code, where
I've tried to explain what can
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
Merged! Thank you!
I'd like to announce it on dev@ (and maybe encourage some people on users@)
to get feedback before we do the 3.1.1 release.
What should I link to to say "it's new -
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
OK - I can work with that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
@afs as I said in y previous mess, I don't seem to be able to get rid of
the conflict (but I am not an expert with git and github) The only solution I
see that would probably work would mean to move
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
> do you mean: "see if I can do something to get rid of the conflict" ?
Yes. If you can't cause git(hub) to not complain, just log here what to do
for the person doing the git merge on this pull
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
@afs,
> If possible, please see if the PR can be alighed to the current Jena
master branch for a clean merge
do you mean: "see if I can do something to get rid of the conflict" ?
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
@acoburn - thanks - that sort of feedback is very useful.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user acoburn commented on the issue:
https://github.com/apache/jena/pull/139
While this isn't exactly a review, I would add that what @fpservant has
implemented here is _exactly_ what I need for some projects I work on --
projects that make heavy use of Jena, but when it comes
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
@stain yes, JSONLD-java can download a context from a URL, and cache it.
The problem is, there is no way that I know of that would allow me to use that
context in a write operation initiated from
Github user stain commented on the issue:
https://github.com/apache/jena/pull/139
If you get the HTTPClient working again, then you should be able to use
JSONLD-Java's
[Caching
mechanism](https://github.com/jsonld-java/jsonld-java#loading-contexts-from-classpathjar)
to avoid
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
I updated this with some sample code, and it seems to me that this is as
good as *I* can. The sample code is the best place to learn how it works and
what it does.
Andy, answering your
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
Andy,
I have reverted to an unmodified version of RDFDataMgr (without write
methods with a context param).
I am sorry that I take so long to finalize this stuff. Remember that one
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
So how many additional 'write+Context' operations? Just the RDFFormat ones
for now?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
I'm not opposed to adding "Context" variants on principle, just a concern
about warping the API in the application writers view by many operations (not
that there are a few at the moment!). There are 22
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
Hi Andy,
getting back to this after, well, a long summer.
I have a remark regarding your following comment:
> RDFDataMgr
>
> The way to set things specially for a writing is to do:
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
Andy
> Apologies that this has taken so long.
no problem, really. Thanks for this answer. Give me some time to take all
your valuable comments into account.
just one remark:
> I
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
JIRA created to track this: https://issues.apache.org/jira/browse/JENA-1208
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user afs commented on the issue:
https://github.com/apache/jena/pull/139
Apologies that this has taken so long.
> TODO some documentation. Where should it be added? The best form would be
small sample code.
Examples can go in
20 matches
Mail list logo
