Dear Commons community,
the discussion has been very productive. Thanks so much for all your
valuable feedback.
But I let myself go for passion, so we went beyond my initial goals for
the discussion. I think the project still needs some more time to decide
whether to go, if Commons is the ri
2014-07-23 1:35 GMT+02:00 Peter Ansell :
> On 22 July 2014 22:17, Gary Gregory wrote:
> > I just saw my name pop up here: Yes we will help from infra with JIRA and
> > using Git is fine as long as it is hosted at Apache and not GitHub. We
> > still have to use Subversion for publishing the site a
On 22 July 2014 22:17, Gary Gregory wrote:
> I just saw my name pop up here: Yes we will help from infra with JIRA and
> using Git is fine as long as it is hosted at Apache and not GitHub. We
> still have to use Subversion for publishing the site and the release files
> of course, this is an Apach
I just saw my name pop up here: Yes we will help from infra with JIRA and
using Git is fine as long as it is hosted at Apache and not GitHub. We
still have to use Subversion for publishing the site and the release files
of course, this is an Apache-wide procedure.
Gary
On Tue, Jul 22, 2014 at 2:
2014-07-22 9:05 GMT+02:00 Sergio Fernández :
>
>
> On 22/07/14 08:55, Peter Ansell wrote:
>
>> On 22 July 2014 16:30, Benedikt Ritter wrote:
>> All of the code contributions have been from Peter Ansell, Andy
>> Seabourne and Sergio Fernández, per the GitHub contributors list, and
>> we all are Ap
On 22/07/14 08:55, Peter Ansell wrote:
On 22 July 2014 16:30, Benedikt Ritter wrote:
All of the code contributions have been from Peter Ansell, Andy
Seabourne and Sergio Fernández, per the GitHub contributors list, and
we all are Apache committers already, in case that helps:
https://github.c
On 22 July 2014 16:30, Benedikt Ritter wrote:
> 2014-07-21 19:44 GMT+02:00 Sergio Fernández :
>
>> Hi,
>>
>>
>> On 21/07/14 17:33, Benedikt Ritter wrote:
>> >
>>
>>> 2014-07-21 16:55 GMT+02:00 Phil Steitz :
>>>
>> >>
>>
>>> On 7/21/14, 5:11 AM, Sergio Fernández wrote:
>>> >>>
>>
>>> Sorry, I
Hi,
On 22/07/14 08:30, Benedikt Ritter wrote:
2014-07-21 19:44 GMT+02:00 Sergio Fernández :
I created SANDBOX-479 with that purpose. It is rather easy, but you are
right that the process needs to be properly managed.
I've looked at the github repo again. I think we all agree that future
disc
2014-07-21 19:44 GMT+02:00 Sergio Fernández :
> Hi,
>
>
> On 21/07/14 17:33, Benedikt Ritter wrote:
> >
>
>> 2014-07-21 16:55 GMT+02:00 Phil Steitz :
>>
> >>
>
>> On 7/21/14, 5:11 AM, Sergio Fernández wrote:
>>>
>> >>>
>
>> Sorry, I tried to find it, but in the web site there is no
informatio
On 21 July 2014 22:14, Sergio Fernández wrote:
> Hi Emmanuel,
>
> On 21/07/14 14:05, Emmanuel Bourg wrote:
>>
>> If I understand well this is a kind of specification API? The actual
>> implementations will be done in Jena/Marmotta/OpenRDF?
>
>
> With the current scope yes, that the overall idea. B
Hi,
On 21/07/14 17:33, Benedikt Ritter wrote:
>
2014-07-21 16:55 GMT+02:00 Phil Steitz :
>>
On 7/21/14, 5:11 AM, Sergio Fernández wrote:
>>>
Sorry, I tried to find it, but in the web site there is no
information about such procedure. Do we need to start a vote and
get a consensus from the Co
On 7/21/14, 8:33 AM, Benedikt Ritter wrote:
> 2014-07-21 16:55 GMT+02:00 Phil Steitz :
>
>> On 7/21/14, 5:11 AM, Sergio Fernández wrote:
>>> Hi Benedikt,
>>>
>>> On 21/07/14 13:12, Benedikt Ritter wrote:
first of all, welcome the Apache Commons dev mailing list. It's
nice to
hear tha
2014-07-21 16:55 GMT+02:00 Phil Steitz :
> On 7/21/14, 5:11 AM, Sergio Fernández wrote:
> > Hi Benedikt,
> >
> > On 21/07/14 13:12, Benedikt Ritter wrote:
> >> first of all, welcome the Apache Commons dev mailing list. It's
> >> nice to
> >> hear that you have decided to share code with others usi
On 7/21/14, 5:11 AM, Sergio Fernández wrote:
> Hi Benedikt,
>
> On 21/07/14 13:12, Benedikt Ritter wrote:
>> first of all, welcome the Apache Commons dev mailing list. It's
>> nice to
>> hear that you have decided to share code with others using the
>> Apache
>> Commons project.
>
> Consider this c
On 21/07/14 13:05, Emmanuel Bourg wrote:
Hi Sergio,
If I understand well this is a kind of specification API? The actual
implementations will be done in Jena/Marmotta/OpenRDF?
Emmanuel Bourg
While, as I understand it, OpenRDF [*] is adopting the interface natively,
It does not look any any
On 21/07/14 12:12, Benedikt Ritter wrote:
About the commons-rdf code itself: I only took a very brief look. As far as
I understand this is only supposed to be an API, hence there are no
implementation classes, right? One thing that caught my eye is
BlankNoreOrIRI... Is this defined as such in the
Hi Emmanuel,
On 21/07/14 14:05, Emmanuel Bourg wrote:
If I understand well this is a kind of specification API? The actual
implementations will be done in Jena/Marmotta/OpenRDF?
With the current scope yes, that the overall idea. But we do not discard
to include some actual code in the future
Hi Benedikt,
On 21/07/14 13:12, Benedikt Ritter wrote:
first of all, welcome the Apache Commons dev mailing list. It's nice to
hear that you have decided to share code with others using the Apache
Commons project.
Consider this contribution our (Andy, Peter and mine) two cents to such
importa
Hi Sergio,
If I understand well this is a kind of specification API? The actual
implementations will be done in Jena/Marmotta/OpenRDF?
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional c
Hello Sergio,
first of all, welcome the Apache Commons dev mailing list. It's nice to
hear that you have decided to share code with others using the Apache
Commons project.
In the past we had the policy, that the commons sandbox is free for all ASF
committers. So you could have started coding at
Dear Commons community,
I'd like to start a discussion about incubating a new commons component
we have been developing in the last weeks at github: commons-rdf [1].
RDF (Resource Description Framework [2]) is a W3C framework for
representing information in the Web. The core structure of the
21 matches
Mail list logo
