note: that wouldn't be a problem.. when merging those two efforts, old url mappings could still made be available.. and also the user authentication would be implemented. this is a first draft showcasing what would actually be expected from a modern sparql endpoint..
krj *Jürgen Jakobitsch* Innovation Director Semantic Web Company GmbH EU: +43-14021235 <+43%201%204021235> US: (415) 800-3776 Mobile: +43-676-6212710 <+43%20676%206212710> https://www.poolparty.biz https://www.semantic-web.com *Download now <https://www.poolparty.biz/wp-content/uploads/2017/08/IDC_Paper_How_Semantic_Technologies_Steer_Cognitive_Applications.pdf> **IDC White Paper* *Get certified! <https://www.poolparty.biz/academy/> **PoolParty Academy* *PoolParty selected as a KMWorld Trend-Setting Product for 2017* PERSONAL INFORMATION | web : http://www.turnguard.com | foaf : http://www.turnguard.com/turnguard | g+ : https://plus.google.com/111233759991616358206/posts | skype : jakobitsch-punkt | xmlns:tg = "http://www.turnguard.com/turnguard#"; | blockchain : https://onename.com/turnguard 2018-04-23 15:02 GMT+02:00 Puja Valiyil <[email protected]>: > I think we should probably keep supporting the old end point as well for > legacy users. > > Sent from my iPhone > > > On Apr 23, 2018, at 4:15 AM, Jürgen Jakobitsch < > [email protected]> wrote: > > > > hi, > > > > as mentioned in previous mails, we've setup a first draft of the proposed > > upgrade of rya's sparql endpoint.. again note, that we've setup a small > > debug/demo maven project using a sesame memory store to demonstrate the > > proposed changes. if the proposed upgrade of the sparql endpoint is > welcome > > we would incorporate this with existing rya code to include all required > > rya features. > > features: > > > > 1. full support for content-negotiation (essential within the > > linkeddata/semantic web realm) > > 2. SPARQL Service Description > > 3. more HTTP Status Codes (202 accepted, 400 bad request, 200 ok) > > 4. all RDF serialization formats available natively from sesame > > 5. customizable web endpoint (via a sesame MAVWriter (ModelAndView) + > JSPs > > + Styles) > > 6. valid XHTML for the endpoint > > 7. valid XHTML+RDFa in a browser for construct queries > > 8. a future rdf4j upgrade will not seriously affect the whole endpoint > > > > the project is very easy to build and you can checkout all features on > your > > local machine easily (examples are provided). the maven build will > include > > a tomcat hosting this sample endpoint, descriptions and code can be found > > here: > > > > https://github.com/jj-semantic-web-com/rya-sparql-endpoint > > > > any feedback, pointers, comments and wishes are highly welcome! > > > > related JIRA task: https://issues.apache.org/jira/browse/RYA-477 > > > > kr jürgen > > > > *Jürgen Jakobitsch* > > Innovation Director > > Semantic Web Company GmbH > > EU: +43-14021235 <+43%201%204021235> > > US: (415) 800-3776 > > Mobile: +43-676-6212710 <+43%20676%206212710> > > https://www.poolparty.biz > > https://www.semantic-web.com > > > > *Download now > > <https://www.poolparty.biz/wp-content/uploads/2017/08/IDC_ > Paper_How_Semantic_Technologies_Steer_Cognitive_Applications.pdf> > > **IDC > > White Paper* > > *Get certified! <https://www.poolparty.biz/academy/> **PoolParty > Academy* > > > > > > *PoolParty selected as a KMWorld Trend-Setting Product for 2017* > > > > > > PERSONAL INFORMATION > > | web : http://www.turnguard.com > > | foaf : http://www.turnguard.com/turnguard > > | g+ : https://plus.google.com/111233759991616358206/posts > > | skype : jakobitsch-punkt > > | xmlns:tg = "http://www.turnguard.com/turnguard#"; > > | blockchain : https://onename.com/turnguard >
