Summary of IRC meeting in #apachemarmotta, Tue Feb 5 09:12:34 2013

[ASF IRC Services <as...@wilderness.apache.org>]

Members present: wastl, tkurz, westei, wikier

----------------
Meeting summary:
----------------

1. Preface

2. reasoning

3. logo
  a. check in final logo sources (bitmap and vector) to SVN and add comment to Jira about the donation (wastl, 3)

4. ldp
  a. http://code.google.com/p/rest-assured/ (wastl, 4)
  b. https://dvcs.w3.org/hg/ldpwg/file/39114b935c70/tests/basic (wikier, 4)

5. memento
  a. http://www.mementoweb.org/ (wastl, 5)
  b. http://www.mementoweb.org/guide/quick-intro/ (wastl, 5)
  c. tkurz first checks if the current implementation still works and then looks into how to extend the webservice regarding time bundles and time maps (wastl, 5)

6. aob


--------
Actions:
--------
- check in final logo sources (bitmap and vector) to SVN and add comment to Jira about the donation (wastl, 09:24:01)
- tkurz first checks if the current implementation still works and then looks into how to extend the webservice regarding time bundles and time maps (wastl, 09:47:09)

IRC log follows:


# 1. Preface #
09:12:42 [wikier]: topics?
09:13:48 [wastl]: quick progress report on reasoning
09:13:56 [wastl]: quick progress report on logo
09:14:11 [wastl]: that's it from my side
09:14:33 [wikier]: ldp for me
09:14:43 [wikier]: tkurz?
09:14:48 [tkurz]: nothing from my side, just bugfixing ;)
09:15:10 [tkurz]: and: i will start to check the memento things today
09:15:47 [wastl]: so we have: reasoning, logo, ldp, memento


# 2. reasoning #
09:16:33 [wastl]: implementation of reasoning is in progress, I am currently working (since yesterday) on the persistence layer that directly opera#ates on the database
09:16:50 [wastl]: I expect to finish this part this morning and test it
09:17:03 [wastl]: and then in the afternoon and tomorrow the real reasoning logic
09:17:11 [wastl]: report end


# 3. logo #
09:17:20 [wikier]: cool
09:18:02 [wikier]: MARMOTTA-5
09:18:03 [wastl]: regarding the logo I discussed with Daniela, she will try for smaller sizes with different approaches (e.g. a bit lighter brown, less strokes)
09:18:25 [wastl]: especially 16x16 and 32x32 are challenging
09:18:33 [wastl]: and the Apache feather does not make it easier :)
09:18:33 [wikier]: yes
09:19:01 [wastl]: I hope we can finish this more or less today
09:19:01 [tkurz]: so I would say the feather is not important for small sizes
09:19:09 [wikier]: probably we can take it out
09:19:23 [wastl]: yes, at least it does not need to be the version with high details
09:19:31 [wastl]: I will send her a link to a simplified version of the feather
09:19:47 [wikier]: ok
09:20:01 [wikier]: home the website will come at the same time than the logo...
09:20:08 [wikier]: s/home/hope
09:20:09 [tkurz]: hopefully
09:20:24 [wastl]: yes, I also hope so
09:20:38 [wastl]: in any case we need a proper home for all the different logo versions
09:20:46 [wikier]: there are many project which don't use the feather in all versions of the logo
09:20:46 [wastl]: I suggest to put the logo in the same repository as the website
09:20:53 [wikier]: see OOo, for instance: https://cwiki.apache.org/OOOUSERS/aoo-3x-logo-explorations.html
09:21:01 [wikier]: wastl: +1
09:21:08 [tkurz]: I wouldn't focus on the feather
09:21:10 [wikier]: also attached to MARMOTTA-5
09:21:38 [wastl]: I am not sure this is possible
09:21:46 [wastl]: the zipped size is 20MB
09:21:46 [wikier]: too big?
09:21:46 [wikier]: ok
09:21:46 [wikier]: so svn
09:22:34 [westei]: maximum size is 10MByte AFAIK
09:22:47 [wikier]: https://wikier@svn.apache.org/repos/asf/incubator/marmotta/logo
09:23:02 [wastl]: +1
09:23:09 [wikier]: ok
09:23:39 [wastl]: ok, so I will check in the logo there then and make a comment to Jira to state that we officially contribute it
09:24:01 [wastl]: #action check in final logo sources (bitmap and vector) to SVN and add comment to Jira about the donation
09:24:07 [wikier]: both jira and svn are official contributions
09:24:14 [wikier]: coool
09:24:22 [wastl]: yes, just to be safe :)
09:24:22 [wikier]: :-)
09:24:37 [wastl]: hopefully closed today


# 4. ldp #
09:24:59 [wikier]: ok, ldp
09:25:02 [wikier]: I already have a core implementation
09:25:16 [wikier]: my task for this morning is to provide a test suite
09:25:38 [wikier]: although there are still many open issues
09:25:39 [wastl]: is this related to the TelCo yesterday?
09:26:21 [wastl]: but a test suite would be good
09:26:35 [wastl]: you can use the RestAssured library for this
09:26:50 [wastl]: and maybe this could be a worthwhile contribution to the WG
09:26:57 [wikier]: well, the main topics yesterday were "aggregation vs. composition", provide a kind of best practices to complement the spec, and etag discussion
09:27:05 [wastl]: if we have a test suite that is generic enough for others to use as well
09:27:12 [wastl]: and we can offer a validator :)
09:27:27 [wikier]: the idea is to use the same set of files
09:27:34 [wikier]: which uses earl for reporting
09:27:34 [wikier]: yes
09:27:49 [wikier]: that's the idea
09:27:58 [wikier]: but still in a very early stage of definition
09:28:20 [wikier]: so I'd like to have something for the next telco
09:28:20 [wastl]: etag is difficult, because it should indicate when a resource has last been modified
09:28:27 [wastl]: but how would you define it?
09:28:49 [wastl]: I was thinking very long about it in the context of the LMF implementation and finally decided it was not worth it
09:29:11 [wikier]: ldp plans to use weaks etags
09:29:41 [wikier]: which is easier to provide
09:29:55 [wikier]: a weakly validating etag match only indicates that the two resources are semantically equivalent
09:30:05 [wastl]: yes, but still you need to define when two representations are "semantically equivalent"
09:30:17 [wikier]: in the context of LDP, that two resources are the same with the same triples
09:30:19 [wastl]: ok
09:30:24 [wikier]: that's the current discussion
09:30:47 [westei]: that can be hard with BNodes
09:30:54 [wastl]: but then it's mostly useless for caching purposes, at least with normal HTTP clients
09:31:01 [wikier]: exactly
09:31:31 [wikier]: I'd try to provide some generic on top on sesame
09:31:34 [wastl]: ok, great
09:31:38 [wikier]: but I don't want to spend so much effort on it
09:32:07 [wastl]: btw, did they consider the etag problem with blank nodes?
09:32:28 [wikier]: briefly
09:32:36 [wikier]: the discussion continues at the mailing list
09:32:36 [wikier]: good point
09:32:51 [wikier]: I'll put it on the table 
09:32:51 [wastl]: ok, maybe this is an aspect to bring in
09:33:28 [wastl]: blank nodes are the empty sets of the semantic web, you can always bring them in to annoy people :)
09:33:52 [wastl]: ok, anyways
09:34:12 [wastl]: so you will develop a test suite in Perl or in Java?
09:34:19 [wikier]: java
09:34:19 [wikier]: of course
09:34:21 [wastl]: ok, great :)
09:34:34 [wastl]: much better, so it can be included in our testing
09:34:36 [wikier]: exactly
09:34:49 [wikier]: using the official files for the other test suites
09:35:11 [wastl]: ok, just the hint to look at RestAssured
09:35:33 [wastl]: #link http://code.google.com/p/rest-assured/
09:35:50 [wikier]: that could be my first option, yes
09:37:03 [wikier]: #link https://dvcs.w3.org/hg/ldpwg/file/39114b935c70/tests/basic
09:37:36 [wikier]: so my plan is our test suite will automatically run over that files
09:37:49 [wastl]: so the Manifest file defines how to run?
09:37:57 [wastl]: and what to expect?
09:37:57 [wikier]: exactly
09:38:12 [wikier]: still under development
09:38:26 [wikier]: but that's the approach they are using in og working groups, such as sparql 1.1
09:38:33 [wastl]: ok, great
09:39:03 [wikier]: let's see...
09:39:03 [wikier]: ;-)
09:39:10 [wikier]: ok, and that's it basically
09:39:33 [wikier]: next topic?


# 5. memento #
09:40:48 [wikier]: right
09:41:02 [wastl]: reference:
09:41:09 [wastl]: #link http://www.mementoweb.org/
09:41:26 [wastl]: Thomas? 
09:42:09 [wastl]: better reference:
09:42:12 [wastl]: #link http://www.mementoweb.org/guide/quick-intro/
09:42:31 [tkurz]: first I will check if the current implementations works after the whole restructuring
09:42:39 [wastl]: the idea is to provide an HTTP extension for representing time information
09:43:22 [tkurz]: afterwards we should provide a UI for browsing the 'old' resource
09:43:29 [wikier]: as soon as I find time to import the wiki, we should start to write some documentation there
09:44:06 [tkurz]: we should also have a look at the new sem web extensions of memento
09:44:06 [wastl]: there is much documentation on the above link already
09:44:21 [wastl]: apparently they extended it for semantic web / Linked Data recently
09:44:35 [wastl]: look at the intro, "Component 2"
09:44:44 [wastl]: "Time Bundles"
09:45:13 [wastl]: this is very interesting and we should probably try to implement it
09:46:10 [wastl]: and maybe this can also at a later point be a contribution to the LDP WG
09:46:17 [tkurz]: +1
09:46:25 [wikier]: +1
09:46:47 [wastl]: ok, so
09:47:09 [wastl]: #action tkurz first checks if the current implementation still works and then looks into how to extend the webservice regarding time bundles and time maps
09:47:32 [tkurz]: fine
09:47:37 [tkurz]: ;)


# 6. aob #
09:47:51 [wastl]: anything else?
09:48:07 [tkurz]: no
09:48:07 [wastl]: otherwise coffee and coding :)
09:48:36 [wikier]: xD
09:48:43 [wikier]: nothing from my side
09:48:43 [wikier]: thx!