We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@kurzum "do you also agree to merge nifs:Annotation from https://github.com/NLP2RDF/ontologies/blob/master/nif-core/nif-stanbol.ttl#L78 into nif-core and rename it AnnotationUnit ? We really need the feature to express basic alternative annotations."
Such node is definitely needed. But let's examine "prior art". in chronological order I think it is:
2 is contradicted by 3, eg
But I guess 2 is older and 3 is current.
I don't know if someone has used 3 (NIF Stanbol). Multisensor hasn't.
I'd be happy if you consolidate all this into AnnotationUnit and friends. KEY QUESTION: I guess that with NIF 2.1, the Stanbol profile will go away?
Ideally and if possible, this should be coordinated with the FAM people, but I don't know any of them...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@kurzum "do you also agree to merge nifs:Annotation from https://github.com/NLP2RDF/ontologies/blob/master/nif-core/nif-stanbol.ttl#L78 into nif-core and rename it AnnotationUnit ? We really need the feature to express basic alternative annotations."
Such node is definitely needed. But let's examine "prior art". in chronological order I think it is:
2 is contradicted by 3, eg
But I guess 2 is older and 3 is current.
I don't know if someone has used 3 (NIF Stanbol). Multisensor hasn't.
I'd be happy if you consolidate all this into AnnotationUnit and friends.
KEY QUESTION: I guess that with NIF 2.1, the Stanbol profile will go away?
Ideally and if possible, this should be coordinated with the FAM people, but I don't know any of them...
The text was updated successfully, but these errors were encountered: