<div dir="ltr">Hi,<div><br></div><div>I will jump in here ;)</div><div><br></div><div>It makes no sense to restrict NIF to REST, primarily because WebSockets are IMHO so important for implementing practical linguistic web services. The problem with REST is that it doesn't really support <a href="https://en.wikipedia.org/wiki/Comet_(programming)">cometting</a>, and as such it can be difficult to effectively keep a large pipeline going without having to make a new connection for each dataset or having to handle with lag in the production of data items.</div><div><br></div><div><br></div><div>As for JSON-LD, I do love the Raptor library but I call bullshit on this quote... the Python guys can do it <a href="https://github.com/RDFLib/rdflib-jsonld/tree/master/rdflib_jsonld">under 1000 LOC</a>... Actually JSON-LD is super easy to implement for web services if you restrict the services to handling only a single context URI. Then the JSON-LD can be handled like normal JSON, hence no need for special RDF parsers.</div><div><br></div><div>Regards,</div><div>John</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 23, 2014 at 12:52 PM, Sebastian Hellmann <span dir="ltr"><<a href="mailto:hellmann@informatik.uni-leipzig.de" target="_blank">hellmann@informatik.uni-leipzig.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Also, I still haven't found the time to
check in detail whether it makes sense to restrict all NIF
services to REST. In principle yes, but as written above, this
needs some thought and I need to read about REST once more. <br>
<br>
JSON-LD will also come soon, but some RDF parsers don't read it,
because it is too complicated to parse: <br>
<a href="http://librdf.org/raptor/" target="_blank">http://librdf.org/raptor/</a> <br>
<br>
all the best,<br>
Sebastian<br>
<br>
<blockquote type="cite">
<h3>JSON Serializers</h3>
<p>Two serializers for to write triples encoded in JSON:</p>
<ol>
<li><code>json</code>: in a resource-centric abbreviated form
like Turtle or RDF/XML-Abbreviated as defined by:
<a href="http://www.w3.org/TR/2013/NOTE-rdf-json-20131107/" target="_blank">RDF
1.1
JSON Alternate Serialization (RDF/JSON)</a>, W3C Working
Group Note, 07 November 2013
</li>
<li><code>json-triples</code>: a triple-centric format based
on the
SPARQL results in JSON format.</li>
</ol>
<p>JSON-LD is not supported - too complex to implement.</p>
</blockquote><div><div class="h5">
<br>
<br>
<br>
On 23.09.2014 12:47, Sebastian Hellmann wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div>Hi Philipp,<br>
sorry, I should have taken a look earlier. I about to go on
holiday in two days and as you might know the pre-holiday time
is quite work intensive... <br>
<br>
Yes, the guidelines look very good. I am happy that you could
extract this from documentation. <br>
<br>
Ciro deployed stanford and opennlp the other day and gets things
runnging again:<br>
<a href="http://demo.nlp2rdf.org:9999/stanfordcorenlpn?f=text&i=This+is+a+test.&t=direct" target="_blank">http://demo.nlp2rdf.org:9999/stanfordcorenlpn?f=text&i=This+is+a+test.&t=direct</a><br>
<br>
There are some minor changes, which need to be discussed.<br>
<br>
for begin and endIndex: <br>
Serializer should use xsd:int , Parser must accept xsd:int,
xsd:long and xsd:nonNegativeInteger and no datatype<br>
Note: xsd:int (32-bit signed int) is optimized by most databases
and therefore provides benefits for SPARQL out of the box. <br>
xsd:nonNegativeInteger is the correct datatype allowing the
right-open interval of [0,inf) but I am not sure, if this
datatype is implemented. <br>
<br>
<br>
for anchorOf and isString:<br>
Serializer must use xsd:string <br>
-> this is to avoid people adding nametags, which can be
ambiguous.<br>
<br>
Other than that very good.<br>
There is a second way to chain parsers via:<br>
curl <a href="http://service1" target="_blank">http://service1</a> -d t="url"
--dataurlencode
<a href="http://demo.nlp2rdf.org:9999/stanfordcorenlpn?f=text&i=This+is+a+test.&t=direct" target="_blank">"http://demo.nlp2rdf.org:9999/stanfordcorenlpn?f=text&i=This+is+a+test.&t=direct"</a><br>
<br>
All the best,<br>
Sebastian<br>
<br>
On 23.09.2014 09:16, Philipp Cimiano wrote:<br>
</div>
<blockquote type="cite">Dear all, <br>
<br>
I was wondering why I have received no feedback other than
from Mariano Rico on the document I sent two weeks ago. My goal
is to finalize the guidelines for the LIDER project this week,
so I would appreciate any feedback. Confirming that the way we
have implemented the NIF-based services is fine would also be an
important type of feedback ;-) <br>
<br>
I attach the document again for ease of reference. <br>
<br>
Any feedback is welcome, thanks a lot! <br>
<br>
Philipp. <br>
<br>
Am 09.09.14 16:27, schrieb Philipp Cimiano: <br>
<blockquote type="cite">Dear all, <br>
<br>
I just joined the list. In the context of the European LIDER
project, I am trying to put together some guidelines on how to
implement NIF-based Restful NLP services. <br>
<br>
Our student Benjamin Siemoneit (CC) has put together a
document describing how he has set up two services, wrapping
the Stanford POS tagger and the Stanford parser. <br>
<br>
The document is attached. I would be very happy to get some
feedback on the document, i.e. on <br>
<br>
1) Parameters of services <br>
2) use of NIF vocabulary <br>
3) chaining of services via curl <br>
<br>
Enjoy the document ;-) <br>
<br>
Philipp. <br>
<br>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
NLP2RDF mailing list
<a href="mailto:NLP2RDF@lists.informatik.uni-leipzig.de" target="_blank">NLP2RDF@lists.informatik.uni-leipzig.de</a>
<a href="http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf" target="_blank">http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf</a>
</pre>
</blockquote>
<br>
<br>
<div>-- <br>
<small>Sebastian Hellmann<br>
AKSW/NLP2RDF research group<br>
Insitute for Applied Informatics (InfAI) and DBpedia
Association<br>
Events: <br>
* <b>Sept. 1-5, 2014</b> Conference Week in Leipzig,
including <br>
** <b>Sept 2nd</b>, <a href="http://mlode2014.nlp2rdf.org/" target="_blank">MLODE 2014</a> <br>
** <b>Sept 3rd</b>, <a href="http://wiki.dbpedia.org/meetings/Leipzig2014" target="_blank">2nd
DBpedia Community Meeting</a><br>
** <b>Sept 4th-5th</b>, <a href="http://semantics.cc/" target="_blank">SEMANTiCS (formerly i-SEMANTICS)
</a><br>
Venha para a Alemanha como PhD: <a href="http://bis.informatik.uni-leipzig.de/csf" target="_blank">http://bis.informatik.uni-leipzig.de/csf</a><br>
Projects: <a href="http://dbpedia.org" target="_blank">http://dbpedia.org</a>,
<a href="http://nlp2rdf.org" target="_blank">http://nlp2rdf.org</a>,
<a href="http://linguistics.okfn.org" target="_blank">http://linguistics.okfn.org</a>,
<a href="http://www.w3.org/community/ld4lt" target="_blank">https://www.w3.org/community/ld4lt</a><br>
Homepage: <a href="http://aksw.org/SebastianHellmann" target="_blank">http://aksw.org/SebastianHellmann</a><br>
Research Group: <a href="http://aksw.org" target="_blank">http://aksw.org</a><br>
Thesis:<br>
<a href="http://tinyurl.com/sh-thesis-summary" target="_blank">http://tinyurl.com/sh-thesis-summary</a><br>
<a href="http://tinyurl.com/sh-thesis" target="_blank">http://tinyurl.com/sh-thesis</a><br>
</small></div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
NLP2RDF mailing list
<a href="mailto:NLP2RDF@lists.informatik.uni-leipzig.de" target="_blank">NLP2RDF@lists.informatik.uni-leipzig.de</a>
<a href="http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf" target="_blank">http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf</a>
</pre>
</blockquote>
<br>
<br>
<div>-- <br>
<small>Sebastian Hellmann<br>
AKSW/NLP2RDF research group<br>
Insitute for Applied Informatics (InfAI) and DBpedia Association<br>
Events: <br>
* <b>Sept. 1-5, 2014</b> Conference Week in Leipzig, including
<br>
** <b>Sept 2nd</b>, <a href="http://mlode2014.nlp2rdf.org/" target="_blank">MLODE
2014</a> <br>
** <b>Sept 3rd</b>, <a href="http://wiki.dbpedia.org/meetings/Leipzig2014" target="_blank">2nd
DBpedia Community Meeting</a><br>
** <b>Sept 4th-5th</b>, <a href="http://semantics.cc/" target="_blank">SEMANTiCS
(formerly i-SEMANTICS) </a><br>
Venha para a Alemanha como PhD: <a href="http://bis.informatik.uni-leipzig.de/csf" target="_blank">http://bis.informatik.uni-leipzig.de/csf</a><br>
Projects: <a href="http://dbpedia.org" target="_blank">http://dbpedia.org</a>,
<a href="http://nlp2rdf.org" target="_blank">http://nlp2rdf.org</a>, <a href="http://linguistics.okfn.org" target="_blank">http://linguistics.okfn.org</a>,
<a href="http://www.w3.org/community/ld4lt" target="_blank">https://www.w3.org/community/ld4lt</a><br>
Homepage: <a href="http://aksw.org/SebastianHellmann" target="_blank">http://aksw.org/SebastianHellmann</a><br>
Research Group: <a href="http://aksw.org" target="_blank">http://aksw.org</a><br>
Thesis:<br>
<a href="http://tinyurl.com/sh-thesis-summary" target="_blank">http://tinyurl.com/sh-thesis-summary</a><br>
<a href="http://tinyurl.com/sh-thesis" target="_blank">http://tinyurl.com/sh-thesis</a><br>
</small></div>
</div></div></div>
<br>_______________________________________________<br>
NLP2RDF mailing list<br>
<a href="mailto:NLP2RDF@lists.informatik.uni-leipzig.de">NLP2RDF@lists.informatik.uni-leipzig.de</a><br>
<a href="http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf" target="_blank">http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf</a><br>
<br></blockquote></div><br></div>