Okay, Reto, that approach makes a lot of sense. It's important to match the
scope of work to the real extent of community resources. In that view, I would
go work on a "server-side type-driven template" system elsewhere.
But let me ask a follow-up question then: what exactly _is_ the core that will
continue within Apache? (I mean in terms of functionality/intention.) Is it
YARA ("yet another RDF API")? Let me make my question pragmatic: if I go and
write a "type-driven template" system, why would I base it on Clerezza instead
of, say, Commons RDF? I'm not asking that question to be annoying (really!); I
sincerely want to be able to articulate the value that Clerezza is offering
that distinguishes it from other projects in the same space. Is it dataset
management?
ajs6f
> On Nov 27, 2017, at 9:32 AM, [email protected] wrote:
>
> Hi A., All,
>
> The idea when reducing clerezza was to have the components that should be
> more stable, notably the core API, at apache so that these benefit by the
> quality assured by the apache process. On the other hand promote small
> projects based on clerezza elsewhere so they can have faster cycles. You're
> more than welcome to join both the core at apache as well as any dependent
> project I'm involved with. But at the moment I see the priority at apache in
> documenting the core modules and API. And simplifying the DataSet API
> (TcManager), probably making it part of the rdf.core repo. I'm not sure
> however if still need both repositories.
> Cheers,
> Reto
>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]]
>> Sent: Tuesday, November 14, 2017 4:53 PM
>> To: [email protected]
>> Subject: Re: Fwd: Interested in becoming a Clerezza committer ?
>>
>>> server side rdf type handling and rendering
>>
>> This would be something I would be glad to work on. I think it would be
>> really
>> useful to a lot of people. JAX-RS implementation independence makes sense,
>> of course.
>>
>> A Clerezza equipped with this kind of functionality could advertise that
>> just by
>> adding a triplestore of your choice, you have a complete application
>> framework that speaks RDF "natively" from disk all the way up.
>>
>>
>> ajs6f
>>
>> Hasan Hasan wrote on 11/14/17 2:26 AM:
>>> Hi Reto,
>>>
>>> so basically we could implement a server side rdf type handling and
>> rendering without using triaxrs?
>>> If yes, wouldn't it be a good part of clerezza to introduce?
>>> And A.Soroka might also be interested in implementing that?
>>>
>>> @A. Soroka, yes... if I am not mistaken... we want to have Clerezza
>> independent of a particular JAX-RS implementation.
>>>
>>> Cheers
>>> Hasan
>>>
>>>
>>> On Tue, Nov 14, 2017 at 7:27 AM, Reto Gmür <[email protected]
>> <mailto:[email protected]>> wrote:
>>>
>>> Hi,
>>>
>>> Check out https://github.com/linked-solutions/tlds
>> <https://github.com/linked-solutions/tlds> for a clerezza based
>>> linked data server applying client-side type-based rendering. It would be
>> possible to have a very similar
>>> implementation that implements e.g. scala-server pages.
>>>
>>> Cheers,
>>> Reto
>>>
>>>> -----Original Message-----
>>>> From: [email protected] <mailto:[email protected]>
>> [mailto:[email protected] <mailto:[email protected]>]
>>>> Sent: Monday, November 13, 2017 12:34 PM
>>>> To: [email protected] <mailto:[email protected]>
>>>> Subject: Re: Fwd: Interested in becoming a Clerezza committer ?
>>>>
>>>> Hey, Hasan--
>>>>
>>>> Are you thinking of some particular issues to avoid when bringing type-
>> based
>>>> rendering back? I.e. were there reasons we can point at that it was
>> removed
>>>> the first time that we want to avoid in future?
>>>>
>>>>
>>>> ajs6f
>>>>
>>>> Hasan wrote on 11/13/17 10:46 AM:
>>>>> Hi all
>>>>>
>>>>> I think ajs6f (A. Soroka, sorry, don't know your firstname) has a good
>>>>> point here.
>>>>> Is clerezza without the legacy code still attractive for people to
>>>>> contribute?
>>>>>
>>>>> @A. Soroka: IMO, if you could propose a functionality to implement on
>> top
>>>>> of clerezza in a clean way
>>>>> e.g. the type-based rendering stuff but without adding a whole bunch
>> of
>>>>> other issues,
>>>>> we might want to make that a part of clerezza in a new stack.
>>>>> By being a committer, one could participate in defining the further
>>>>> development of clerezza.
>>>>>
>>>>> I'd be glad to hear the opinions of other clerezza devs.
>>>>>
>>>>> regards
>>>>> hasan
>>>>>
>>>>>
>>>>> On Mon, Nov 13, 2017 at 3:51 PM, <[email protected]
>> <mailto:[email protected]>> wrote:
>>>>>
>>>>>> Hello, Hasan--
>>>>>>
>>>>>> I didn't make very much progress (really any) on resuscitating the
>>>>>> type-based rendering system because about that time I got heavily
>> involved
>>>>>> as a committer for Jena. I'm still interested in pursuing that work,
>>>>>> tho'.
>>>>>>
>>>>>> I'm certainly interested in being a committer for Clerezza, but I feel
>>>>>> that I have to ask, what is Clerezza? I don't mean that in a joking way,
>> I
>>>>>> mean that without the type-based rendering system, I'm not sure
>> exactly
>>>>>> when I would use Clerezza instead of a more well-developed and
>> older RDF
>>>>>> framework like Jena or RDF4J. And if I need a measure of
>> independence
>>>> from
>>>>>> specific implementations, I could use Commons RDF to achieve that
>> for
>>>> most
>>>>>> core RDF concepts.
>>>>>>
>>>>>> I got interested in Clerezza because of the type-based-rendering
>> system,
>>>>>> which seemed to offer the possibility (a little bit like LDPath
>> templating)
>>>>>> of an elegant stack that could take me from persistence in a
>> triplestore
>>>>>> all the way through into a browser or phone, without making me work
>> at
>>>>>> spending time gluing together different layers that were never
>> intended to
>>>>>> handle linked data.
>>>>>>
>>>>>> Can we articulate some clear, simple use cases for Clerezza?
>>>>>>
>>>>>> ajs6f
>>>>>>
>>>>>>
>>>>>> A. Soroka wrote on 11/13/17 9:36 AM:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Begin forwarded message:
>>>>>>>>
>>>>>>>> *From: *Hasan <[email protected] <mailto:[email protected]>
>> <mailto:[email protected] <mailto:[email protected]>>>
>>>>>>>> *Subject: **Re: Interested in becoming a Clerezza committer ?*
>>>>>>>> *Date: *November 12, 2017 at 4:52:11 AM EST
>>>>>>>> *To: *"[email protected]
>> <mailto:[email protected]> <mailto:[email protected]
>>> <mailto:[email protected]>>" <
>>>>>>>> [email protected] <mailto:[email protected]>
>>>>>>>> <mailto:[email protected]
>> <mailto:[email protected]>>>
>>>>>>>> *Reply-To: *[email protected]
>> <mailto:[email protected]> <mailto:[email protected]
>>> <mailto:[email protected]>>
>>>>>>>>
>>>>>>>> Hi Reto, Stian, A. Soroka, and all Clerezza Devs.
>>>>>>>>
>>>>>>>> A year ago I started this thread.
>>>>>>>> I have made some small improvements to the website esp. the
>> tutorials.
>>>>>>>> I admit It is a slow progress, but better slow than not at all.
>>>>>>>> I'd like to count on you all to make a faster progress.
>>>>>>>> So, if you have some ideas or would like to write or co-write
>> tutorials,
>>>>>>>> please let us know.
>>>>>>>>
>>>>>>>> Further, I would like to ask for suggestions on how to improve our
>>>>>>>> existing
>>>>>>>> codes.
>>>>>>>> Do you have issues that can be resolved within this project?
>>>>>>>>
>>>>>>>> @A. Soroka: How was the outcome of your efforts to use parts of
>> Apache
>>>>>>>> Clerezza Legacy codes (typerendering and typehandlerspace) ?
>>>>>>>>
>>>>>>>> @all: Would you like to become a new committer to further
>> develop
>>>> Apache
>>>>>>>> Clerezza?
>>>>>>>> Is there anything you miss that you want to see within Apache
>> Clerezza?
>>>>>>>>
>>>>>>>> @Reto: What would you suggest to make Apache Clerezza more
>> usable?
>>>>>>>>
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>> Hasan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Nov 15, 2016 at 8:47 AM, Hasan Hasan <[email protected]
>> <mailto:[email protected]>
>>>> <mailto:
>>>>>>>> [email protected] <mailto:[email protected]>>> wrote:
>>>>>>>>
>>>>>>>> Hi Stian
>>>>>>>>>
>>>>>>>>> On Sun, Nov 13, 2016 at 4:16 PM, Stian Soiland-Reyes
>>>> <[email protected] <mailto:[email protected]>
>>>>>>>>> <mailto:[email protected] <mailto:[email protected]>>>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Agree for playing on Clerezzas strengths on JAX-RS and I would say
>> to
>>>>>>>>>> actually include the SPARQL-as-Graph binding as well.
>>>>>>>>>>
>>>>>>>>>> Also worth seeing if there is possible crossover with the new
>> incubator
>>>>>>>>>> podling Apache Juneau which is also looking for contributors:
>>>>>>>>>> http://juneau.incubator.apache.org/#about.html
>> <http://juneau.incubator.apache.org/#about.html>
>>>>>>>>>>
>>>>>>>>>> I think the Clerezza website need a bit of similar tutorials to get
>>>>>>>>>> started
>>>>>>>>>> so potential contributors understand what it is all about.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Yes, it urgently needs an update.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> http://clerezza.apache.org/getting-started/
>> <http://clerezza.apache.org/getting-started/> links to "RESTful Web
>>>>>>>>>> Service
>>>>>>>>>> Framework (JAX-RS) Tutorial", "RDF Tutorial" and "Tutorial:
>> Combining
>>>>>>>>>> JAX-RS and RDF" which are all 404 :-(
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Should probably be removed since it is not what Clerezza currently
>> is
>>>>>>>>> now?
>>>>>>>>> It's a pity to remove a good tutorial,
>>>>>>>>> but what do you think?
>>>>>>>>>
>>>>>>>>> Cheers
>>>>>>>>> Hasan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 10 Nov 2016 4:18 pm, "A. Soroka" <[email protected]
>> <mailto:[email protected]> <mailto:
>>>>>>>>>> [email protected] <mailto:[email protected]>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi, Clerezza-folks!
>>>>>>>>>>>
>>>>>>>>>>> The most exciting part of Clerezza to me, by far, is the JAX-RS
>>>>>>>>>>> support.
>>>>>>>>>>>
>>>>>>>>>>> I'd rather work on Commons RDF (or Jena, where I am a
>> committer
>>>> now)
>>>>>>>>>>> to
>>>>>>>>>>> move RDF APIs forward, and there are lots of powerful SPARQL
>> impls
>>>> out
>>>>>>>>>>> there, each with its own streangths and weaknesses. But the
>> JAX-RS
>>>>>>>>>>>
>>>>>>>>>> thing--
>>>>>>>>>>
>>>>>>>>>>> that's completely unique to Clerezza, and it's a really cool idea.
>>>>>>>>>>> It's
>>>>>>>>>>>
>>>>>>>>>> not
>>>>>>>>>>
>>>>>>>>>>> always easy to move RDF to and from the Web, and JAX-RS is a
>>>> powerful,
>>>>>>>>>>> stable, enormously-well-supported technology so reusing it is a
>> great
>>>>>>>>>>> tactical move. I'd be interested in working on Clerezza, but really
>>>>>>>>>>> only
>>>>>>>>>>> for the JAX-RS part. I'd actually be happy to see the RDF API
>> move
>>>>>>>>>>>
>>>>>>>>>> towards
>>>>>>>>>>
>>>>>>>>>>> Commons (focus the efforts for more power!).
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> A. Soroka
>>>>>>>>>>> Apache Jena PMC
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Nov 8, 2016, at 12:25 AM, Hasan <[email protected]
>> <mailto:[email protected]> <mailto:
>>>>>>>>>>>> [email protected] <mailto:[email protected]>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Dear Clerezza Developers
>>>>>>>>>>>>
>>>>>>>>>>>> Clerezza PMC is currently looking for new committers to help
>>>>>>>>>>>>
>>>>>>>>>>> developing
>>>>>>>>>>
>>>>>>>>>>> and
>>>>>>>>>>>
>>>>>>>>>>>> improving Apache Clerezza.
>>>>>>>>>>>>
>>>>>>>>>>>> Apache Clerezza allows to easily develop semantic web
>> application
>>>> by
>>>>>>>>>>>> providing the following:
>>>>>>>>>>>> - An API to access RDF Graphs
>>>>>>>>>>>> - SPARQL Support
>>>>>>>>>>>> - Support of JAX-RS
>>>>>>>>>>>>
>>>>>>>>>>>> If you or your colleagues are interested in being a Clerezza
>>>>>>>>>>>>
>>>>>>>>>>> committer,
>>>>>>>>>>
>>>>>>>>>>> please don't hesitate to contact us through this list.
>>>>>>>>>>>> You may and are encouraged to forward this email to the
>> mailing
>>>> lists
>>>>>>>>>>>>
>>>>>>>>>>> you
>>>>>>>>>>
>>>>>>>>>>> are involved in.
>>>>>>>>>>>>
>>>>>>>>>>>> Best regards
>>>>>>>>>>>>
>>>>>>>>>>>> Hasan
>>>>>>>>>>>> On behalf of Clerezza PMC
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>>
>>>
