Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDF4J conversion #56

Open
ansell opened this issue Aug 3, 2016 · 3 comments
Open

RDF4J conversion #56

ansell opened this issue Aug 3, 2016 · 3 comments

Comments

@ansell
Copy link
Collaborator

ansell commented Aug 3, 2016

General issue for the conversion to RDF4J.

Other than the technical changes that should be fairly straightforward, should we change the name to something not including the word "sesame" anymore.

joshsh added a commit that referenced this issue Aug 3, 2016
@joshsh
Copy link
Owner

joshsh commented Aug 3, 2016

Good question. RDFTools4J? If we can find a good name, then yes. Otherwise, I don't think there is much harm in letting the name decouple.

@ansell
Copy link
Collaborator Author

ansell commented Aug 3, 2016

Keeping the status quo and decoupling may be useful to keep the brand in the long term, but may cause confusion in the near future. I don't have any immediate good names to propose though so maybe just staying with the current name would be the best way to go.

@abrokenjester
Copy link

abrokenjester commented Aug 3, 2016

Just freewheeling here (and also going slightly off topic), but have you considered a possible merge with the RDF4J project? We'd be overjoyed to have you on board.

Not something to decide on overnight of course and I'll understand if you prefer to keep the project under your own control. But I can't help thinking that having our committers cooperate more will benefit everyone.

Btw apologies if I asked this before and you already said no. I honestly can't remember :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants