Hi Sebastain Indeed there seems to be quite some overlap between open annotation and NIF. The annotation we need cleraly go beyound NLP-annotation. We might want to say that according to engine A the second sentence was writter in a bad mood and that that according to engine B a particular referes to a the person with profile http://...
It would be good to see examples on how this looks like in NIF and Open Annotation. Cheers, Reto On Sun, May 26, 2013 at 10:31 PM, Sebastian Hellmann < [email protected]> wrote: > Hi Reto, > let me offer you a different perspective: > > Am 24.05.2013 15:40, schrieb Reto Bachmann-Gmür: > > I haven't had the time yet to look at NIF. I'm happy that you agree that >> Stanbol should express the annotations (wherever possible) using the >> emergen W3C annotation standard. >> > > Which standard do you mean with "emerging W3C annotation standard" ? NIF > or Open Annotation? > From a formal perspective NIF will be very official in June when > Internationalization Tag Set (ITS) Version 2.0 ( > http://www.w3.org/TR/its20 ) becomes a W3C recommendation. > Open Annotation is a community of practice (also a W3C community group) . > The formal W3C requirements for working groups and W3C recommendations do > not apply to them. > > NIF targets NLP web services and NLP middleware and frameworks. > Requirements for NIF are scalability, exactness, reproducibility of > annotations. > Open Annotation currently targets annotation of web resources from an end > user perspective, especially seen through a browser. > I am currently active on their mailing list, to help them with the NLP use > case (which is not at the core of their interest). > > From both viewpoints NIF is a more formal standard as well as more > pertinent for Stanbol. > There is a NIF community as well, but we wanted to get the technical core > straight, which is finished now, but not properly documented yet (due to > moving infrastructure). > > Please have a look at the (scientific) description: > http://svn.aksw.org/papers/**2013/ISWC_NIF/public.pdf<http://svn.aksw.org/papers/2013/ISWC_NIF/public.pdf> > > The core idea of the FISE ontology is quite good, but for us to include it > into NIF, it still needs some work. > The problem is, if Stanbol moves to Open Annotation completely, NIF will > need to fill this gap and create a model that is similar to the way Stanbol > works now. > This is why I started this issue. > > All the best, > Sebastian > > > >> To my understanding "Stanbol Enhancement Structure" is supposed to >> describe >> which ontological terms and construct are used to describe their >> enhancements. >> >> Cheers, >> Reto >> >> >> On Thu, May 23, 2013 at 5:38 PM, Sebastian Hellmann < >> [email protected]**leipzig.de <[email protected]>> >> wrote: >> >> Hello Reto, >>> ah yes, I read up on some of the Apache procedures to see how you are >>> working and I see now that the mailing list is the most important means >>> of >>> communication here. Thanks for pointing me to the issue. In principle, >>> do >>> you want me to comment here or in the issue tracker? >>> >>> Regarding the different models: >>> >>> First of all alignment should happen with the "Open Annotation Data >>> Model": >>> http://www.w3.org/ns/oa# >>> This is the most current version. Annotation Ontology was merged into it. >>> >>> I really recommend grounding any work on their model, as it is really >>> good >>> and powerful. I am not sure however, whether, it provides the right level >>> of scalability for NLP. >>> Looking at: >>> http://de.slideshare.net/****paolociccarese/open-**<http://de.slideshare.net/**paolociccarese/open-**> >>> annotation-specifiers-and-****specific-resources-tutorial<ht** >>> tp://de.slideshare.net/**paolociccarese/open-** >>> annotation-specifiers-and-**specific-resources-tutorial<http://de.slideshare.net/paolociccarese/open-annotation-specifiers-and-specific-resources-tutorial> >>> > >>> >>> There are 3 important things missing: >>> - inclusion of the actual text in the web service request >>> - providing best practices for identifiers, e.g. >>> http://purl.org/olia/penn.owl#****DT<http://purl.org/olia/penn.owl#**DT>< >>> http://purl.org/olia/penn.**owl#DT <http://purl.org/olia/penn.owl#DT>> >>> >>> - reducing the number of URNs and triples >>> >>> This is where NIF comes in. (If you are in doubt, please try to create an >>> OA example where a simple sentence is POS annotated over a web service). >>> >>> Regarding Ruperts problem with backward compatibility. >>> In a first step, it should be enough to build an RDF parser/serializer >>> based on the new OWL file. >>> >>> I didn't yet understand, what is meant exactly by "Stanbol Enhancement >>> Structure"[1]. >>> Is this the OWL file for serializing annotations (e.g. for use in SPARQL) >>> or does it describe the internal structure of the Stanbol Java Framework? >>> >>> I think the second one can stay as it is for now and then the new >>> structure should be created (as serialization format) meanwhile with the >>> clear aim to replace the former in the future. This would give all >>> clients >>> enough time to adapt. >>> >>> What do you think? >>> >>> All the best, >>> Sebastian >>> >>> [1] >>> http://stanbol.apache.org/****docs/trunk/components/**<http://stanbol.apache.org/**docs/trunk/components/**> >>> enhancer/enhancementstructure.****html<http://stanbol.apache.** >>> org/docs/trunk/components/**enhancer/enhancementstructure.**html<http://stanbol.apache.org/docs/trunk/components/enhancer/enhancementstructure.html> >>> > >>> >>> >>> >>> >>> Am 23.05.2013 14:12, schrieb Reto Bachmann-Gmür: >>> >>> Hi Sebastian >>>> >>>> Are you aware of >>>> https://issues.apache.org/****jira/browse/STANBOL-351<https://issues.apache.org/**jira/browse/STANBOL-351> >>>> <https:**//issues.apache.org/jira/**browse/STANBOL-351<https://issues.apache.org/jira/browse/STANBOL-351> >>>> > >>>> >>>> ? >>>> >>>> Rtaher than doing telcos we should discus things on the list. >>>> >>>> Cheers, >>>> Reto >>>> >>>> >>>> On Thu, May 23, 2013 at 9:27 AM, Sebastian Hellmann < >>>> [email protected]**leip**zig.de <http://leipzig.de> < >>>> [email protected]**leipzig.de<[email protected]> >>>> >> >>>> wrote: >>>> >>>> Hi all, >>>> >>>>> we created an OWL schema called NLP Interchange Format(NIF), which >>>>> leverages Apache Stanbols FISE ontology. >>>>> Recent documentation is here: >>>>> http://svn.aksw.org/papers/******2013/ISWC_NIF/public.pdf<http://svn.aksw.org/papers/****2013/ISWC_NIF/public.pdf> >>>>> <http**://svn.aksw.org/papers/**2013/**ISWC_NIF/public.pdf<http://svn.aksw.org/papers/**2013/ISWC_NIF/public.pdf> >>>>> > >>>>> <http:**//svn.aksw.org/papers/**2013/**ISWC_NIF/public.pdf<http://svn.aksw.org/papers/2013/**ISWC_NIF/public.pdf> >>>>> <htt**p://svn.aksw.org/papers/2013/**ISWC_NIF/public.pdf<http://svn.aksw.org/papers/2013/ISWC_NIF/public.pdf> >>>>> > >>>>> >>>>> >>>>> Personally, I think the general structure (using URN for each >>>>> annotation) >>>>> is quite good, but I am a little bit unhappy with some facts: >>>>> 1. URL persistence: when will the FISE ontology move from IKS to the >>>>> Apache Stanbol namespace. In my opinion, sooner is better. The longer >>>>> it >>>>> is >>>>> out there, the more side effects it will cause: >>>>> http://xkcd.com/1172/ >>>>> 2. Some issues need discussions and some streamlining. I would be happy >>>>> to >>>>> be of assistance and would offer to hold some Ontology telcos to get it >>>>> straight. >>>>> http://svn.apache.org/repos/******asf/stanbol/trunk/enhancer/****<http://svn.apache.org/repos/****asf/stanbol/trunk/enhancer/**> >>>>> <http://svn.apache.org/repos/****asf/stanbol/trunk/enhancer/****<http://svn.apache.org/repos/**asf/stanbol/trunk/enhancer/**> >>>>> > >>>>> generic/servicesapi/src/main/******resources/fise.owl<http://**** >>>>> svn.apache.org/repos/asf/****stanbol/trunk/enhancer/**<http://svn.apache.org/repos/asf/**stanbol/trunk/enhancer/**> >>>>> >>>>> generic/servicesapi/src/main/****resources/fise.owl<http://** >>>>> svn.apache.org/repos/asf/**stanbol/trunk/enhancer/** >>>>> generic/servicesapi/src/main/**resources/fise.owl<http://svn.apache.org/repos/asf/stanbol/trunk/enhancer/generic/servicesapi/src/main/resources/fise.owl> >>>>> > >>>>> e.g. >>>>> - start and end have xsd:int limiting it to a 4GB text file >>>>> - extracted-from might not need to be functional. Also there might be a >>>>> relation to prov:wasDerivedFrom >>>>> These issues all need discussion however. >>>>> >>>>> Any ideas on how to proceed? >>>>> >>>>> All the best, >>>>> Sebastian >>>>> >>>>> -- >>>>> Dipl. Inf. Sebastian Hellmann >>>>> Department of Computer Science, University of Leipzig >>>>> Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.****** >>>>> aksw.org< >>>>> http://nlp-**dbpedia2013.**blogs.aksw.org<http://dbpedia2013.blogs.aksw.org> >>>>> <http://nlp-**dbpedia2013.blogs.aksw.org<http://nlp-dbpedia2013.blogs.aksw.org> >>>>> > >>>>> >>>>>> , >>>>>> >>>>> Deadline: *July 8th*) >>>>> Venha para a Alemanha como PhD: http://bis.informatik.uni-****le** >>>>> ipzig.de/csf <http://leipzig.de/csf><http:/**/bis. <http://bis.>** >>>>> informatik.uni-leipzig.de/csf <http://bis.informatik.uni-** >>>>> leipzig.de/csf <http://bis.informatik.uni-leipzig.de/csf>> >>>>> >>>>> Projects: http://nlp2rdf.org , http://linguistics.okfn.org , >>>>> http://dbpedia.org/Wiktionary , http://dbpedia.org >>>>> Homepage: http://bis.informatik.uni-****le**ipzig.de/SebastianHellmann >>>>> **<http://leipzig.de/**SebastianHellmann<http://leipzig.de/SebastianHellmann> >>>>> > >>>>> <htt**p://bis.informatik.uni-****leipzig.de/SebastianHellmann<** >>>>> http://bis.informatik.uni-**leipzig.de/SebastianHellmann<http://bis.informatik.uni-leipzig.de/SebastianHellmann> >>>>> > >>>>> Research Group: http://aksw.org >>>>> >>>>> >>>>> -- >>> Dipl. Inf. Sebastian Hellmann >>> Department of Computer Science, University of Leipzig >>> Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.****aksw.org< >>> http://nlp-**dbpedia2013.blogs.aksw.org<http://nlp-dbpedia2013.blogs.aksw.org> >>> >, >>> Deadline: *July 8th*) >>> Venha para a Alemanha como PhD: http://bis.informatik.uni-**le** >>> ipzig.de/csf <http://leipzig.de/csf><http://bis.** >>> informatik.uni-leipzig.de/csf <http://bis.informatik.uni-leipzig.de/csf> >>> > >>> Projects: http://nlp2rdf.org , http://linguistics.okfn.org , >>> http://dbpedia.org/Wiktionary , http://dbpedia.org >>> Homepage: >>> http://bis.informatik.uni-**le**ipzig.de/SebastianHellmann<http://leipzig.de/SebastianHellmann> >>> <htt**p://bis.informatik.uni-**leipzig.de/SebastianHellmann<http://bis.informatik.uni-leipzig.de/SebastianHellmann> >>> > >>> Research Group: http://aksw.org >>> >>> > > -- > Dipl. Inf. Sebastian Hellmann > Department of Computer Science, University of Leipzig > Events: NLP & DBpedia 2013 > (http://nlp-dbpedia2013.blogs.**aksw.org<http://nlp-dbpedia2013.blogs.aksw.org>, > Deadline: *July 8th*) > Venha para a Alemanha como PhD: > http://bis.informatik.uni-**leipzig.de/csf<http://bis.informatik.uni-leipzig.de/csf> > Projects: http://nlp2rdf.org , http://linguistics.okfn.org , > http://dbpedia.org/Wiktionary , http://dbpedia.org > Homepage: > http://bis.informatik.uni-**leipzig.de/SebastianHellmann<http://bis.informatik.uni-leipzig.de/SebastianHellmann> > Research Group: http://aksw.org >
