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

who's developing NIF 2.1 and where? (Provenance and Confidence) #1

Open
VladimirAlexiev opened this issue Mar 14, 2016 · 4 comments
Open

Comments

@VladimirAlexiev
Copy link

The Provenance and Confidence in NIF 2.1 proposal (http://nif.readthedocs.org/en/2.1-rc/prov-and-conf.html):

  • It describes something completely different from the NIF+Stanbol (FISE) profile:

I wrote in NLP2RDF/specification#2 that I don't like that NIF+Stanbol uses completely different properties for "multiple annotations": the current proposal is better in this regard.

Can we have some assurance that the first link above will be the future NIF 2.1? We'd like to know this for sure before we make mega-tons of RDF in the Multisensor project.

There are several repos and thus several trackers under https://github.com/NLP2RDF (ontologies, specification, documentation), which is really bad, as I asked in NLP2RDF/ontologies#12.

  • Is someone looking at these trackers and addressing the issues?
  • Please "close" all but one: 1. Is it possible to move the outstanding issues to one tracker? 2. If you can't forbid posting, at least say it in red on the repo's home page.
@VladimirAlexiev
Copy link
Author

Just noticed that this proposal also disregards the direct props that exist in ITSRDF, eg:

  itsrdf:taAnnotatorsRef "text-analysis|http://linguatec.com";
  itsrdf:taConfidence 0.9.

@neradis
Copy link
Contributor

neradis commented Mar 15, 2016

There are several repos and thus several trackers under https://github.com/NLP2RDF (ontologies, specification, documentation), which is really bad

Totally agreeing with that. Followed your suggestions, added notes about not using the trackers in the specification and documentation repositories for issues with/discussion about the NIF ontology and vocabulary per se. We can still resort to actually close when there will be cases from now on the people continues posting misplaced issues there due to TL;DR-syndrome.

@neradis
Copy link
Contributor

neradis commented Mar 15, 2016

Just noticed that this proposal also disregards the direct props that exist in ITSRDF

In line with the issue tracker policy suggested I will quote that concern in the ontologies issue tracker to answer it.

@VladimirAlexiev
Copy link
Author

@neradis Could you please try to use https://github-issue-mover.appspot.com/ to "move" all open issues to ontologies? There's no "move" operation on github, but it makes a copy, closes the original and makes a link.

Got this tool from http://stackoverflow.com/questions/9720718/how-do-i-move-an-issue-on-github-to-another-repo, which mislav/hub#886 calls "a fount of knowledge" on the topic.

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

2 participants