[INFO] Graduation in progress: the podling is leaving the nest!

[Jakob Frank]

Hi all,

in their last meeting, the ASF board has decided to establish Apache
Marmotta as a new Top-Level Project!

INFRA-7026 [1] is tracking the process of migration, so please commit
(and push) your outstanding changes ASAP!
This is important for the stuff in SVN [2], with git it should be easy
to update the remote url.

Best,
Jakob

[1] https://issues.apache.org/jira/browse/INFRA-7026
[2] https://svn.apache.org/repos/asf/incubator/marmotta

Re: [Fwd: ASF Board Meeting Summary - November 20, 2013]

[Jakob Frank]

"the podling is leaving the nest"

Best,
Jakob

On 21 November 2013 00:19, Sergio Fernández
 wrote:
> On 20/11/13 23:46, Sebastian Schaffert wrote:
>>
>> We managed! ;-)
>
>
> Cool!
> Thanks to all people who have contributed to this :-)
>
> --
> Sergio Fernández
> Senior Researcher
> Knowledge and Media Technologies
> Salzburg Research Forschungsgesellschaft mbH
> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> T: +43 662 2288 318 | M: +43 660 2747 925
> sergio.fernan...@salzburgresearch.at
> http://www.salzburgresearch.at

Re: Hello

[Jakob Frank]

Hi Oliver,

nice to meet you (again, this time officially on the Apache Marmotta
mailinglist)!

Getting write access to the repositories requires karma which can be
earned by contributing to the project before, both in therms of
bug-reports, design work, writing documentation and of course code
patches. [1,2]

I'm sure the rest of the dev-team is curious to see your proposed
redesign, maybe you can share them with us?
You could either post your patch to this list - or maybe it is easier
if you provide a few screenshots of your redesign so we can discuss
them here.

Best,
Jakob

[1] http://marmotta.incubator.apache.org/development.html
[2] http://www.apache.org/foundation/how-it-works.html#meritocracy

On 18 November 2013 11:41, Oliver Janner
 wrote:
> I'm a new member of the KMT team of Salzburg Research.
>
> I've been working on a redesign of the Apache Marmotta homepage previously
> and would like to commit my changes.
>
> --
> Oliver Janner
> User Interface Design @ KMT
>
> Salzburg Research Forschungsgesellschaft mbH
> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> T: +43.662.2288-249
> oliver.jan...@salzburgresearch.at
> http://www.salzburgresearch.at
>

[jira] [Created] (MARMOTTA-363) rename module kiwi-contextaware to sesame-contextaware

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-363:


 Summary: rename module kiwi-contextaware to sesame-contextaware
 Key: MARMOTTA-363
 URL: https://issues.apache.org/jira/browse/MARMOTTA-363
 Project: Marmotta
  Issue Type: Task
  Components: KiWi Triple Store, Sesame Tools
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
 Fix For: 3.2


kiwi-contextaware is part of the kiwi library, but is in fact not at all kiwi 
specific, so it should move to the sesame-tools.




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (MARMOTTA-364) kiwi-contextaware should allow multiple 'read' contexts.

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-364:


 Summary: kiwi-contextaware should allow multiple 'read' contexts.
 Key: MARMOTTA-364
 URL: https://issues.apache.org/jira/browse/MARMOTTA-364
 Project: Marmotta
  Issue Type: Improvement
  Components: KiWi Triple Store, Sesame Tools
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
 Fix For: 3.2


currently, kiwi-contextaware restricts a sail to a fixed context. It would be 
useful to
# allow to restrict to more than one context
# allow to restrict to one _write_ and multiple _read_ contexts




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (MARMOTTA-362) Versions are not listed on the webpage

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-362:


 Summary: Versions are not listed on the webpage
 Key: MARMOTTA-362
 URL: https://issues.apache.org/jira/browse/MARMOTTA-362
 Project: Marmotta
  Issue Type: Bug
  Components: Website
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sergio Fernández


http://marmotta.incubator.apache.org/development.html#Versions should list the 
available versions of marmotta.

This was done via javascript querying the JIRA API.

In JIRA 6, jsonp support was removed, thus the request now fails because of 
missing CORS settings.

https://developer.atlassian.com/display/JIRADEV/Preparing+for+JIRA+6.0#PreparingforJIRA6.0-JSON-Pnolongersupported




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (MARMOTTA-361) Check javadoc style on the website

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-361:


 Summary: Check javadoc style on the website
 Key: MARMOTTA-361
 URL: https://issues.apache.org/jira/browse/MARMOTTA-361
 Project: Marmotta
  Issue Type: Task
  Components: Website
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sergio Fernández


Because of INFRA-6837, the javadoc is not published in the marmotta website.

The style of the javadoc needs to be adapted to the website styling.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

kiwi-contextaware

[Jakob Frank]

Hi all,

I'm currently (again) working on the website and stumbled upon the
Contextual Sail Wrapper (module kiwi-contextaware in libraries/kiwi/)

>From what I see in the code, this module could (should?) be moved to
the sesame-tools, as it is not kiwi-specific.

WDYT?

Best,
Jakob

Fwd: [RESULT][VOTE] Graduate Apache Marmotta as TLP

[Jakob Frank]

We're on track to to graduation!

Best,
Jakob

-- Forwarded message --
From: Jakob Frank 
Date: 8 November 2013 09:10
Subject: [RESULT][VOTE] Graduate Apache Marmotta as TLP
To: gene...@incubator.apache.org

Hi all,

after more than 72hrs the vote about graduating the Marmotta podling as
a TLP passes with 9 +1s, 8 of those from IPMC members:

Bertrand Delacretaz (IPMC)
Andy Seaborne (IPMC, Marmotta Champion)
Fabian Christ (IPMC, Marmotta Mentor)
Alexei Fedotov
Nandana Mihindukulasooriya (IPMC, Marmotta Mentor)
Alan D. Cabrera (IPMC)
Suresh Marru (IPMC)
Marvin Humphrey (IPMC)
Jake Farrell (IPMC)

There were no +0/-1s.

Thank you all for voting!

I'll proceed by sending the Resolution to board@a.o

Best,
Jakob

On Mon, 2013-11-04 at 09:59 +0100, Jakob Frank wrote:
> Hi all,
>
> the Marmotta podling, whose goal is to provide an Open Platform for
> Linked Data, entered incubation in December 2012. Since then, the
> codebase has stabilized and two releases were published following ASF
> policies and guidelines.
> The community has grown, two new committers have joined the development
> team and more people joined the mailing lists.
>
> The last incubator report lists Marmotta as "Ready to graduate" [1], the
> Marmotta community has decided to take this step [2] and agreed on a
> Graduation Resolution Draft [3] which is also attached below.
>
> The resolution draft was posted to general@incubator.a.o for discussion
> [4] and raised no concerns, now please cast your votes:
>
> [ ]  +1 Graduate the Marmotta podling from Incubator
> [ ]  +0 Indifferent to graduation status of the Marmotta podling
> [ ]  -1 Reject graduation of the Marmotta podling from Incubator because...
>
> The vote will be open for at least 72 hours starting now.
>
>
> Best,
> Jakob
> on behalf of the Marmotta community
>
> [1] <http://s.apache.org/marmotta-graduation-vote>
> [2] <http://s.apache.org/marmotta-graduation-result>
> [3] <http://s.apache.org/marmotta-graduation-resolution>
> [4] <http://s.apache.org/dYt>
>
> Apache Marmotta Graduation Resolution
> =
>
> X. Establish the Apache Marmotta Project
>
>WHEREAS, the Board of Directors deems it to be in the best
>interests of the Foundation and consistent with the
>Foundation's purpose to establish a Project Management
>Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to
>the public, related to an open platform for Linked Data.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Marmotta Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Marmotta Project be and hereby is
>responsible for the creation and maintenance of software
>related to an open platform for Linked Data;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache Marmotta" be
>and hereby is created, the person holding such office to
>serve at the direction of the Board of Directors as the chair
>of the Apache Marmotta Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Marmotta Project; and be it further
>
>RESOLVED, that the persons listed immediately below be and
>    hereby are appointed to serve as the initial members of the
>Apache Marmotta Project:
>
>  * Peter Ansell 
>  * Fabian Christ   
>  * Sergio Fernández 
>  * Jakob Frank   
>  * Dietmar Glachs  
>  * Thomas Kurz   
>  * Nandana Mihindukulasooriya  
>  * Raffaele Palmieri 
>  * Sebastian Schaffert  
>  * Rupert Westenthaler 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank
>be appointed to the office of Vice President, Apache Marmotta, to
>serve in accordance with and subject to the direction of the
>Board of Directors and the Bylaws of the Foundation until
>death, resignation, retirement, removal or disqualification,
>or until a successor is appointed; and be it further
>
>RESOLVED, that the Apache Marmotta Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Marmotta podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Marmotta podling encumbered upon the Apache Incubator
>Project are hereafter discharged.
>
>
>


signature.asc
Description: PGP signature

Re: Accidently merged into "master"

[Jakob Frank]

With help from infra [1] I was able to revert the erroneous merge:

This is what I did:
git revert --no-commit --no-edit -s 4aa87db
git revert --no-commit --no-edit -s a9bf7e4 -m 1
git revert --no-commit --no-edit -s be31f8a
git revert --no-commit --no-edit -s 4b8b868
git revert --no-commit --no-edit -s c576351
git commit -s
git push origin master

Best,
Jakob

[1] http://s.apache.org/pRO

On 16 October 2013 10:02, Jakob Frank  wrote:
> Easiest way would be to do a --hard reset of the master, but that's
> not allowed in the ASF Repo (at least for branch master)
> Also deleting the remote branch and re-pushing it is not allowed.
>
> So I filed an issue with Infra [1]
>
> Best,
> Jakob
>
> [1] https://issues.apache.org/jira/browse/INFRA-6876
>
> On 1 October 2013 02:13, Peter Ansell  wrote:
>> That didn't reset to the right commit because there were commits since
>> cdb3223d that need to be kept ... I will look into it some more. Part
>> of the complexity seems to be that git can't easily revert merges and
>> other commits simultaneously so it may need two reverts (and then a
>> squash to make it look like a single revert before pushing)
>>
>> Peter
>>
>> On 1 October 2013 09:51, Peter Ansell  wrote:
>>> Fixed.
>>>
>>> For reference, the command I used was the following, where the SHA1
>>> hash is the merge commit, and I needed to use -m 2 because it was a
>>> merge, and specifically "2" because of the direction the merge was
>>> done in (-m 1 would have retained the other tree of commits):
>>>
>>> git revert -m 2 a9bf7e4fa56f00e26e09a5fae002686eb65631df
>>>
>>> You can see the comparison at the following URL on GitHub, which for
>>> me is completely empty, as desired.
>>>
>>> https://github.com/ansell/incubator-marmotta/compare/apache:cdb3223db7439a9f8fd7fb5159ffd52f6da0ecb7...4aa87dbe5c121476176292416e36e71f613be83e?expand=1#files_bucket
>>>
>>> Cheers,
>>>
>>> Peter
>>>
>>> On 1 October 2013 07:55, Peter Ansell  wrote:
>>>> I think you need to push a revert commit for the master branch.
>>>>
>>>> --
>>>> Peter
>>>>
>>>> On 01/10/2013, at 3:31 AM, Sebastian Schaffert 
>>>>  wrote:
>>>>
>>>>> Sorry, I don't manage (Apache does not allow forcing reverting a version).
>>>>> Maybe someone who already did this can help me tomorrow ...
>>>>>
>>>>> Greetings,
>>>>>
>>>>> Sebastian
>>>>>
>>>>>
>>>>> 2013/9/30 Sebastian Schaffert 
>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> while working on MARMOTTA-324, I accidently merged back and pushed my
>>>>>> branch into master instead of develop. I'll try to revert this change as
>>>>>> soon as possible, sorry.
>>>>>>
>>>>>> Greetings,
>>>>>>
>>>>>> Sebastian
>>>>>>

Fwd: [VOTE] Graduate Apache Marmotta as TLP

[Jakob Frank]

FYI

"No more Mickey Mouse", we are heading for graduation!

Best,
Jakob

-- Forwarded message ------
From: Jakob Frank 
Date: 4 November 2013 09:59
Subject: [VOTE] Graduate Apache Marmotta as TLP
To: gene...@incubator.apache.org

Hi all,

the Marmotta podling, whose goal is to provide an Open Platform for
Linked Data, entered incubation in December 2012. Since then, the
codebase has stabilized and two releases were published following ASF
policies and guidelines.
The community has grown, two new committers have joined the development
team and more people joined the mailing lists.

The last incubator report lists Marmotta as "Ready to graduate" [1], the
Marmotta community has decided to take this step [2] and agreed on a
Graduation Resolution Draft [3] which is also attached below.

The resolution draft was posted to general@incubator.a.o for discussion
[4] and raised no concerns, now please cast your votes:

[ ]  +1 Graduate the Marmotta podling from Incubator
[ ]  +0 Indifferent to graduation status of the Marmotta podling
[ ]  -1 Reject graduation of the Marmotta podling from Incubator because...

The vote will be open for at least 72 hours starting now.


Best,
Jakob
on behalf of the Marmotta community

[1] <http://s.apache.org/marmotta-graduation-vote>
[2] <http://s.apache.org/marmotta-graduation-result>
[3] <http://s.apache.org/marmotta-graduation-resolution>
[4] <http://s.apache.org/dYt>

Apache Marmotta Graduation Resolution
=

X. Establish the Apache Marmotta Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to an open platform for Linked Data.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache Marmotta Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Marmotta Project be and hereby is
   responsible for the creation and maintenance of software
   related to an open platform for Linked Data;
   and be it further

   RESOLVED, that the office of "Vice President, Apache Marmotta" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache Marmotta Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Marmotta Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Marmotta Project:

 * Peter Ansell 
 * Fabian Christ       
 * Sergio Fernández 
 * Jakob Frank   
 * Dietmar Glachs  
 * Thomas Kurz   
 * Nandana Mihindukulasooriya  
 * Raffaele Palmieri 
 * Sebastian Schaffert  
 * Rupert Westenthaler     

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank
   be appointed to the office of Vice President, Apache Marmotta, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the Apache Marmotta Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Marmotta podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Marmotta podling encumbered upon the Apache Incubator
   Project are hereafter discharged.


signature.asc
Description: PGP signature

Re: branching workflow

[Jakob Frank]

On 31 Oct 2013 09:36, "Sergio Fernández" <
sergio.fernan...@salzburgresearch.at> wrote:
>
> what we are misunderstanding here in the concept of "stable code".
Besides the wrong merge Sebastian did (see INFRA-6876), we are considering
only releases as stable code. And I thing we should do that more often. The
criteria would need to be discussed, but could be something as simple as
"periodically, if jenkins' builds are stable, all tests passing and no
critical/blocking issues open, we could merge develop into master". This
could be done by any committer, a special person, or even the release
manager, I don't know.
I would prefer an automatic approach, e.g. after a stable Jenkins build
(all tests passing).
I see two issues with that: first, the apache Jenkins is not really stable
itself and second, we are missing postgres and mysql databases for testing
there.

But for a start, we could try to manually merge back to master once a week
(iff all tests pass, including postgres and mysql)

What is important: the version on master MUST be working! It is the first
impression someone will have when checking out the code.

Best
Jakob

[jira] [Resolved] (MARMOTTA-223) add ldpath function to resolve HTML/XML entities

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-223.
--

   Resolution: Fixed
Fix Version/s: 3.2

> add ldpath function to resolve HTML/XML entities
> 
>
> Key: MARMOTTA-223
> URL: https://issues.apache.org/jira/browse/MARMOTTA-223
> Project: Marmotta
>  Issue Type: New Feature
>  Components: LDPath
>Reporter: Sebastian Schaffert
>    Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.2
>
>   Original Estimate: 4h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Content selected by LDPath often contains HTML or XML data. We already 
> support stripping out tags, but entities are still not resolved. We should 
> offer an LDPath function for this.
> (from https://code.google.com/p/lmf/issues/detail?id=143)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (MARMOTTA-343) Prepare graduation

[Jakob Frank (JIRA)]

[ 
https://issues.apache.org/jira/browse/MARMOTTA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810175#comment-13810175
 ] 

Jakob Frank commented on MARMOTTA-343:
--

What happened so far:
* Marmotta community decided to go towards graduation 
[[vote|http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201310.mbox/%3C5260D935.9090709%40apache.org%3E]]
* Marmotta community agreed on a Graduation Resolution 
[[vote|http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201310.mbox/%3C1382947773.2712.12.camel%40kis07%3E]]
* Graduation Resolution is discussed on general@incubator.i.a.o 
[[thread|http://mail-archives.apache.org/mod_mbox/incubator-general/201310.mbox/%3C1383049827.2712.16.camel%40kis07%3E]]
  

> Prepare graduation
> --
>
> Key: MARMOTTA-343
> URL: https://issues.apache.org/jira/browse/MARMOTTA-343
> Project: Marmotta
>  Issue Type: Task
>Reporter: Sergio Fernández
>Assignee: Sergio Fernández
>
> Meta-task to track the graduation process, starting from: 
> http://markmail.org/message/jkpj6hcfnhylqsog



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-348) cleanup managed dependencies in parent-pom

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-348.
--

Resolution: Fixed

removed fi.tikesos:rdfa-core and org.quartz-scheduler:quartz

> cleanup managed dependencies in parent-pom
> --
>
> Key: MARMOTTA-348
> URL: https://issues.apache.org/jira/browse/MARMOTTA-348
> Project: Marmotta
>  Issue Type: Bug
>  Components: Build Environment
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.1.1, 3.2
>
>
> e.g. remove
> {code}
> 
> fi.tikesos
> rdfa-core
> 0.0.8
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: [RESULT][VOTE] Apache Marmotta Graduation Resolution

[Jakob Frank]

On 28 October 2013 09:09, Jakob Frank  wrote:
> Mentors: Please present the resolution draft to general@incubator.a.o
Sergio just pointed out to me that we can move the resolution to
general@incubator.a.o ourselves - it a mentor-task only when
graduation as a sub-project - my bad.

I'll send out the mail to general@ soon.

Best,
Jakob

[jira] [Resolved] (MARMOTTA-347) site-build fails because of the marmotta-reactor being not deployed

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-347.
--

Resolution: Fixed
  Assignee: Jakob Frank  (was: Sebastian Schaffert)

> site-build fails because of the marmotta-reactor being not deployed
> ---
>
> Key: MARMOTTA-347
> URL: https://issues.apache.org/jira/browse/MARMOTTA-347
> Project: Marmotta
>  Issue Type: Bug
>  Components: Build Environment, Website
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Critical
>  Labels: cms
> Fix For: 3.2
>
>
> So either we remove the dependency to marmotta-reactor from marmotta-site or 
> we also deploy the marmotta-reactor (pom).
> http://ci.apache.org/builders/marmotta-site-staging/builds/144



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (MARMOTTA-348) cleanup managed dependencies in parent-pom

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-348:


 Summary: cleanup managed dependencies in parent-pom
 Key: MARMOTTA-348
 URL: https://issues.apache.org/jira/browse/MARMOTTA-348
 Project: Marmotta
  Issue Type: Bug
  Components: Build Environment
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
 Fix For: 3.2


e.g. remove
{code}

fi.tikesos
rdfa-core
0.0.8

{code}




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (MARMOTTA-347) site-build fails because of the marmotta-reactor being not deployed

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-347:


 Summary: site-build fails because of the marmotta-reactor being 
not deployed
 Key: MARMOTTA-347
 URL: https://issues.apache.org/jira/browse/MARMOTTA-347
 Project: Marmotta
  Issue Type: Bug
  Components: Build Environment, Website
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
Priority: Critical
 Fix For: 3.2


So either we remove the dependency to marmotta-reactor from marmotta-site or we 
also deploy the marmotta-reactor (pom).

http://ci.apache.org/builders/marmotta-site-staging/builds/144



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[RESULT][VOTE] Apache Marmotta Graduation Resolution

[Jakob Frank]

Hi all,

the final draft of the Graduation Resolution was accepted by the
Marmotta Community:

9 +1s:
Sergio Fernandez
Jakob Frank
Rupert Westenthaler
Sebastian Schaffert
Andy Seaborne
Thomas Kurz
Raffaele Palmieri
Dietmar Glachs
Nandana Mihindukulasooriya

No -1s.

Thank you all for voting!

Mentors: Please present the resolution draft to general@incubator.a.o

Best,
Jakob


On 24 October 2013 10:28, Jakob Frank  wrote:
> Hi all,
>
> this is a VOTE on the final draft of the Graduation Resolution which
> will VOTEd on general@i.a.o and then send to board@a.o to be included
> in the agenda of the November meeting.
>
> The full text of the resolution is attached below, and also available
> in the svn [1]
>
> Please cast your vote:
> [ ] +1  I accept and support the Graduation Resolution.
> [ ] -1  I don't accept the Graduation Resolution because...
>
> The vote will be open for at least 72 hours and passes if a majority
> of at least 3 +1s are cast.
>
> Best,
> Jakob
>
> [1] 
> https://svn.apache.org/viewvc/incubator/marmotta/graduation/resolution.txt?revision=1535293
>
> Apache Marmotta Graduation Resolution
> =
>
> X. Establish the Apache Marmotta Project
>
>WHEREAS, the Board of Directors deems it to be in the best
>interests of the Foundation and consistent with the
>Foundation's purpose to establish a Project Management
>Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to
>the public, related to an open platform for Linked Data.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Marmotta Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Marmotta Project be and hereby is
>responsible for the creation and maintenance of software
>related to an open platform for Linked Data;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache Marmotta" be
>and hereby is created, the person holding such office to
>serve at the direction of the Board of Directors as the chair
>of the Apache Marmotta Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Marmotta Project; and be it further
>
>RESOLVED, that the persons listed immediately below be and
>hereby are appointed to serve as the initial members of the
>    Apache Marmotta Project:
>
>  * Peter Ansell 
>  * Fabian Christ   
>  * Sergio Fernández 
>  * Jakob Frank   
>  * Dietmar Glachs  
>  * Thomas Kurz   
>  * Nandana Mihindukulasooriya  
>  * Raffaele Palmieri 
>  * Sebastian Schaffert  
>  * Rupert Westenthaler 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank
>be appointed to the office of Vice President, Apache Marmotta, to
>serve in accordance with and subject to the direction of the
>Board of Directors and the Bylaws of the Foundation until
>death, resignation, retirement, removal or disqualification,
>or until a successor is appointed; and be it further
>
>RESOLVED, that the Apache Marmotta Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Marmotta podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Marmotta podling encumbered upon the Apache Incubator
>Project are hereafter discharged.



signature.asc
Description: This is a digitally signed message part

[jira] [Resolved] (MARMOTTA-344) Backport KiWiLoader to 3.1 and 3.0

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-344.
--

   Resolution: Fixed
Fix Version/s: 3.1.1
   3.0.1
 Assignee: Jakob Frank  (was: Sebastian Schaffert)

backported

> Backport KiWiLoader to 3.1 and 3.0
> --
>
> Key: MARMOTTA-344
> URL: https://issues.apache.org/jira/browse/MARMOTTA-344
> Project: Marmotta
>  Issue Type: Improvement
>  Components: Triple Store
>    Reporter: Jakob Frank
>    Assignee: Jakob Frank
> Fix For: 3.0.1, 3.1.1
>
>
> KiWiLoader significantly improves the performance for bigger data imports, 
> thus should be available also for the 3.0 and 3.1 versions.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-314) getGraph is returning wrong datatype

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-314.
--

Resolution: Fixed

> getGraph is returning wrong datatype
> 
>
> Key: MARMOTTA-314
> URL: https://issues.apache.org/jira/browse/MARMOTTA-314
> Project: Marmotta
>  Issue Type: Bug
>  Components: LDPath
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>  Labels: api-change
> Fix For: 3.2
>
>   Original Estimate: 4h
>  Time Spent: 1h
>  Remaining Estimate: 3h
>
> The graph keyword in ldpath expects a list of URIs to limit the evaluation of 
> the program to a (set of) named graph(s)/context(s).
> currently getGraph function of an LDPath Program is returning a Set; 
> Set would be better.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-342) Document the new KiWi Loader

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-342.
--

Resolution: Done

documented in the wiki

> Document the new KiWi Loader
> 
>
> Key: MARMOTTA-342
> URL: https://issues.apache.org/jira/browse/MARMOTTA-342
> Project: Marmotta
>  Issue Type: Sub-task
>  Components: Triple Store
>Affects Versions: 3.1-incubating
>Reporter: Sergio Fernández
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.2
>
>
> Would be nice to have some documentation about such cool feature!
> The wiki could be the right place for it: 
> https://wiki.apache.org/marmotta/ImportData



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-345) Refactor the local file import

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-345.
--

   Resolution: Done
Fix Version/s: 3.2
 Assignee: Jakob Frank  (was: Sebastian Schaffert)

refactored and cleaned up.

marmotta-commons now has a WatcherService that can be used for other similar 
tasks.

> Refactor the local file import
> --
>
> Key: MARMOTTA-345
> URL: https://issues.apache.org/jira/browse/MARMOTTA-345
> Project: Marmotta
>  Issue Type: Task
>  Components: Platform
>Affects Versions: 3.2
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.2
>
>
> The local file-import was a quick proof of concept implementation and should 
> be restructured.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-295) Already existed files are not imported at boot time

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-295.
--

Resolution: Fixed
  Assignee: Jakob Frank  (was: Sergio Fernández)

fixed together with MARMOTTA-345

> Already existed files are not imported at boot time
> ---
>
> Key: MARMOTTA-295
> URL: https://issues.apache.org/jira/browse/MARMOTTA-295
> Project: Marmotta
>  Issue Type: Bug
>  Components: Platform
>Affects Versions: 3.1-incubating
>Reporter: Sergio Fernández
>Assignee: Jakob Frank
> Fix For: 3.2
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> For the same reason than MARMOTTA-294, files already there when the platform 
> boots are not imported into Marmotta.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-296) Support compressed files in the local import

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-296.
--

Resolution: Implemented
  Assignee: Jakob Frank  (was: Sergio Fernández)

Implemented: can handle gzip and bz2

> Support compressed files in the local import
> 
>
> Key: MARMOTTA-296
> URL: https://issues.apache.org/jira/browse/MARMOTTA-296
> Project: Marmotta
>  Issue Type: Improvement
>  Components: Platform
>Affects Versions: 3.1-incubating
>Reporter: Sergio Fernández
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.2
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Jakob suggests to add support to compressed files (zip, gz and so on), which 
> should not be so difficult.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-294) Already existed directories are not registered at boot time

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-294.
--

Resolution: Fixed
  Assignee: Jakob Frank  (was: Sergio Fernández)

fixed during MARMOTTA-345

> Already existed directories are not registered at boot time
> ---
>
> Key: MARMOTTA-294
> URL: https://issues.apache.org/jira/browse/MARMOTTA-294
> Project: Marmotta
>  Issue Type: Bug
>  Components: Platform
>Affects Versions: 3.1-incubating
>Reporter: Sergio Fernández
>Assignee: Jakob Frank
> Fix For: 3.2
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The current implementation of the local import sub-directories (MARMOTTA-291) 
> is only triggered when new ones are created. Therefore, those directories 
> already there when the platform boots are not correctly registered in the 
> watch process; so files copied there are not handled either.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: [VOTE] Apache Marmotta Graduation Resolution

[Jakob Frank]

And here's my
+1

Best,
Jakob

On 24 October 2013 10:28, Jakob Frank  wrote:
> Hi all,
>
> this is a VOTE on the final draft of the Graduation Resolution which
> will VOTEd on general@i.a.o and then send to board@a.o to be included
> in the agenda of the November meeting.
>
> The full text of the resolution is attached below, and also available
> in the svn [1]
>
> Please cast your vote:
> [ ] +1  I accept and support the Graduation Resolution.
> [ ] -1  I don't accept the Graduation Resolution because...
>
> The vote will be open for at least 72 hours and passes if a majority
> of at least 3 +1s are cast.
>
> Best,
> Jakob
>
> [1] 
> https://svn.apache.org/viewvc/incubator/marmotta/graduation/resolution.txt?revision=1535293
>
> Apache Marmotta Graduation Resolution
> =
>
> X. Establish the Apache Marmotta Project
>
>WHEREAS, the Board of Directors deems it to be in the best
>interests of the Foundation and consistent with the
>Foundation's purpose to establish a Project Management
>Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to
>the public, related to an open platform for Linked Data.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Marmotta Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Marmotta Project be and hereby is
>responsible for the creation and maintenance of software
>related to an open platform for Linked Data;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache Marmotta" be
>and hereby is created, the person holding such office to
>serve at the direction of the Board of Directors as the chair
>of the Apache Marmotta Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Marmotta Project; and be it further
>
>RESOLVED, that the persons listed immediately below be and
>hereby are appointed to serve as the initial members of the
>    Apache Marmotta Project:
>
>  * Peter Ansell 
>  * Fabian Christ   
>  * Sergio Fernández 
>  * Jakob Frank   
>  * Dietmar Glachs  
>  * Thomas Kurz   
>  * Nandana Mihindukulasooriya  
>  * Raffaele Palmieri 
>  * Sebastian Schaffert  
>  * Rupert Westenthaler 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank
>be appointed to the office of Vice President, Apache Marmotta, to
>serve in accordance with and subject to the direction of the
>Board of Directors and the Bylaws of the Foundation until
>death, resignation, retirement, removal or disqualification,
>or until a successor is appointed; and be it further
>
>RESOLVED, that the Apache Marmotta Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Marmotta podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Marmotta podling encumbered upon the Apache Incubator
>Project are hereafter discharged.

[VOTE] Apache Marmotta Graduation Resolution

[Jakob Frank]

Hi all,

this is a VOTE on the final draft of the Graduation Resolution which
will VOTEd on general@i.a.o and then send to board@a.o to be included
in the agenda of the November meeting.

The full text of the resolution is attached below, and also available
in the svn [1]

Please cast your vote:
[ ] +1  I accept and support the Graduation Resolution.
[ ] -1  I don't accept the Graduation Resolution because...

The vote will be open for at least 72 hours and passes if a majority
of at least 3 +1s are cast.

Best,
Jakob

[1] 
https://svn.apache.org/viewvc/incubator/marmotta/graduation/resolution.txt?revision=1535293

Apache Marmotta Graduation Resolution
=

X. Establish the Apache Marmotta Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to an open platform for Linked Data.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache Marmotta Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Marmotta Project be and hereby is
   responsible for the creation and maintenance of software
   related to an open platform for Linked Data;
   and be it further

   RESOLVED, that the office of "Vice President, Apache Marmotta" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache Marmotta Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Marmotta Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Marmotta Project:

 * Peter Ansell 
 * Fabian Christ   
 * Sergio Fernández     
 * Jakob Frank   
 * Dietmar Glachs  
 * Thomas Kurz   
 * Nandana Mihindukulasooriya  
 * Raffaele Palmieri 
 * Sebastian Schaffert  
 * Rupert Westenthaler 

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank
   be appointed to the office of Vice President, Apache Marmotta, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the Apache Marmotta Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Marmotta podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Marmotta podling encumbered upon the Apache Incubator
   Project are hereafter discharged.

Re: [DISCUSS] Apache Marmotta Graduation Resolution

[Jakob Frank]

Since no other voices were raised, Sergio and me decided on the
initial PMC Chair for Marmotta: It will be me.

I'll send out the VOTE on the final resolution draft in a moment.

Best,
Jakob

On 23 October 2013 22:29, Fabian Christ  wrote:
> Hi,
>
> 2013/10/22 Jakob Frank :
>> I'd like to see more discussion about the whole draft! At least some 
>> comment...
>
> I think it is just fine as it is so far ;)
>
> Best,
>  - Fabian
>
>
> --
> Fabian
> http://twitter.com/fctwitt

[jira] [Created] (MARMOTTA-346) update admin-ui for marmotta-reasoner-kiwi to use the skwrl-mode for codemirror

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-346:


 Summary: update admin-ui for marmotta-reasoner-kiwi to use the 
skwrl-mode for codemirror
 Key: MARMOTTA-346
 URL: https://issues.apache.org/jira/browse/MARMOTTA-346
 Project: Marmotta
  Issue Type: Improvement
  Components: Admin Interface
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Thomas Kurz
Priority: Minor
 Fix For: 3.2


Currently, the admin-ui of the marmotta-reasoner-kiwi module uses a plain 
textarea as editor of the reasoning program

The webjar codemirror-modes contains a codemirror-mode for skwrl.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: [DISCUSS] Apache Marmotta Graduation Resolution

[Jakob Frank]

I'd like to see more discussion about the whole draft! At least some comment...

We should finish the resolution until Oct. 27th, and IMHO it makes
sense to have a final VOTE on the text (which should start Thursday
latest) so c'mon folks, speak up!

As for the Chair: I'm OK with all three candidates, but would prefer
Sergio or myself to allow Sebastian focus on the technical aspects.

Best,
Jakob


On 21 October 2013 18:11, Sergio Fernández  wrote:
> On 18/10/13 11:29, Jakob Frank wrote:
>>
>> * the PMC Chair / VP [6]: the candidates so far are Sebastian, Sergio
>>   and myself who would be willing to take the role.
>> Do you have other nominees?
>> Do you have a preference or objections? (remember: this is a public
>> list, but you can send you concerns also toprivate@marmotta.i.a.o)
>
>
> I'd like to see more discussion about this point ;-)
>
>
> --
> Sergio Fernández
> Senior Researcher
> Knowledge and Media Technologies
> Salzburg Research Forschungsgesellschaft mbH
> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> T: +43 662 2288 318 | M: +43 660 2747 925
> sergio.fernan...@salzburgresearch.at
> http://www.salzburgresearch.at

[DISCUSS] Apache Marmotta Graduation Resolution

[Jakob Frank]

Hi all,

in order to move forward with the graduation process we need to create
a Resolution Charter which will be finally (after approved by a VOTE
on general@i.a.o) sent to the ASF Board. [1]

I started out with a draft [2] and changed the most obvious things for
Marmotta, but there are some things we need to decide on (marked with
##FIXME in the draft)
* project description: I took "an open platform for Linked Data" -
because it's the first sentence on our webpage [3]. Do you have any
better idea or is it OK?
* initial project members: I took the full committer/ppmc list plus
Fabian and Nandana who were invited [4] and accepted, Andy refused but
will stay in contact on the dev@marmotta.(i.)a.o list [5]
  Is there anyone else who wants to step down?
* the PMC Chair / VP [6]: the candidates so far are Sebastian, Sergio
and myself who would be willing to take the role.
  Do you have other nominees?
  Do you have a preference or objections? (remember: this is a public
list, but you can send you concerns also to private@marmotta.i.a.o)
* project bylaws: do we need project specific bylaws? What would they be?
  Topics that could be handled in the bylaws: committer == PMC, VOTE
rules (majority vs. consensus vs. unanimous)
* and of course all the rest of the resolution.

The next board meeting is on Nov 20th 2013 (2013-11-20), so to stay
<12 months in incubation we have the following schedule:
- until 2013-10-27: draft discussion on dev@marmotta.i.a.o, then send
to general@i.a.o for discussion
- until 2013-11-02: start VOTE on general@i.a.o
- until 2013-11-09: send resolution to board@a.o to be included into
the November Agenda.
All dates have some backup time, but we can finish the process also earlier.

Best,
Jakob

[1] http://incubator.apache.org/guides/graduation.html#toplevel
[2] 
https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt
[3] http://marmotta.incubator.apache.org/
[4] 
http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201310.mbox/%3C525BC467.4040208%40apache.org%3E
[5] 
http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201310.mbox/%3C525D5AA8.9070903%40apache.org%3E
[6] http://www.apache.org/foundation/how-it-works.html#pmc-chair
[7] 
https://svn.apache.org/repos/asf/incubator/marmotta/graduation/resolution.txt

Resolution DRAFT [7]
==

X. Establish the Apache Marmotta Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to an open platform for Linked Data.
## FIXME: project-description: "an open platform for Linked Data"

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache Marmotta Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

## FIXME: (again) project-description
   RESOLVED, that the Apache Marmotta Project be and hereby is
   responsible for the creation and maintenance of software
   related to an open platform for Linked Data;
   and be it further

   RESOLVED, that the office of "Vice President, Apache Marmotta" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache Marmotta Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Marmotta Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Marmotta Project:

## FIXME: Update the list of initial members
 * Peter Ansell 
 * Fabian Christ   
     * Sergio Fernandez 
 * Jakob Frank   
 * Dietmar Glachs  
 * Thomas Kurz   
 * Nandana Mihindukulasooriya  
 * Raffaele Palmieri 
 * Sebastian Schaffert  
 * Rupert Westenthaler 

## FIXME: Enter the appointed PMC Chair / VP here
   NOW, THEREFORE, BE IT FURTHER RESOLVED, that ${VP}
   be appointed to the office of Vice President, Apache Marmotta, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

## FIXME: Remove this if we do not have bylaws
   RESOLVED, that the initial Apache Marmotta PM

[jira] [Created] (MARMOTTA-345) Refactor the local file import

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-345:


 Summary: Refactor the local file import
 Key: MARMOTTA-345
 URL: https://issues.apache.org/jira/browse/MARMOTTA-345
 Project: Marmotta
  Issue Type: Task
  Components: Platform
Affects Versions: 3.2
Reporter: Jakob Frank
Assignee: Sebastian Schaffert


The local file-import was a quick proof of concept implementation and should be 
restructured.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: thinking about graduation...

[Jakob Frank]

On 16 October 2013 09:59, Sergio Fernández  wrote:
> On 16/10/13 09:40, Jakob Frank wrote:
>>
>> We are talking/discussing about individuals here, so IMHO the
>> PMC-Chair discussion should be moved toprivate@marmotta.i.a.o
>
> Do you think so? Personally I cannot find any reason why such discussion
> could not be public at dev@...
We are talking about people here, so it's the same like talking about
committers or pmc-members.

I think it's not right to discuss the pros/cons of a person (even for
a specific role) in the general public.

Best,
Jakob

Re: Accidently merged into "master"

[Jakob Frank]

Easiest way would be to do a --hard reset of the master, but that's
not allowed in the ASF Repo (at least for branch master)
Also deleting the remote branch and re-pushing it is not allowed.

So I filed an issue with Infra [1]

Best,
Jakob

[1] https://issues.apache.org/jira/browse/INFRA-6876

On 1 October 2013 02:13, Peter Ansell  wrote:
> That didn't reset to the right commit because there were commits since
> cdb3223d that need to be kept ... I will look into it some more. Part
> of the complexity seems to be that git can't easily revert merges and
> other commits simultaneously so it may need two reverts (and then a
> squash to make it look like a single revert before pushing)
>
> Peter
>
> On 1 October 2013 09:51, Peter Ansell  wrote:
>> Fixed.
>>
>> For reference, the command I used was the following, where the SHA1
>> hash is the merge commit, and I needed to use -m 2 because it was a
>> merge, and specifically "2" because of the direction the merge was
>> done in (-m 1 would have retained the other tree of commits):
>>
>> git revert -m 2 a9bf7e4fa56f00e26e09a5fae002686eb65631df
>>
>> You can see the comparison at the following URL on GitHub, which for
>> me is completely empty, as desired.
>>
>> https://github.com/ansell/incubator-marmotta/compare/apache:cdb3223db7439a9f8fd7fb5159ffd52f6da0ecb7...4aa87dbe5c121476176292416e36e71f613be83e?expand=1#files_bucket
>>
>> Cheers,
>>
>> Peter
>>
>> On 1 October 2013 07:55, Peter Ansell  wrote:
>>> I think you need to push a revert commit for the master branch.
>>>
>>> --
>>> Peter
>>>
>>> On 01/10/2013, at 3:31 AM, Sebastian Schaffert 
>>>  wrote:
>>>
 Sorry, I don't manage (Apache does not allow forcing reverting a version).
 Maybe someone who already did this can help me tomorrow ...

 Greetings,

 Sebastian


 2013/9/30 Sebastian Schaffert 

> Hi guys,
>
> while working on MARMOTTA-324, I accidently merged back and pushed my
> branch into master instead of develop. I'll try to revert this change as
> soon as possible, sorry.
>
> Greetings,
>
> Sebastian
>

Re: thinking about graduation...

[Jakob Frank]

On 16 October 2013 08:50, Nandana Mihindukulasooriya
 wrote:
>>  Technical leadership and chair are IMO two different things.
>>> Agreed.
>>
>> OK. So, what do you propose? I  would be willing on take such role, and
>> Jakob I/ m pretty sure too. But that's something needs to be agreed by the
>> community. Do we need to open a vote for such simple decision?
>
> I think it would be nice to have a discuss thread or vote thread and keep
> it open at least for 72 hours so that if anyone wants to propose someone /
> object to someone they can do so.  I think you can even call for volunteers
> here in this thread so that anyone has a chance to to propose themselves.
> In either way, with a core community who knows each other pretty well, I
> hope it shouldn't be much complex.

We are talking/discussing about individuals here, so IMHO the
PMC-Chair discussion should be moved to private@marmotta.i.a.o

Best,
Jakob

3.1.x and 3.0.x maintainance-branches

[Jakob Frank]

Hi all,

today i pushed two new branches to the repository: maintenance-3.0.x
and maintenance-3.1.x

They start at the resp. release tags (3.0.0-incubating and
3.1.0-incubating) and are there for backports, bugfixes, etc...

I already used both branches to backport the KiWiLoader [1] to the
previous releases. If anyone has a  fix or feature that should be
backported please tell so, I'd like to make a create
maintenance-release rather soon.

Best,
Jakob

[1] https://issues.apache.org/jira/browse/MARMOTTA-344

Re: [VOTE] Graduate Apache Marmotta from incubator and become a TLP

[Jakob Frank]

+1

On 15 October 2013 15:15, Sebastian Schaffert
 wrote:
> +1
>
>
> 2013/10/15 Rupert Westenthaler 
>
>> +1
>>
>> On Tue, Oct 15, 2013 at 12:45 PM, Szaby Grünwald 
>> wrote:
>> > +1
>> >
>> >
>> > On 15 October 2013 08:30, Sergio Fernández  wrote:
>> >
>> >> Hi all,
>> >>
>> >> since entering Incubation in December 2012, the project and the
>> community
>> >> have significantly evolved. So I think we accomplished most of the goals
>> >> that we set when we decided to join ASF Incubator.
>> >>
>> >> Therefore, although it is not a requirement, but recommended to express
>> >> our willingness/readiness to govern ourselves, I'd like to start this
>> vote
>> >> within the community about the graduating of Marmotta out of Incubator
>> and
>> >> establishing it as Top Level Project.
>> >>
>> >> [ ] +1  Apache Marmotta is ready to graduate
>> >> [ ] +0  Don't care
>> >> [ ] -1  Apache Marmotta is not ready to graduate because...
>> >>
>> >> Everyone in the community is encouraged to vote. Votes from IPMC
>> >> members and Mentors are binding. This vote will run 72-hours.
>> >>
>> >> Kind regards,
>> >>
>> >> --
>> >> Sergio Fernández
>> >> Senior Researcher
>> >> Knowledge and Media Technologies
>> >> Salzburg Research Forschungsgesellschaft mbH
>> >> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
>> >> T: +43 662 2288 318 | M: +43 660 2747 925
>> >> sergio.fernandez@**salzburgresearch.at<
>> sergio.fernan...@salzburgresearch.at>
>> >> http://www.salzburgresearch.at
>> >>
>>
>>
>>
>> --
>> | Rupert Westenthalerrwes...@apache.org
>> | Bodenlehenstraße 11 ++43-699-11108907
>> | A-5500 Bischofshofen
>>

[jira] [Created] (MARMOTTA-344) Backport KiWiLoader to 3.1 and 3.0

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-344:


 Summary: Backport KiWiLoader to 3.1 and 3.0
 Key: MARMOTTA-344
 URL: https://issues.apache.org/jira/browse/MARMOTTA-344
 Project: Marmotta
  Issue Type: Improvement
  Components: Triple Store
Reporter: Jakob Frank
Assignee: Sebastian Schaffert


KiWiLoader significantly improves the performance for bigger data imports, thus 
should be available also for the 3.0 and 3.1 versions.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: thinking about graduation...

[Jakob Frank]

On 14 October 2013 12:16, Sergio Fernández  wrote:
> * The list of initial members of the project. Beside your mentoring during
> incubation, I'd like to have on board all our mentors after graduation. I
> really appreciate your experience, both about Apache and Semantic Web
> technologies. So, Andy, Fabian, Nandana, would you like to continue with us
> after graduation?
++1

> * Who would be the Apache Marmotta Vice President? Personally my candidate
> for such position is Sebastian, since he is the technical leader of the
> project.
IMHO that's something we can discuss together with the preparation of
the resolution to the board.

FMPOV, the first step is for us to "decide" that we want to go for
graduation - i.e. we need to VOTE. Our mentors already repeatedly told
us to move forward, so I don't think there's an issue here.

So if nobody opposes, i'll start a VOTE tomorrow or the day after...

Best,
Jakob

[jira] [Resolved] (MARMOTTA-310) Create kiwi-loader module

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-310.
--

Resolution: Implemented

> Create kiwi-loader module
> -
>
> Key: MARMOTTA-310
> URL: https://issues.apache.org/jira/browse/MARMOTTA-310
> Project: Marmotta
>  Issue Type: New Feature
>  Components: Triple Store
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.2
>
>   Original Estimate: 48h
>  Time Spent: 7h 10m
>  Remaining Estimate: 0h
>
> It would be nice to have an option to load big datasets into a 
> kiwi-triplestore without having to start up the complete marmotta platform.
> A simple CLI tool that (exclusively?) connects to the database and loads a 
> provided rdf-dump/file should do the trick.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: thinking about graduation...

[Jakob Frank]

Another positive comment re. graduation by our October-Report Shepherd
(Andrei Savu (asavu), [1])!

The Podling status page looks complete [2], only the Podling-Name
search is still open [3] - who should close this issue? We? Mentors?
Someone from trademark@a.o?

Best,
Jakob

[1] http://markmail.org/message/uadwz2kuxobgsbyq
[2] http://incubator.apache.org/projects/marmotta.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-39

On 5 October 2013 12:26, Sergio Fernández
 wrote:
> I think the following report illustrates quite nice how hard we were working
> in the last 10 months:
>
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12314321&periodName=monthly&daysprevious=300&cumulative=true&versionLabels=all&selectedProjectId=12314321&reportKey=com.atlassian.jira.plugin.system.reports%3Acreatedvsresolved-report&Next=Next
>
> :-)
>
>
> On 04/10/13 16:23, Fabian Christ wrote:
>>
>> Hi,
>>
>> yeah - graduation time :)
>>
>> +1 to go for it
>>
>> Best,
>>   - Fabian
>>
>> 2013/10/4 Sebastian Schaffert :
>>>
>>>
>>> Am Donnerstag, den 03.10.2013, 17:57 +0200 schrieb Sergio Fernández:

 Hi,

 although not yet official announced (awaiting to be mirrored), we could
 say we've fulfilled the milestone of releasing a new version of
 Marmotta. Not because the release itself, but for all those things we
 have learned as project in the way. Since we joined Incubation in
 December (although we actually started in February after we got LMF 2.6)
 we have evolved a lot as team, and that can be noticed in how the
 quality of the software has improved in these months. Thanks all of you
 for such effort!

 Therefore I think now we are finally ready to graduate Marmotta as a
 Apache Top Level Project, so it's the time to seriously talk about it.
 And I'd like to hear what you, all the team, do think about such
 important step.
>>>
>>>
>>> I agree that we should finally move forward. Can we quickly summarize
>>> the steps that are remaining (by checking against the graduation guide
>>> you mentioned)?
>>>
>>> For quick reference, here is our status page:
>>>
>>>* http://incubator.apache.org/projects/marmotta.html
>>>

 Personally I think the graduation would bring some clear benefits (more
 self governance, more visibility, faster releases, etc) that we
 currently don't have as a podling. But we still need to continue growing
 as project, don't forget that.

 BTW, there is a good guide about the graduation process [1]. Get the
 name approved [2] would be one of the first things to push forward.

 Cheers,

 [1] http://incubator.apache.org/guides/graduation.html
 [2] http://issues.apache.org/jira/browse/PODLINGNAMESEARCH-39

>>>
>>> Greetings,
>>>
>>> Sebastian
>>>
>
> --
> Sergio Fernández
> Salzburg Research
> +43 662 2288 318
> Jakob-Haringer Strasse 5/II
> A-5020 Salzburg (Austria)
> http://www.salzburgresearch.at

[jira] [Created] (MARMOTTA-339) ldpath-backend-linkeddata deploys tar.gz and zip to maven repository

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-339:


 Summary: ldpath-backend-linkeddata deploys tar.gz and zip to maven 
repository
 Key: MARMOTTA-339
 URL: https://issues.apache.org/jira/browse/MARMOTTA-339
 Project: Marmotta
  Issue Type: Bug
  Components: LDPath
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
 Fix For: 3.2


error in the deploy settings?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (MARMOTTA-330) "Data View" in platform-core results in HTTP 415 errors

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-330:


 Summary: "Data View" in platform-core results in HTTP 415 errors
 Key: MARMOTTA-330
 URL: https://issues.apache.org/jira/browse/MARMOTTA-330
 Project: Marmotta
  Issue Type: Bug
  Components: Platform, Web Services
Affects Versions: 3.2
Reporter: Jakob Frank
Assignee: Thomas Kurz
 Fix For: 3.2


When opening the "Data View", no results are shown but the console logs a 
series of HTTP 415 "Unsupported Media Type" errors.

Looks like this is related to MARMOTTA-325



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: [RESULT][VOTE] Release Apache Marmotta 3.1.0-incubating

[Jakob Frank]

Hooray!

Best,
Jakob

On 3 October 2013 14:45, Sebastian Schaffert  wrote:
> FYI, we will proceed with the release process then.
>
> -- Forwarded message --
> From: Sebastian Schaffert 
> Date: 2013/10/3
> Subject: [RESULT][VOTE] Release Apache Marmotta 3.1.0-incubating
> To: gene...@incubator.apache.org
>
>
> Dear all,
>
> thanks for your support! The 72 hours have now passed and we have 8
> positive votes, of which 3 are binding and 5 are non-binding. We now have
> the required number of positive binding votes and will therefore proceed
> with the release.
>
> The remark by sebb has been added as an issue for the next release
> (MARMOTTA-327).
>
> Greetings,
>
> Sebastian
>
>
>
> 2013/10/2 Olivier Lamy 
>
>> +1 sources build fine.
>>
>> --
>> Olivier
>> On Sep 30, 2013 8:17 PM, "Sebastian Schaffert" 
>> wrote:
>>
>> > Dear all,
>> >
>> > After several months of work since the last incubating release
>> > (3.0.0-incubating) in April, we are now ready to release version
>> > 3.1.0-incubating. We fixed all the remaining issues that have been
>> > discussed in April (see thread [1]) plus many more technical issues. We
>> > have already held a vote that was open for more than 72 hours on the
>> Apache
>> > Marmotta developer mailinglist [2]. The vote concluded [3] with 7
>> positive
>> > votes, of which 2 have been binding from IPMC members (Andy and Nandana)
>> > and the remaining 5 from the Apache Marmotta developers.
>> >
>> > I'd therefore like to ask the general incubator to check our release
>> > candidate. The release notes are available at the Jira Issue Tracker [4].
>> > The vote form is included at the bottom of this mail.
>> >
>> > Greetings,
>> >
>> > Sebastian
>> >
>> >
>> > [1] http://apache.markmail.org/message/5tieelmeevi2j6xb
>> > [2] http://apache.markmail.org/message/lk3hc3jutoaxp6dr
>> > [3] http://apache.markmail.org/message/fvytzho2pnhasw2c
>> > [4]
>> >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321&version=12324026
>> >
>> > ===
>> > A candidate for the Marmotta 3.1.0-incubating release is available at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/
>> >
>> > The release candidate is based on the sources tagged with
>> 3.1.0-incubating
>> > in:
>> >
>> > https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git
>> >
>> > The release candidate consists of the following source distribution
>> > archives:
>> > - apache-marmotta-3.1.0-
>> > incubating-src.[zip|tar.gz]
>> >   SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527
>> >   SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729
>> >
>> > In addition, the following supplementary binary distributions are
>> provided:
>> > - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz]
>> >   SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd
>> >   SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617
>> > - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz]
>> >   SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab
>> >   SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75
>> > - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz]
>> >   SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142
>> >   SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838
>> >
>> > A staged Maven repository is available for review at:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachemarmotta-092/
>> >
>> > Please vote on releasing this package as Apache Marmotta
>> 3.1.0-incubating.
>> > The vote is open for the next 72 hours and passes if a majority of at
>> > least three +1 Marmotta PMC votes are cast.
>> >
>> > [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating
>> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
>> > [ ] -1 Do not release this package because...
>> >
>> > ===
>> >
>> > Release Notes - Marmotta - Version 3.1-incubating
>> >
>> > ** Sub-task
>> > * [MARMOTTA-216] - Implement JOIN improvements
>> > * [MARMOTTA-217] - Implement FILTER improvements
>> > * [MARMOTTA-218] - Integrate in marmotta-sparql
>> >
>> >
>> > ** Bug
>> > * [MARMOTTA-28] - Implement tests for core that take into account
>> > triple store changes
>> > * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently
>> > not working properly
>> > * [MARMOTTA-66] - Rework sesame-commons ResourceUtils
>> > * [MARMOTTA-143] - unable to import big files
>> > * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer
>> > * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords
>> > * [MARMOTTA-155] - 3-char lang-tags are not accepted
>> > * [MARMOTTA-156] - Add Logback configuration to all tests to
>> > enable/disable debug logging
>> > * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file
>> contains
>> > wrong comments
>> > *

[jira] [Resolved] (MARMOTTA-323) Splash Screen of version 3.1.0-incubating shows version 3.0.0

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-323.
--

   Resolution: Fixed
Fix Version/s: 3.2

splash-image now generated using a maven plugin.

> Splash Screen of version 3.1.0-incubating shows version 3.0.0
> -
>
> Key: MARMOTTA-323
> URL: https://issues.apache.org/jira/browse/MARMOTTA-323
> Project: Marmotta
>  Issue Type: Bug
>  Components: Launchers
>Affects Versions: 3.1-incubating
>Reporter: Rupert Westenthaler
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.2
>
>
> The splash screen shown when launching marmotta notes the wrong version. 
> 3.0.0-incubating instead of 3.1.0-incubating



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (MARMOTTA-317) module description in installer is not properly formatted

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-317.
--

Resolution: Fixed

module description is (XML-Text-)normalized during refpack generation

> module description in installer is not properly formatted
> -
>
> Key: MARMOTTA-317
> URL: https://issues.apache.org/jira/browse/MARMOTTA-317
> Project: Marmotta
>  Issue Type: Bug
>  Components: Launchers
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Trivial
> Fix For: 3.2
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> On the installer-screen where you select the modules to install, the 
> description of the components has a weird formatting: line breaks and 
> indentation look almost arbitrary.
> This might be because of automatic formatting of the source-xml used to 
> generate the installer.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-316) Add our new committers to the installer welcome screen

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-316.
--

Resolution: Fixed

> Add our new committers to the installer welcome screen
> --
>
> Key: MARMOTTA-316
> URL: https://issues.apache.org/jira/browse/MARMOTTA-316
> Project: Marmotta
>  Issue Type: Task
>  Components: Launchers
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.2
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> Our new commiters are not listed in the installer welcome page!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

October 2013 Report timeline

[Jakob Frank]

It's reporting time, this is my draft:

Marmotta

An open implementation of a Linked Data Platform.

Marmotta has been incubating since 2012-12-03.

Three most important issues to address in the move towards graduation:

  1. Get the 3.1.0-incubating resease out
  2. Check whether Marmotta is a suitable name
(https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-39)
  3. PPMC & IPMC VOTE

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  No such issues.

How has the community developed since the last report?

  * The upcoming  3.1.0-incubating release was rescheduled to "after
summer vacation time" and is currently VOTEd on at dev@marmotta.i.a.o
(http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201309.mbox/%3CCAP3xvwa4oFR-w%2BNqh1QwpjKdL6%2BmEpgvnXt5Af5Sf-FkM98TRA%40mail.gmail.com%3E)
  * Traffic on dev@marmotta.i.a.o was decreasing over the summer
months but is rising again in September during the preparation of the
next release.
  * We are starting to get bug reports from non-committers in JIRA
while traffic on users@marmotta.i.a.o is slowly evolving.

How has the project developed since the last report?

  * The upcoming 3.1.0-incubating release is ready and currently under VOTE
  * The project was explicitly recommended for graduation after the
last report in July
(http://mail-archives.apache.org/mod_mbox/incubator-general/201307.mbox/%3c51ec142f.4080...@apache.org%3E)
but we wanted to have another release before graduation to stabilize
the release process and and have another check of the N&L by the
incubator community.

Date of last release:

  2013-04-24 (3.0.0-incubating)

When were the last committers or PMC members elected?

  2013-05-21 (Raffaele Palmieri)
  2013-06-24 (Peter Ansell)



-- Forwarded message --
From: Marvin Humphrey 
Date: 26 September 2013 02:09
Subject: October 2013 Report timeline
To: "gene...@incubator.apache.org" 


Greets,

Here's the timeline for the Incubator's October 2013 report, which is also
available on the wiki page:

http://wiki.apache.org/incubator/October2013

Wed October 2  -- Podling reports due by end of day
Sun October 6  -- Shepherd reviews due by end of day
Sun October 6  -- Summary due by end of day
Tue October 8  -- Mentor signoff due by end of day
Wed October 9  -- Report submitted to board
Wed October 16 -- Board meeting

There are two tweaks to the schedule as compared with last month: both the
shepherd comments and main report summary have been moved up and are now due by
end-of-day Sunday instead of end-of-day Tuesday, in order to allow more time
for review by Mentors and other interested community members.

Reports are due for the following podlings one week from today. (Joe Schaefer,
if you could run the script to send out reminders, that would be great.)

Celix
Chukwa
DeviceMap
Helix
jclouds
Marmotta
MetaModel
ODF Toolkit
Olingo
Ripple
Samza
Sentry
Spark
Storm
Stratos
Tashi
VXQuery

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Marmotta 3.1.0-incubating (RC3)

[Jakob Frank]

+1

While checking, I found some minor issues (MARMOTTA-316 to
MARMOTTA-321) which are IMHO fine to leave for the next release...

Best,
Jakob

On 24 September 2013 17:30, Sebastian Schaffert  wrote:
> Next try :-) Please vote until Friday, 27th, 18:00 CEST.
>
>
> ===
> A candidate for the Marmotta 3.1.0-incubating release is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/
>
> The release candidate is based on the sources tagged with 3.1.0-incubating
> in:
>
> https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git
>
> The release candidate consists of the following source distribution
> archives:
> - apache-marmotta-3.1.0-incubating-src.[zip|tar.gz]
>   SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527
>   SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729
>
> In addition, the following supplementary binary distributions are provided:
> - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz]
>   SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd
>   SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617
> - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz]
>   SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab
>   SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75
> - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz]
>   SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142
>   SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachemarmotta-092/
>
> Please vote on releasing this package as Apache Marmotta 3.1.0-incubating.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Marmotta PMC votes are cast.
>
> [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> ===
>
> Release Notes - Marmotta - Version 3.1-incubating
>
> ** Sub-task
> * [MARMOTTA-216] - Implement JOIN improvements
> * [MARMOTTA-217] - Implement FILTER improvements
> * [MARMOTTA-218] - Integrate in marmotta-sparql
>
>
> ** Bug
> * [MARMOTTA-28] - Implement tests for core that take into account
> triple store changes
> * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently
> not working properly
> * [MARMOTTA-66] - Rework sesame-commons ResourceUtils
> * [MARMOTTA-143] - unable to import big files
> * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer
> * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords
> * [MARMOTTA-155] - 3-char lang-tags are not accepted
> * [MARMOTTA-156] - Add Logback configuration to all tests to
> enable/disable debug logging
> * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file contains
> wrong comments
> * [MARMOTTA-171] - remove legacy subdirs from src/main/webapp in
> marmotta-webapp
> * [MARMOTTA-186] - LDPath parser fails on local names that contain '.'
> * [MARMOTTA-187] - ldpath extension for CM does not recognize local
> names with '.' or '-'
> * [MARMOTTA-191] - SPARQL graph results fails under some circunstances
> * [MARMOTTA-197] - ldpath is loosing brackets on re-serialisation
> * [MARMOTTA-204] - Update to Sesame 2.7.1
> * [MARMOTTA-205] - Turtle-Exports do not contain any language tags
> * [MARMOTTA-206] - Strictly follow the standard formatting on the NOTICE
> * [MARMOTTA-208] - Meta Put Webservice Deleting Tuples Incorrectly
> * [MARMOTTA-213] - Address the issues on our NOTICE files
> * [MARMOTTA-214] - Memento timestamp does not use the right template
> * [MARMOTTA-221] - ldpath is loosing quotes for StringConstants on
> re-serialisation
> * [MARMOTTA-225] - Serializing ldpath field mappings with URIs as
> fieldname does not work correctly
> * [MARMOTTA-227] - Snorql uses different set of prefixes in the query
> evaluation than the showed at the user interface
> * [MARMOTTA-231] - Admin Interface: changing list values does not work
> * [MARMOTTA-232] - Reasoner does not add all justifications
> * [MARMOTTA-234] - Loading webjars resources doesn't work
> * [MARMOTTA-235] - facading with primitive types (int, long, float,
> etc) results in ClassCastExeption
> * [MARMOTTA-236] - triple-leak with concurrent connections in facading
> * [MARMOTTA-240] - MediaWiki provider is not detecting all redirects.
> * [MARMOTTA-242] - LdPath Templating shoud set default output-encoding
> * [MARMOTTA-243] - Fix JRebel configuration
> * [MARMOTTA-247] - URNs are not properly handled by the Linked Data
> Explorer
> * [MARMOTTA-253] - Delete context does not work for external URIs
> * [MARMOTTA-254] - Triples are not available after import
> * [MARMOTT

[jira] [Created] (MARMOTTA-321) update/cleanup the entries in the LICENSE file for "Apache Marmotta code subcomponents"

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-321:


 Summary: update/cleanup the entries in the LICENSE file for 
"Apache Marmotta code subcomponents"
 Key: MARMOTTA-321
 URL: https://issues.apache.org/jira/browse/MARMOTTA-321
 Project: Marmotta
  Issue Type: Bug
  Components: Admin Interface
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
 Fix For: 3.2


Most of entries in the "Apache Marmotta code subcomponents" are for 3rd-party 
javascripts libraries which have been moved into separate webjars in Marmotta.

So the paths in the LICENSE file should be updated

For some of these custom webjars, there might be an official release so they 
can be removed from Marmotta (and therefor also from the LICENSE)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-320) fix typos in the LICENSE file

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-320:


 Summary: fix typos in the LICENSE file
 Key: MARMOTTA-320
 URL: https://issues.apache.org/jira/browse/MARMOTTA-320
 Project: Marmotta
  Issue Type: Bug
  Components: Launchers
Reporter: Jakob Frank
Assignee: Sergio Fernández
Priority: Minor


The LICENSE.txt included in the binary distributions contains some typos:
- webapp, line 2505 (wrong inserted url)
- installer, line 925 (s/ther/the/)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (MARMOTTA-199) uninstaller.jar is invalid or corrupt

[Jakob Frank (JIRA)]

[ 
https://issues.apache.org/jira/browse/MARMOTTA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777320#comment-13777320
 ] 

Jakob Frank commented on MARMOTTA-199:
--

Just tested with 3.1.0-incubating installer; worked fine

java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)


> uninstaller.jar is invalid or corrupt
> -
>
> Key: MARMOTTA-199
> URL: https://issues.apache.org/jira/browse/MARMOTTA-199
> Project: Marmotta
>  Issue Type: Bug
>  Components: Extras
>Affects Versions: 3.0-incubating
> Environment: 3.0.0-incubating installer
> java version "1.7.0_15" (headless)
> OpenJDK Runtime Environment (IcedTea7 2.3.7) (7u15-2.3.7-0ubuntu1~12.10.1)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
>Reporter: Jakob Frank
>Assignee: Sergio Fernández
> Fix For: 3.2
>
>
> After installing Marmotta with the installer, the uninstaller would not work:
> java -jar Uninstaller/uninstaller.jar
> Error: Invalid or corrupt jarfile uninstaller.jar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-319) Allow starting apache marmotta directly after installation

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-319:


 Summary: Allow starting apache marmotta directly after installation
 Key: MARMOTTA-319
 URL: https://issues.apache.org/jira/browse/MARMOTTA-319
 Project: Marmotta
  Issue Type: Wish
  Components: Launchers
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sergio Fernández
Priority: Trivial
 Fix For: 3.2


If izpack provides this option: it would be nice to have a checkbox like: 
"automatically startup after the installation is complete"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-318) provide a start-script for the platform within the installer

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-318:


 Summary: provide a start-script for the platform within the 
installer
 Key: MARMOTTA-318
 URL: https://issues.apache.org/jira/browse/MARMOTTA-318
 Project: Marmotta
  Issue Type: Wish
  Components: Launchers
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sergio Fernández
Priority: Minor
 Fix For: 3.2


When using the installer, you can create shortcuts for the application 
menu/desktop to start the platform.

If you do not select this option, you have to start tomcat manually, which is 
in fact the "wrong" apache project ;-)
It would be nice to provide a simple start-script in the root installation 
directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-317) module description in installer is not properly formatted

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-317:


 Summary: module description in installer is not properly formatted
 Key: MARMOTTA-317
 URL: https://issues.apache.org/jira/browse/MARMOTTA-317
 Project: Marmotta
  Issue Type: Bug
  Components: Launchers
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sergio Fernández
Priority: Trivial
 Fix For: 3.2


On the installer-screen where you select the modules to install, the 
description of the components has a weird formatting: line breaks and 
indentation look almost arbitrary.

This might be because of automatic formatting of the source-xml used to 
generate the installer.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-316) Add our new committers to the installer welcome screen

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-316:


 Summary: Add our new committers to the installer welcome screen
 Key: MARMOTTA-316
 URL: https://issues.apache.org/jira/browse/MARMOTTA-316
 Project: Marmotta
  Issue Type: Bug
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
 Fix For: 3.2


Our new commiters are not listed in the installer welcome page!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-314) getGraph is returning wrong datatype

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-314:


 Summary: getGraph is returning wrong datatype
 Key: MARMOTTA-314
 URL: https://issues.apache.org/jira/browse/MARMOTTA-314
 Project: Marmotta
  Issue Type: Bug
  Components: LDPath
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
 Fix For: 3.2


The graph keyword in ldpath expects a list of URIs to limit the evaluation of 
the program to a (set of) named graph(s)/context(s).

currently getGraph function of an LDPath Program is returning a Set; 
Set would be better.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-311) Check kiwi-stack for consistency

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-311:


 Summary: Check kiwi-stack for consistency
 Key: MARMOTTA-311
 URL: https://issues.apache.org/jira/browse/MARMOTTA-311
 Project: Marmotta
  Issue Type: Improvement
  Components: Triple Store
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
 Fix For: 3.2


When connecting to an existing database, the kiwi-triplestore should check the 
consistency of the kiwi-sail-stack.

Background: When connecting to a database with an incomplete configuration 
(e.g. without kiwi-versioning while the database was created with), the 
database might become corrupted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-310) Create kiwi-loader module

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-310:


 Summary: Create kiwi-loader module
 Key: MARMOTTA-310
 URL: https://issues.apache.org/jira/browse/MARMOTTA-310
 Project: Marmotta
  Issue Type: Improvement
  Components: Triple Store
Affects Versions: 3.1-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
 Fix For: 3.2


It would be nice to have an option to load big datasets into a kiwi-triplestore 
without having to start up the complete marmotta platform.

A simple CLI tool that (exclusively?) connects to the database and loads a 
provided rdf-dump/file should do the trick.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-208) Meta Put Webservice Deleting Tuples Incorrectly

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-208.
--

Resolution: Cannot Reproduce
  Assignee: Jakob Frank  (was: Thomas Kurz)

confirmed sebastians suggestion: this was fixed some time ago...

> Meta Put Webservice Deleting Tuples Incorrectly
> ---
>
> Key: MARMOTTA-208
> URL: https://issues.apache.org/jira/browse/MARMOTTA-208
> Project: Marmotta
>  Issue Type: Bug
>  Components: Platform
>Affects Versions: 3.0-incubating
> Environment: Windows, JDK 6, H2 database
>Reporter: Jonathan Koppenhofer
>Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>
> If you use the Meta Put webservice to update your metadata, tuples that did 
> not change between the existing metadata and the new metadata are removed, 
> leaving on the tuples that changed as active for the subject.
> To Reproduce:
> 1.) Use the Meta webservice to put some RDF metadata... For example...
>xmlns:context="http://localhost:8080/LMF/context/";
>   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
>   xmlns:local="http://localhost:8080/LMF/resource/";
>   xmlns:dc="http://purl.org/dc/elements/1.1/";>
> http://localhost:8080/LMF/resource/test:4";>
>rdf:datatype="http://www.w3.org/2001/XMLSchema#string";>TESTING me with Linked 
> Data
>  rdf:datatype="http://www.w3.org/2001/XMLSchema#string";>this is a test of 
> me
> 
> 
> 2.) This should create 2 new tuples for the particular subject.
> 3.) Now use the exact same RDF document, and do it again... You will notice 
> that all tuples for the subject are removed.
> 4.) Now change either the dc.title or dc.decsription values, and put the meta 
> again. You will now notice the tuple exists for the changed value, but still 
> does not exist for the value that was not changed.
> In looking at the MetaWebService.java in the putMeta method, I notice it 
> remove() for all tuples, and then right after add() for the new tuples all 
> within the same transaction. It would seem the remove and the add being in 
> the same transaction is causing the issue if you are removing a tuple you are 
> simultaneously trying to add.
> I made the change to...
> 1.) Remove tuples
> 2.) commit
> 3.) begin a new transaction
> 4.) add
> 4.) commit
> ... and it seemed to give me the expected behavior.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-205) Turtle-Exports do not contain any language tags

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-205.
--

Resolution: Cannot Reproduce

seems to be solved through the rdf-1.1 rollback

> Turtle-Exports do not contain any language tags
> ---
>
> Key: MARMOTTA-205
> URL: https://issues.apache.org/jira/browse/MARMOTTA-205
> Project: Marmotta
>  Issue Type: Bug
>  Components: Triple Store
>Affects Versions: 3.0-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>
> When serializing rdf data into turtle, all language tags are discarded.
> This is because Sesame appends language tags only to untyped literals, but we 
> are using the RDF1.1 notation which adds rdf:langString to Literals with 
> lang-tag.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-215) Select LDPath relative to a Graph/Context

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-215.
--

Resolution: Implemented

> Select LDPath relative to a Graph/Context
> -
>
> Key: MARMOTTA-215
> URL: https://issues.apache.org/jira/browse/MARMOTTA-215
> Project: Marmotta
>  Issue Type: Improvement
>  Components: LDPath
> Environment: N/A
>Reporter: Jonathan Koppenhofer
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.1-incubating
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Would be nice to be able to filter/select LDPath by Graph... Been discussed 
> before @ 
> https://groups.google.com/forum/?fromgroups=#!topic/lmf-users/bsekkhF-fIo

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-110) Split LDPath backend API

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-110.
--

Resolution: Implemented

> Split LDPath backend API
> 
>
> Key: MARMOTTA-110
> URL: https://issues.apache.org/jira/browse/MARMOTTA-110
> Project: Marmotta
>  Issue Type: Improvement
>  Components: LDPath
>Affects Versions: 2.6
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.1-incubating
>
>
> In LDPath, a backend is required to parse and evaluate a program.
> As parsing does not always require access to a datastore, it would be useful 
> to split the interface of the backend into two parts: one used for parsing 
> and one to evaluate programs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-225) Serializing ldpath field mappings with URIs as fieldname does not work correctly

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-225.
--

Resolution: Implemented

> Serializing ldpath field mappings with URIs as fieldname does not work 
> correctly
> 
>
> Key: MARMOTTA-225
> URL: https://issues.apache.org/jira/browse/MARMOTTA-225
> Project: Marmotta
>  Issue Type: Bug
>  Components: LDPath
>Affects Versions: 3.0-incubating
>Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> In ldpath it is possible to create a fieldmapping that is using an URI as 
> field-name. The idea behind this is to create new properties based on ldpath 
> constructs.
> However, the serialization of such a fieldmapping is invalid and cannot be 
> parsed:
> INPUT (valid):
> @prefix ex: <http://example.com/ldpath#>;
> ex:bar = ex:title :: xsd:string;
> Parsed and serialized (invalid):
> @prefix ex: <http://example.com/ldpath#>
> http://example.com/ldpath#bar = ex:title :: xsd:string;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-237) 137 Tests are ignored

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-237.
--

   Resolution: Not A Problem
Fix Version/s: 3.1-incubating

most of the skipped tests are ignored on the build-server (jenkins) because of 
a database being not available (postgres, mysql)

> 137 Tests are ignored
> -
>
> Key: MARMOTTA-237
> URL: https://issues.apache.org/jira/browse/MARMOTTA-237
> Project: Marmotta
>  Issue Type: Test
>Affects Versions: 3.1-incubating
>    Reporter: Jakob Frank
>    Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Currently many tests are ignored, probably because an Assume fails.
> This numberneeds to be reduced dramatically. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: marmotta 3.1.0-incubating release preparation

[Jakob Frank]

+1 for an IRC meeting.

Tuesday, Wednesday are fine for me

Best,
Jakob

On 9 September 2013 08:27, Sergio Fernández  wrote:
> Hi,
>
> development is evolving as usual, now the planned issue are being reduced to
> 20. Although we should find time to discuss the release preparation. I still
> see some of those issue (particularly MARMOTTA-228) that could be shift to
> 3.2, so then focus on getting a good release by fixing the bugs.
>
> What about a IRC meeting? Tuesday or Wednesday would be fine. Take into
> account we have developers in quite different time zones (UTC+1, UTC+2 and
> UTC+10 are the ones I know about), so it might be not so easy to find a
> common time-slot, but we should try it.
>
> Thanks.
>
> Cheers,
>
>
> On 02/09/13 16:43, Sergio Fernández wrote:
>>
>> Hi,
>>
>> now that more or less all of us should be back from the vacations break,
>> I think is time to resume the preparation of our next, and hopefully
>> last under incubation, release.
>>
>> Right now we have registered 25 issues for such milestone:
>>
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MARMOTTA%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.1-incubating%22%20ORDER%20BY%20priority%20DESC
>>
>>
>> Taking a look to the list, I think is something we could afford in the
>> following two weeks if we focus on solving the actual bugs (13) and we
>> shift major new features for the following release.
>>
>> For instance, MARMOTTA-228 (Switch to Bootstrap the admin markup) is
>> blocking several tasks related with the admin ui. So we must discuss
>> what's missing in that topic branch, and if such major refactoring could
>> go in this release.
>>
>> Cheers,
>>
>
> --
> Sergio Fernández

Re: local import feature

[Jakob Frank]

Hi all,

my idea of a "config-file" for the local import was the following;

By default:
files in MARMOTTA_HOME/import are imported into the default context
files in MARMOTTA_HOME/import/foo/bar are imported into context
BASE_URI/context/foo/bar

The above default setting can be overwritten on a _per directory_ base
by placing a "config-file" into a folder, e.g.
for MARMOTTA_HOME/import/foobar/ - if it contains a file, say
".context", containing "http://example.com/context/"; in the first
line, all files placed into this directory will be imported into
context http://example.com/context/

I'd like to avoid a round-trip between file-system and the
configuration, as it complicates the workflow:
1) create directory structure in MARMOTTA_HOME
2) configure context in the admin-ui
3) copy files to the directory

What I don't like with the url-encoded-directory names is that it
requires the detection of absolute URIs vs. relative URIs for contexts
to be hard coded.

Best,
Jakob

On 30 August 2013 10:16, Raffaele Palmieri  wrote:
> Hi Sergio,
> I think that configuration file may not be necessary for the moment coming
> easily to implementation, but Jakob's idea is good for providing mapping
> between rdf data files and fully URIs of contexts and extensible to other
> future options.
> So I would implement the procedure preparing to read a config file that
> overwrites default options(local subpath of import directories), if see
> also Marmotta-296 about import of compressed files, the order of importing
> could be important and config file could help to establish it.
> Cheers,
> Raffaele.
>
>
> On 29 August 2013 17:55, Sergio Fernández  wrote:
>
>> Hi,
>>
>> until now, all import options for data in Marmotta were going through the
>> import web service, which is quite flexible and allow us to import data
>> from different scenarios (admin ui, client library, custom calls with curl
>> or whatever, and so on). But, of course, it has the inherited overhead from
>> HTTP. Therefore local import feature (MARMOTTA-145 [1]) was on my wish list
>> for quite long time... And according my experiments the performance is a
>> big step forward.
>>
>> Finally this week I've found some time to implement it, and it's already
>> available in the develop branch, and in the latest maven snapshots. On the
>> wiki you could find some more information how it works [2]; but basically
>> Marmotta is watching a local directory, where it imports all the files
>> copied there. I've already collected some interesting features (target
>> context names [3][4] and compressed files [5]) and bugs (importing at boot
>> time [6][7]).
>>
>> Regarding one of this features (MARMOTTA-293: support fully qualified
>> context names importing locally), I'd like to ask the marmotta community
>> what option would be preferable for you. Basically in a coffee break I
>> discussed it with Jakob, and he suggests to make use of a config file for
>> such things; but personally I'd prefer to make it simpler, for instance
>> just using a url-encoded directory name for those cases. But I'd like to
>> listen other opinion before implement it; any other opinion? Ideas would be
>> welcomed ;-)
>>
>> Cheers,
>>
>> [1] 
>> https://issues.apache.org/**jira/browse/MARMOTTA-145
>> [2] http://wiki.apache.org/**marmotta/ImportData#Import_**
>> data_via_the_local_directory
>> [3] 
>> https://issues.apache.org/**jira/browse/MARMOTTA-291
>> [4] 
>> https://issues.apache.org/**jira/browse/MARMOTTA-293
>> [5] 
>> https://issues.apache.org/**jira/browse/MARMOTTA-296
>> [6] 
>> https://issues.apache.org/**jira/browse/MARMOTTA-294
>> [7] 
>> https://issues.apache.org/**jira/browse/MARMOTTA-295
>> --
>> Sergio Fernández
>>

[jira] [Commented] (MARMOTTA-296) Support compressed files in the local import

[Jakob Frank (JIRA)]

[ 
https://issues.apache.org/jira/browse/MARMOTTA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753814#comment-13753814
 ] 

Jakob Frank commented on MARMOTTA-296:
--

Why only for local imports? Would be as useful if the WebServices support it.

Maybe something worth to be contributed to Sesame?

> Support compressed files in the local import
> 
>
> Key: MARMOTTA-296
> URL: https://issues.apache.org/jira/browse/MARMOTTA-296
> Project: Marmotta
>  Issue Type: Improvement
>  Components: Platform
>Affects Versions: 3.1-incubating
>Reporter: Sergio Fernández
>Assignee: Sergio Fernández
>Priority: Minor
> Fix For: 3.1-incubating
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Jakob suggests to add support to compressed files (zip, gz and so on), which 
> should not be so difficult.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-66) Rework sesame-commons ResourceUtils

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-66.
-

Resolution: Fixed
  Assignee: Sebastian Schaffert  (was: Jakob Frank)

kudos to Sebastian ;-)

> Rework sesame-commons ResourceUtils
> ---
>
> Key: MARMOTTA-66
> URL: https://issues.apache.org/jira/browse/MARMOTTA-66
> Project: Marmotta
>  Issue Type: Bug
>  Components: Sesame Tools
>Affects Versions: 2.6
>    Reporter: Jakob Frank
>Assignee: Sebastian Schaffert
> Fix For: 3.1-incubating
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> ResourceUtils contains a number of useful convenience methods. But many of 
> the do not really do what they promise or do not handle the connection as 
> they should.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-292) Update Codemirror to version 3.x

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-292:


 Summary: Update Codemirror to version 3.x
 Key: MARMOTTA-292
 URL: https://issues.apache.org/jira/browse/MARMOTTA-292
 Project: Marmotta
  Issue Type: Improvement
  Components: Extras
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Sergio Fernández


The Codemirror webjar should be updated to the latest Codemirror version 
(currently 3.16)

Check for API changes and adapt ldpath and skwrl modes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-220) CM plugin for the (s)kwrl reasoning language

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-220.
--

Resolution: Implemented

skwrl-mode for codemirror implemented

> CM plugin for the (s)kwrl reasoning language
> 
>
> Key: MARMOTTA-220
> URL: https://issues.apache.org/jira/browse/MARMOTTA-220
> Project: Marmotta
>  Issue Type: New Feature
>  Components: Admin Interface, Triple Store
>    Reporter: Jakob Frank
>    Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>   Original Estimate: 12h
>  Time Spent: 2.25h
>  Remaining Estimate: 0h
>
> It would be nice to have syntax-highlighting for the kiwi reasoning language 
> in CodeMirror.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-219) CM-Plugin for LDPath sould support comments

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-219.
--

Resolution: Implemented

support for comments added

> CM-Plugin for LDPath sould support comments
> ---
>
> Key: MARMOTTA-219
> URL: https://issues.apache.org/jira/browse/MARMOTTA-219
> Project: Marmotta
>  Issue Type: Improvement
>  Components: Admin Interface, LDPath
>Affects Versions: 3.0-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>   Original Estimate: 2h
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> since 3.0, LDPath supports comments. This should be reflected in the 
> ldpath-language definition for codemirror

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-242) LdPath Templating shoud set default output-encoding

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-242.
--

   Resolution: Fixed
Fix Version/s: 3.1-incubating

> LdPath Templating shoud set default output-encoding
> ---
>
> Key: MARMOTTA-242
> URL: https://issues.apache.org/jira/browse/MARMOTTA-242
> Project: Marmotta
>  Issue Type: Bug
>  Components: LDPath
>Affects Versions: 3.0-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.1-incubating
>
>   Original Estimate: 2h
>  Time Spent: 0.25h
>  Remaining Estimate: 0h
>
> Some built-in functions of freemarker need the output-encoding set, this 
> should be done by the framework embedding freemarker.
> see 
> http://freemarker.sourceforge.net/docs/ref_builtins_string.html#ref_builtin_url
> as a workaround one can set the encoding explicitly in the template using
> <#setting url_escaping_charset="UTF-8">

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-282) Hidden Time-Zone effect during RDF Import

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-282.
--

Resolution: Fixed
  Assignee: Jakob Frank  (was: Sebastian Schaffert)

> Hidden Time-Zone effect during RDF Import
> -
>
> Key: MARMOTTA-282
> URL: https://issues.apache.org/jira/browse/MARMOTTA-282
> Project: Marmotta
>  Issue Type: Bug
>  Components: Platform
>Affects Versions: 3.0-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Critical
>
> I imported a really simple turtle file - and somehow during import all 
> xsd:dateTime Literals where changed:
> (Local timezone is CEST, which is UTC+2)
> Imported
> local:1234 dct:created "2013-08-01T00:00:00.000Z"^^xsd:dateTime .
> Linked Data Explorer shows:
> dct:created   "2013-07-31T22:00:00.000Z"^^xsd:dateTime
> curl -H "Accept: text/turtle" http://localhost:8080/resource/1234 shows:
> local:1234 dct:created "2013-07-31T22:00:00.000Z"^^xsd:dateTime .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (MARMOTTA-285) Implement/Integrate Sesame SPARQL Testsuite into KiWi

[Jakob Frank (JIRA)]

[ 
https://issues.apache.org/jira/browse/MARMOTTA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748354#comment-13748354
 ] 

Jakob Frank commented on MARMOTTA-285:
--

The manifest-test are on my list, but i did not yet see how they should be 
implemented.

As for the sesame-store-testsuite: I'm already working on that (MARMOTTA-287)

> Implement/Integrate Sesame SPARQL Testsuite into KiWi
> -
>
> Key: MARMOTTA-285
> URL: https://issues.apache.org/jira/browse/MARMOTTA-285
> Project: Marmotta
>  Issue Type: Bug
>  Components: Triple Store
>Reporter: Jakob Frank
>Assignee: Sebastian Schaffert
>  Labels: sesame, sparql, test
>
> Sesame has a nice test suite for the SPARQL Implementation - to ensure 
> conformance of our local optimizations.
> https://bitbucket.org/openrdf/sesame/src/2de4dce36fb2b8c577581146b534525d3f6c12a0/testsuites/sparql/
> 
> org.openrdf.sesame
> sesame-sparql-testsuite
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-287) Implement/Integrate Sesame Store Testsuite into KiWi

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-287:


 Summary: Implement/Integrate Sesame Store Testsuite into KiWi
 Key: MARMOTTA-287
 URL: https://issues.apache.org/jira/browse/MARMOTTA-287
 Project: Marmotta
  Issue Type: Test
  Components: Triple Store
Reporter: Jakob Frank
Assignee: Sebastian Schaffert


Sesame has a nice test suite for store implementations:

https://bitbucket.org/openrdf/sesame/src/983edfccb2306977d0eae61dac3a5cd0c9ffe851/testsuites/store?at=master


org.openrdf.sesame
sesame-store-testsuite


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-286) Update KiWi TripleStore to RDF1.1

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-286:


 Summary: Update KiWi TripleStore to RDF1.1
 Key: MARMOTTA-286
 URL: https://issues.apache.org/jira/browse/MARMOTTA-286
 Project: Marmotta
  Issue Type: Improvement
  Components: Triple Store
Reporter: Jakob Frank
Assignee: Sebastian Schaffert


Once Sesame has updated the RDF Model to RDF-1.1, the KiWi Triplestore should 
also update to RDF1.1

http://www.w3.org/TR/rdf11-concepts/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-285) Implement/Integrate Sesame SPARQL Testsuite into KiWi

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-285:


 Summary: Implement/Integrate Sesame SPARQL Testsuite into KiWi
 Key: MARMOTTA-285
 URL: https://issues.apache.org/jira/browse/MARMOTTA-285
 Project: Marmotta
  Issue Type: Bug
  Components: Triple Store
Reporter: Jakob Frank
Assignee: Sebastian Schaffert


Sesame has a nice test suite for the SPARQL Implementation - to ensure 
conformance of our local optimizations.

https://bitbucket.org/openrdf/sesame/src/2de4dce36fb2b8c577581146b534525d3f6c12a0/testsuites/sparql/


org.openrdf.sesame
sesame-sparql-testsuite


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-284) Database Error during SPARQL Update

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-284:


 Summary: Database Error during SPARQL Update
 Key: MARMOTTA-284
 URL: https://issues.apache.org/jira/browse/MARMOTTA-284
 Project: Marmotta
  Issue Type: Bug
  Components: Triple Store
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
Priority: Critical


Found this in the logfile (wrong format for the date?):

15:11:29.278 ERROR o.a.m.kiwi.sail.KiWiSailConnection - Could not persist 
rdf-statement (http://localhost:8080/resource/TeLItTFu http://p
url.org/dc/terms/modified 
"2013-08-21T15:11:19"^^<http://www.w3.org/2001/XMLSchema#dateTime>)
org.postgresql.util.PSQLException: ERROR: insert or update on table "triples" 
violates foreign key constraint "triples_object_fkey"
  Detail: Key (object)=(1711802) is not present in table "nodes".
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
 ~[postgresql-9.2-1002-jdbc4.jar:na]
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
 ~[postgresql-9.2-1002-jdbc4.jar:na]
at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) 
~[postgresql-9.2-1002-jdbc4.jar:na]
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
 ~[postgresql-9.2-1002-jdbc4.jar:na]
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
 ~[postgresql-9.2-1002-jdbc4.jar:na]
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:363)
 ~[postgresql-9.2-1002-jdbc4.jar:na]
at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) ~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.6.0_27]
at java.lang.reflect.Method.invoke(Method.java:616) ~[na:1.6.0_27]
at 
org.apache.tomcat.jdbc.pool.interceptor.AbstractQueryReport$StatementProxy.invoke(AbstractQueryReport.java:235)
 ~[tomcat-jdbc-7.0.3
7.jar:na]
at sun.proxy.$Proxy130.executeUpdate(Unknown Source) ~[na:na]
at 
org.apache.marmotta.kiwi.persistence.KiWiConnection.storeTriple(KiWiConnection.java:946)
 ~[kiwi-triplestore-3.0.0-incubating.jar:3.
0.0-incubating]
at 
org.apache.marmotta.kiwi.sail.KiWiSailConnection.addStatementInternal(KiWiSailConnection.java:168)
 [kiwi-triplestore-3.0.0-incubati
ng.jar:3.0.0-incubating]
at 
org.apache.marmotta.kiwi.sail.KiWiSailConnection.addStatementInternal(KiWiSailConnection.java:114)
 [kiwi-triplestore-3.0.0-incubati
ng.jar:3.0.0-incubating]
at 
org.openrdf.sail.helpers.SailConnectionBase.addStatement(SailConnectionBase.java:441)
 [sesame-sail-api-2.7.0-beta2.jar:na]
at 
org.openrdf.sail.helpers.SailConnectionBase.endUpdate(SailConnectionBase.java:548)
 [sesame-sail-api-2.7.0-beta2.jar:na]
at 
org.openrdf.sail.helpers.SailConnectionWrapper.endUpdate(SailConnectionWrapper.java:169)
 [sesame-sail-api-2.7.0-beta2.jar:na]
at 
org.openrdf.sail.helpers.SailConnectionWrapper.endUpdate(SailConnectionWrapper.java:169)
 [sesame-sail-api-2.7.0-beta2.jar:na]
at 
org.openrdf.repository.sail.helpers.SailUpdateExecutor.executeUpdate(SailUpdateExecutor.java:157)
 [sesame-repository-sail-2.7.0-bet
a2.jar:na]
at org.openrdf.repository.sail.SailUpdate.execute(SailUpdate.java:91) 
[sesame-repository-sail-2.7.0-beta2.jar:na]
at 
org.apache.marmotta.platform.sparql.services.sparql.SparqlServiceImpl.update(SparqlServiceImpl.java:290)
 [marmotta-sparql-3.0.0-inc
ubating.jar:3.0.0-incubating]
at 
org.apache.marmotta.platform.sparql.services.sparql.SparqlServiceImpl$Proxy$_$$_WeldClientProxy.update(SparqlServiceImpl$Proxy$_$$_WeldClientProxy.java)
 [marmotta-sparql-3.0.0-incubating.jar:3.0.0-incubating]
at 
org.apache.marmotta.platform.sparql.webservices.SparqlWebService.updatePostDirectly(SparqlWebService.java:405)
 [marmotta-sparql-3.0.0-incubating.jar:3.0.0-incubating]
at 
org.apache.marmotta.platform.sparql.webservices.SparqlWebService$Proxy$_$$_WeldClientProxy.updatePostDirectly(SparqlWebService$Proxy$_$$_WeldClientProxy.java)
 [marmotta-sparql-3.0.0-incubating.jar:3.0.0-incubating]
at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source) 
~[na:na]
...
15:11:29.676 WARN  o.openrdf.repository.sail.SailUpdate - exception during 
update execution: 
org.openrdf.sail.SailException: database error while storing statement
at 
org.apache.marmotta.kiwi.sail.KiWiSailConnection.addStatementInternal(KiWiSailConnection.java:187)
 ~[kiwi-triplestore-3.0.0-incubating.jar:3.0.0-incubating]
at 
org.apache.marmotta.kiwi.sail.KiWiSailConnection.addStatementInternal(KiWiSailConnection.java:114)

Re: RDF-patch : doc updated

[Jakob Frank]

Hi Andy, all

I had a quick look through the document - and overall I like the clean
and simple approach of the proposed format.

Here are my first comments:
- HTTP PATCH targets a resource - IMHO it should be allowed that the
server limits changes to this addressed resource. (the illustrative
example in the doc modifies two resources)

- if you continue the resource-centered approach, you could allow to
skip the subject in the patch file. (but then: how to distinguish
between POC and SPO statements?)

- what about allowing wildcards for deletion? e.g.
D  foaf:name ?x .
to delete all foaf:names for ex:bob

- is the ordering of the statements significant? i.e. what is the
result of the following patch:
D    .
A    .
is it different to the result of
A    .
D    .


Best,
Jakob

On 12 August 2013 11:23, Andy Seaborne  wrote:
> On 11/08/13 18:07, Andy Seaborne wrote:
>>
>> Rob, all,
>
>
> Wrong dev@ :-(
>
> But your welcome to comment and make suggestions :-)
>
> The doc is:
>
> http://afs.github.io/rdf-patch/
>
> Andy
>
>
>>
>> I've made some changes : I've moved the discussion of features to an
>> appendix and added some possibilities for some of these items.
>>
>> http://afs.github.io/rdf-patch/#notes
>>
>>  A.1 Line Mode
>>  A.2 Metadata
>>  A.2.1 Linking
>>  A.2.2 Inline
>>  A.3 Transaction Boundaries
>>  A.4 Alternative Blank Node Syntax
>>  A.5 Alignment Errors
>>  A.6 Binary Format
>>
>> - - - - -
>>
>> Prompted by
>> https://twitter.com/pdxleif/status/366267325818736640
>>
>> Where should we encourage discussion in going to a wider audience?
>>
>> One possibility is github, using the issues area of the git repo .  But
>> you have to know where to look and the semweb world is still quite
>> mailing-list driven.
>>
>> public-sparql-...@w3.org makes some sense (it's not a high volume list).
>>   Other more general lists like semantic-...@w3.org have their pros and
>> cons.
>>
>>  Andy
>
>

[jira] [Created] (MARMOTTA-282) Hidden Time-Zone effect during RDF Import

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-282:


 Summary: Hidden Time-Zone effect during RDF Import
 Key: MARMOTTA-282
 URL: https://issues.apache.org/jira/browse/MARMOTTA-282
 Project: Marmotta
  Issue Type: Bug
  Components: Platform
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
Priority: Critical


I imported a really simple turtle file - and somehow during import all 
xsd:dateTime Literals where changed:

(Local timezone is CEST, which is UTC+2)

Imported
local:1234 dct:created "2013-08-01T00:00:00.000Z"^^xsd:dateTime .

Linked Data Explorer shows:
dct:created "2013-07-31T22:00:00.000Z"^^xsd:dateTime

curl -H "Accept: text/turtle" http://localhost:8080/resource/1234 shows:
local:1234 dct:created "2013-07-31T22:00:00.000Z"^^xsd:dateTime .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-277) Fix the Monitoring (Task) Service

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-277:


 Summary: Fix the Monitoring (Task) Service
 Key: MARMOTTA-277
 URL: https://issues.apache.org/jira/browse/MARMOTTA-277
 Project: Marmotta
  Issue Type: Bug
  Components: Platform
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
 Fix For: 3.1-incubating


In some installations, the current tasks list in the admin-ui is filled up with 
entries that are no longer valid (i.e. tasks that are already finished)

Now i found the following stacktrace in tomcat's localhost.log:
Jul 23, 2013 4:40:49 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [default] in context with path [] threw 
exception
org.jboss.resteasy.spi.UnhandledException: 
java.util.ConcurrentModificationException
at 
org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:365)
at 
org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:233)
at 
org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:209)
at 
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:557)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invokePropagateNotFound(SynchronousDispatcher.java:169)
at 
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:212)
at 
org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:59)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:186)
at 
org.apache.marmotta.platform.core.filters.ModuleResourceFilter.doFilter(ModuleResourceFilter.java:163)
at 
org.apache.marmotta.platform.core.filters.ModuleResourceFilter$Proxy$_$$_WeldClientProxy.doFilter(ModuleResourceFilter$Proxy$_$$_We
ldClientProxy.java)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:181)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:183)
at 
org.apache.marmotta.platform.core.filters.MarmottaServerNameFilter.doFilter(MarmottaServerNameFilter.java:104)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:181)
at 
org.apache.marmotta.platform.core.filters.TemplatingFilter.doFilter(TemplatingFilter.java:176)
at 
org.apache.marmotta.platform.core.filters.TemplatingFilter$Proxy$_$$_WeldClientProxy.doFilter(TemplatingFilter$Proxy$_$$_WeldClient
Proxy.java)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:181)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:183)
at 
org.apache.marmotta.platform.security.filters.MarmottaAccessControlFilter.doFilter(MarmottaAccessControlFilter.java:142)
at 
org.apache.marmotta.platform.security.filters.MarmottaAccessControlFilter$Proxy$_$$_WeldClientProxy.doFilter(MarmottaAccessControlF
ilter$Proxy$_$$_WeldClientProxy.java)
at 
org.apache.marmotta.platform.core.servlet.MarmottaResourceFilter$LMFFilterChain.doFilter(MarmottaResourceFilter.java:181)
at 
org.apache.marmotta.platform.user.filters.MarmottaAuthenticationFilter.doFilter(MarmottaAuthenticationFilter.java:163)
at 
org.apache.marmotta.platform.user.filters.MarmottaAuthenticationFilter$Proxy$_$$_WeldClientProxy.doFilter(MarmottaAuthenticationFil
ter$Proxy$_$$_WeldClientProxy.java)
[...]
Caused by: java.util.ConcurrentModificationException
at java.util.WeakHashMap$HashIterator.nextEntry(WeakHashMap.java:784)
at java.util.WeakHashMap$ValueIterator.next(WeakHashMap.java:811)
at 
org.apache.marmotta.platform.core.services.task.TaskManagerServiceImpl.getTasks(TaskManagerServiceImpl.java:99)
at 
org.apache.marmotta.platform.core.services.task.TaskManagerServiceImpl.getTasksByGroup(TaskManagerServiceImpl.java:182)
at 
org.apache.marmotta.platform.core.services.task.TaskManagerServiceImpl$Proxy$_$$_WeldClientProxy.getTasksByGroup(TaskManagerServiceImpl$Proxy$_$$_WeldClientProxy.java)
 

[jira] [Created] (MARMOTTA-275) SPARQL Query Form in Admin-UI is using wrong server address

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-275:


 Summary: SPARQL Query Form in Admin-UI is using wrong server 
address
 Key: MARMOTTA-275
 URL: https://issues.apache.org/jira/browse/MARMOTTA-275
 Project: Marmotta
  Issue Type: Bug
  Components: Admin Interface
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Thomas Kurz
 Fix For: 3.1-incubating


In the Admin-UI we have global javascript variables for base-URL/-URI of the 
installation:

_BASIC_URL which is the base URI for local (RDF-)resources on the server
_SERVER_URL which is the base URL to access the different webservices.

In many (most?) cases these two variables have the same value.

But sometimes not, and SNORQL is using the wrong one (should be _SERVER_URL)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: LDP is planning to go to Last Call soon

[Jakob Frank]

Hi all,

these are my first comments, after I had a quick look into the draft [1]:

* LDP declares dct:modified and dct:creator as (optionally)
server-controlled (managed) properties. The dct-vocabulary is
wide-spread and used in many applications, declaring it managed will
break many of them. There is a ldp-vocabulary, why not use
ldp:modified / ldp:creator for this purpose? [Section 4.4]
* for paging (cool feature!), LDP defines links to the next page using
ldp:nextPage (and a corresponding HTTP Link-Header) to indicate the
URI of the next page. Is there a reason not to also include the links
ldp:prevPage, ldp:firstPage, ldp:lastPage? [Section 4.9]
* for a non-LDPR POSTed to the LDP server, the server may create a
corresponding LDPR. The non-LDPR may Link (HTTP-Header) to it's
associated LDPR using the "meta"-relation - why not add the also an
inverse Link (HTTP Header) using e.g. the "content"-relation? [Section
5.4]
* my general impression is that in several places (especially with
paging [Section 4.9] and inlining [Sections 4.10 and 5.10]) server
responses mix data and request-specific meta-data (e.g. navigation
links with paging, etc...). I have no alternative proposal but still
this feels somehow "soiled" (sorry, did not find a better wording).

Probably these issues were discussed lengthily in the WG, maybe
someone more involved there can share some insights?

Best
Jakob

[1] - https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html


On 17 July 2013 16:20, Sergio Fernández  wrote:
> Hi Nandana,
>
>
> On 17/07/13 16:13, Nandana Mihindukulasooriya wrote:
>>
>> As of this week's telecon [1], LDP WG is planning to go for the last call
>> on 7/22 and there are some significant changes in the spec after F2F3.
>> This
>> week is for the WG members to do their final reviews. It might be a good
>> time for Marmotta devs to have a look at the spec draft [2] and see how it
>> fits Marmotta.
>
>
> I created MARMOTTA-272 exactly with that purpose. My problem in last weeks
> is the time. But for sure we should provide feedback to the spec as a
> project.
>
> If you want, we can collect there the notes, trying to provide proper
> feedback.
>
> Cheers,
>
> --
> Sergio Fernández

Re: planning 3.1.0-incubating release

[Jakob Frank]

+1

we'll spin another round for an IRC-meeting for the release-planning
in September.

Best
Jakob

On 17 July 2013 09:00, Sergio Fernández  wrote:
> I guess would be better to delay this until September when all will be back
> from holidays... what do you think?
> I the meantime, continue working as normal.
>
>
> On 12/07/13 20:57, Sergio Fernández wrote:
>>
>> not so many people have voted in the doodle...
>> http://doodle.com/tbxe8aikq7sg7yf6
>> for the moment Monday at 9 or 10 (UTC) looks to be the most popular
>> option, but three of us is not enough to clearly say so
>> would be great to meet and discuss about the following release
>> otherwise I guess we should think about delay it until being back of
>> vacations in September...
>>
>> On 03/07/13 17:51, Jakob Frank wrote:
>>>
>>> What about having an IRC-meeting to go through the issues and decide what
>>> should go into 3.1 and what could be moved to 3.2.
>>>
>>> We have developers in quite different timezones (UTC+1, UTC+2 and UTC+10
>>> are the ones I know about) - so it might be not so easy to find a common
>>> time-slot but we should try:
>>>
>>> So please pick your preferred time slots for an IRC meeting (all times in
>>> UTC!):
>>> http://doodle.com/tbxe8aikq7sg7yf6
>>>
>>> Best,
>>> Jakob
>>>
>>> On 3 July 2013 12:46, Sergio Fernández  wrote:
>>>>
>>>> Hi,
>>>>
>>>> yesterday Jakob and me we were talking about the possibility to plan the
>>>> next release by the end of July 2013. I think we have made an important
>>>> progress in many parts of the project, but we should try to reflect
>>>> those
>>>> things as releases.
>>>>
>>>> Taking a quick look into our issue tracker:
>>>>
>>>>
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MARMOTTA%20AND%20fixVersion%20%3D%20%223.1-incubating%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
>>>
>>>>
>>>> Currently there are 55 issues planner for that version. For me it's
>>>> quite
>>>> clear that we would need to prioritize some of them, and shift some to
>>>
>>> 3.2.
>>>>
>>>> So I think all current assignees should decide what to do with their
>>>
>>> issues
>>>>
>>>> by 3.1.0, trying to balance priority and the time they would have to
>>>> take
>>>> care of those issue.
>>>>
>>>> What do you think? Would be feasible?
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Sergio Fernández
>>>
>>>
>>
>
> --
> Sergio Fernández

[jira] [Resolved] (MARMOTTA-197) ldpath is loosing brackets on re-serialisation

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-197.
--

   Resolution: Fixed
Fix Version/s: 3.1-incubating

fixed in 7df9f1d36285767a8d987f509414cd7881e478aa

> ldpath is loosing brackets on re-serialisation
> --
>
> Key: MARMOTTA-197
> URL: https://issues.apache.org/jira/browse/MARMOTTA-197
> Project: Marmotta
>  Issue Type: Bug
>  Components: LDPath
>Affects Versions: 3.0-incubating
>Reporter: Dietmar Glachs
>Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>   Original Estimate: 0.5h
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Sending the following ldpath statement
> … doc:hasRelatedConcept[ ( (skos:broader)* / skos:topConceptOf ) is 
> <http://example.com/foo>] … 
> works fine, but after re-serialisation the result is
> … doc:hasRelatedConcept[(skos:broader)* / skos:topConceptOf is 
> <http://example.com/foo>]… 
> which is not a valid ldpath statement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-240) MediaWiki provider is not detecting all redirects.

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-240.
--

   Resolution: Fixed
Fix Version/s: (was: 3.0-incubating)

Was fixed in 58c3b5cd587f4d44d41b626124fdf3fc82f7b909

> MediaWiki provider is not detecting all redirects.
> --
>
> Key: MARMOTTA-240
> URL: https://issues.apache.org/jira/browse/MARMOTTA-240
> Project: Marmotta
>  Issue Type: Bug
>  Components: LDClient
>Affects Versions: 3.0-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Minor
> Fix For: 3.1-incubating
>
>   Original Estimate: 10m
>  Time Spent: 5m
>  Remaining Estimate: 5m
>
> Should be quite simple, in MediawikiProvider:75, in the regex replace \s+ by 
> \s*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-221) ldpath is loosing quotes for StringConstants on re-serialisation

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-221.
--

   Resolution: Fixed
Fix Version/s: (was: 3.0-incubating)

Was resolved some time ago

> ldpath is loosing quotes for StringConstants on re-serialisation
> 
>
> Key: MARMOTTA-221
> URL: https://issues.apache.org/jira/browse/MARMOTTA-221
> Project: Marmotta
>  Issue Type: Bug
>  Components: LDPath
>Affects Versions: 3.0-incubating
>    Reporter: Jakob Frank
>Assignee: Jakob Frank
>Priority: Critical
> Fix For: 3.1-incubating
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Tested with:
> title_en = dct:hasVersion[dct:language is "en"]/dct:title :: xsd:string;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (MARMOTTA-273) Implement string equals functioninality

[Jakob Frank (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MARMOTTA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Frank resolved MARMOTTA-273.
--

   Resolution: Fixed
Fix Version/s: 3.1-incubating

implemented

> Implement string equals functioninality
> ---
>
> Key: MARMOTTA-273
> URL: https://issues.apache.org/jira/browse/MARMOTTA-273
> Project: Marmotta
>  Issue Type: New Feature
>  Components: LDPath
>Reporter: Thomas Kurz
>    Assignee: Jakob Frank
> Fix For: 3.1-incubating
>
>  Time Spent: 3.7h
>  Remaining Estimate: 0h
>
> It it often useful, to filter based on string similarity. Such a filter 
> filter could look like this:
> @filter fn:eq(fn:substr(dct:identifier,"0","4"), "myid") ;
> Therefore a fn.eq for strings is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (MARMOTTA-273) Implement string equals functioninality

[Jakob Frank (JIRA)]

[ 
https://issues.apache.org/jira/browse/MARMOTTA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709749#comment-13709749
 ] 

Jakob Frank commented on MARMOTTA-273:
--

to avoid name-clashes, the new function will be called fn:equals

> Implement string equals functioninality
> ---
>
> Key: MARMOTTA-273
> URL: https://issues.apache.org/jira/browse/MARMOTTA-273
> Project: Marmotta
>  Issue Type: New Feature
>  Components: LDPath
>Reporter: Thomas Kurz
>Assignee: Jakob Frank
>
> It it often useful, to filter based on string similarity. Such a filter 
> filter could look like this:
> @filter fn:eq(fn:substr(dct:identifier,"0","4"), "myid") ;
> Therefore a fn.eq for strings is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: planning 3.1.0-incubating release

[Jakob Frank]

What about having an IRC-meeting to go through the issues and decide what
should go into 3.1 and what could be moved to 3.2.

We have developers in quite different timezones (UTC+1, UTC+2 and UTC+10
are the ones I know about) - so it might be not so easy to find a common
time-slot but we should try:

So please pick your preferred time slots for an IRC meeting (all times in
UTC!):
http://doodle.com/tbxe8aikq7sg7yf6

Best,
Jakob

On 3 July 2013 12:46, Sergio Fernández  wrote:
> Hi,
>
> yesterday Jakob and me we were talking about the possibility to plan the
> next release by the end of July 2013. I think we have made an important
> progress in many parts of the project, but we should try to reflect those
> things as releases.
>
> Taking a quick look into our issue tracker:
>
>
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MARMOTTA%20AND%20fixVersion%20%3D%20%223.1-incubating%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
>
> Currently there are 55 issues planner for that version. For me it's quite
> clear that we would need to prioritize some of them, and shift some to
3.2.
> So I think all current assignees should decide what to do with their
issues
> by 3.1.0, trying to balance priority and the time they would have to take
> care of those issue.
>
> What do you think? Would be feasible?
>
> Cheers,
>
> --
> Sergio Fernández

Re: Incubator PMC/Board report for Jul 2013 ([ppmc])

[Jakob Frank]

I would rephrase the "How did X develop" sections the following way:

How has the community developed since the last report?

  * dev@marmotta.i.a.o continues with high traffic but slightly
decreasing: Apr. 265, May 161, Jun. 137. We expect the numbers to
raise again with the preparation of the next release.
  * Two new persons have been elected as new committer and PPMC
members: Raffaele Palmieri (Eustema Spa) on May 21st, 2013, and Peter
Ansell (University of Queensland) on Jun 24th, 2013.

How has the project developed since the last report?

  * The first release (3.0.0-incubating) has been published on April
24th, 2013. Since that the project is actively working of different
improvements, bug fixes and new features, registering 266 issues at
jira (60% resolved).
  * The next release (3.1.0-incubation) is planned for the upcoming
weeks 
(http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201307.mbox/%3C51D40104.3060203%40apache.org%3E).
  * The first two most important issues the project targets to move
towards graduation have been already achieved; and the third one, dev
community, is being addressed too. Therefore the project has already
started to discuss about such option
(http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201305.mbox/%3C51A35FFA.2070707%40apache.org%3E).

Date of last release: April 24th, 2013.



Best,
Jakob

On 3 July 2013 14:41, Sergio Fernández
 wrote:
> On 03/07/13 12:19, Andy Seaborne wrote:
>>
>> I was asking for a link to the "planned for the the upcoming
>> weeks"
>
>
> Right, Good point. Now we have such link:
>
> http://mail-archives.apache.org/mod_mbox/incubator-marmotta-dev/201307.mbox/%3C51D40104.3060203%40apache.org%3E
>
> The report has been submitted to the IPMC:
>
> https://wiki.apache.org/incubator/July2013
>
> and it'd ready to be sign by our mentors.
>
> Thanks for your contributions to the report.
>
> Cheers,
>
> --
> Sergio Fernández
> Salzburg Research
> +43 662 2288 318
> Jakob-Haringer Strasse 5/II
> A-5020 Salzburg (Austria)
> http://www.salzburgresearch.at

[WELCOME] Please welcome Peter Ansell as new committer and PPMC member

[Jakob Frank]

Dear Marmotta Community,

the Apache Marmotta PPMC has voted for adding Peter Ansell as a new
committer and PPMC member.

Peter, we are glad to have you on board, welcome!

Best,
Jakob

Re: [POLL] context vs. graph vs. ...

[Jakob Frank]

>>>  for the moment +1 for graph.
>> Good; thanks for your opinion on this.
> My vote for "graph" depends on the fact that in Marmotta "context" has a
> different meaning than "container", and so "graph" is the only good
> alternative.
why does context != container rule out context?

AFAIU, this thread is about finding a common name for x for  quadruples, and so far we do not have the concept of
(LDP)containers in marmotta.

Best,
Jakob

Re: [POLL] context vs. graph vs. ...

[Jakob Frank]

+1 for raising this issue.

I'm happy with both, "context" and "graph" (with a slight preference
for "context" as this is the term used in the Sesame API)

namedGraph, quad, kspace, etc... I don't like...

Best
Jakob

On 4 June 2013 18:33, Sergio Fernández  wrote:
> Hi,
>
> in Marmotta we inherited from the underlined RDF API (Sesame OpenRDF) the
> term "context" for referring to triple containers with their own URI.
>
> There are several other terms for referring same thing: graph, named graph,
> quad, etc; actually in the former KiWi were known as "knowledge spaces".
> Moreover we have a terminology issue with the statement @context in LDPath.
>
> So, since we are still in the moment where such core concepts could be
> renamed, do you thing we should do it?
>
> Personally I'd be happy to switch to graph, but I'm also fine with the
> current term.
>
> Thanks in advance for your comments.
>
> Cheers,
>
> --
> Sergio Fernández

Jenkins disabled

[Jakob Frank]

Since we're currently getting flooded by the jenkins server, I
disabled the notifications to the mailinglist for now.

Sergio and me will look into the configuration again and then enable
the notifications again.

Best
Jakob

[jira] [Created] (MARMOTTA-243) Fix JRebel configuration

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-243:


 Summary: Fix JRebel configuration
 Key: MARMOTTA-243
 URL: https://issues.apache.org/jira/browse/MARMOTTA-243
 Project: Marmotta
  Issue Type: Bug
  Components: Build Environment
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Sebastian Schaffert
Priority: Critical


the generation of the rebel.xml is broken (rebel-root is not correctly set)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (MARMOTTA-242) LdPath Templating shoud set default output-encoding

[Jakob Frank (JIRA)]

Jakob Frank created MARMOTTA-242:


 Summary: LdPath Templating shoud set default output-encoding
 Key: MARMOTTA-242
 URL: https://issues.apache.org/jira/browse/MARMOTTA-242
 Project: Marmotta
  Issue Type: Bug
  Components: LDPath
Affects Versions: 3.0-incubating
Reporter: Jakob Frank
Assignee: Jakob Frank
Priority: Minor


Some built-in functions of freemarker need the output-encoding set, this should 
be done by the framework embedding freemarker.

see 
http://freemarker.sourceforge.net/docs/ref_builtins_string.html#ref_builtin_url

as a workaround one can set the encoding explicitly in the template using
<#setting url_escaping_charset="UTF-8">

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira