[NLP2RDF] Guidelines for RESTful NIF-based services

[Sebastian Hellmann]

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.

JSON-LD will also come soon, but some RDF parsers don't read it, because 
it is too complicated to parse:
http://librdf.org/raptor/

all the best,
Sebastian

>
>       JSON Serializers
>
> Two serializers for to write triples encoded in JSON:
>
>  1. |json|: in a resource-centric abbreviated form like Turtle or
>     RDF/XML-Abbreviated as defined by: RDF 1.1 JSON Alternate
>     Serialization (RDF/JSON)
>     <http://www.w3.org/TR/2013/NOTE-rdf-json-20131107/>, W3C Working
>     Group Note, 07 November 2013
>  2. |json-triples|: a triple-centric format based on the SPARQL
>     results in JSON format.
>
> JSON-LD is not supported - too complex to implement.
>



On 23.09.2014 12:47, Sebastian Hellmann wrote:
> Hi Philipp,
> 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...
>
> Yes, the guidelines look very good. I am happy that you could extract 
> this from documentation.
>
> Ciro deployed stanford and opennlp the other day and gets things 
> runnging again:
> http://demo.nlp2rdf.org:9999/stanfordcorenlpn?f=text&i=This+is+a+test.&t=direct
>
> There are some minor changes, which need to be discussed.
>
> for begin and endIndex:
> Serializer should use xsd:int , Parser must accept xsd:int, xsd:long 
> and xsd:nonNegativeInteger and no datatype
> Note: xsd:int (32-bit signed int) is optimized by most databases and 
> therefore provides benefits for SPARQL out of the box.
> xsd:nonNegativeInteger is the correct datatype allowing the right-open 
> interval of [0,inf) but I am not sure, if this datatype is implemented.
>
>
> for anchorOf and isString:
> Serializer must use xsd:string
> -> this is to avoid people adding nametags, which can be ambiguous.
>
> Other than that very good.
> There is a second way to chain parsers via:
> curl http://service1 -d t="url" --dataurlencode 
> "http://demo.nlp2rdf.org:9999/stanfordcorenlpn?f=text&i=This+is+a+test.&t=direct"
>
> All the best,
> Sebastian
>
> On 23.09.2014 09:16, Philipp Cimiano wrote:
>> Dear all,
>>
>>   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 ;-)
>>
>> I attach the document again for ease of reference.
>>
>> Any feedback is welcome, thanks a lot!
>>
>> Philipp.
>>
>> Am 09.09.14 16:27, schrieb Philipp Cimiano:
>>> Dear all,
>>>
>>>  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.
>>>
>>> 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.
>>>
>>> The document is attached. I would be very happy to get some feedback 
>>> on the document, i.e. on
>>>
>>> 1) Parameters of services
>>> 2) use of NIF vocabulary
>>> 3) chaining of services via curl
>>>
>>> Enjoy the document ;-)
>>>
>>> Philipp.
>>>
>>
>>
>>
>> _______________________________________________
>> NLP2RDF mailing list
>> NLP2RDF at lists.informatik.uni-leipzig.de
>> http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf
>
>
> -- 
> Sebastian Hellmann
> AKSW/NLP2RDF research group
> Insitute for Applied Informatics (InfAI) and DBpedia Association
> Events:
> * *Sept. 1-5, 2014* Conference Week in Leipzig, including
> ** *Sept 2nd*, MLODE 2014 <http://mlode2014.nlp2rdf.org/>
> ** *Sept 3rd*, 2nd DBpedia Community Meeting 
> <http://wiki.dbpedia.org/meetings/Leipzig2014>
> ** *Sept 4th-5th*, SEMANTiCS (formerly i-SEMANTICS) <http://semantics.cc/>
> Venha para a Alemanha como PhD: http://bis.informatik.uni-leipzig.de/csf
> Projects: http://dbpedia.org, http://nlp2rdf.org, 
> http://linguistics.okfn.org, https://www.w3.org/community/ld4lt 
> <http://www.w3.org/community/ld4lt>
> Homepage: http://aksw.org/SebastianHellmann
> Research Group: http://aksw.org
> Thesis:
> http://tinyurl.com/sh-thesis-summary
> http://tinyurl.com/sh-thesis
>
>
> _______________________________________________
> NLP2RDF mailing list
> NLP2RDF at lists.informatik.uni-leipzig.de
> http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf


-- 
Sebastian Hellmann
AKSW/NLP2RDF research group
Insitute for Applied Informatics (InfAI) and DBpedia Association
Events:
* *Sept. 1-5, 2014* Conference Week in Leipzig, including
** *Sept 2nd*, MLODE 2014 <http://mlode2014.nlp2rdf.org/>
** *Sept 3rd*, 2nd DBpedia Community Meeting 
<http://wiki.dbpedia.org/meetings/Leipzig2014>
** *Sept 4th-5th*, SEMANTiCS (formerly i-SEMANTICS) <http://semantics.cc/>
Venha para a Alemanha como PhD: http://bis.informatik.uni-leipzig.de/csf
Projects: http://dbpedia.org, http://nlp2rdf.org, 
http://linguistics.okfn.org, https://www.w3.org/community/ld4lt 
<http://www.w3.org/community/ld4lt>
Homepage: http://aksw.org/SebastianHellmann
Research Group: http://aksw.org
Thesis:
http://tinyurl.com/sh-thesis-summary
http://tinyurl.com/sh-thesis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.informatik.uni-leipzig.de/pipermail/nlp2rdf/attachments/20140923/037c2710/attachment-0001.html>