Log of the #fcrepo channel on chat.freenode.net

Using timezone: Eastern Standard Time
* madgoat joins00:31
* madgoat leaves
* dwilcox joins04:41
* jonathangee leaves05:40
* jonathangee joins05:51
* dwilcox_ joins
* dwilcox leaves05:52
* dwilcox_ leaves06:19
* peichman joins07:06
* peichman leaves07:08
* jjtuttle_ leaves07:12
* jjtuttle joins07:14
* peichman joins07:28
* peichman leaves07:29
* coblej joins08:24
* grosscol joins09:15
* peichman joins
* apb18 joins09:19
* peichman leaves09:51
* bseeger joins09:54
* peichman joins09:58
* coblej leaves10:28
* coblej joins10:29
* dwilcox joins10:32
* coblej leaves
* coblej joins
* dwilcox leaves10:36
* peichman leaves10:38
* peichman joins10:40
* bseeger leaves11:00
* tpendragon joins11:02
* yinlin joins
<grosscol>https://github.com/fcrepo4-labs/fcrepo_perf_analysis/blob/feature/dist-upload/dist/test2.pu.postgres/test2.pu.postgres.md11:05
https://github.com/fcrepo4-labs/fcrepo_perf_analysis/blob/feature/dist-upload/sequential.sh11:09
https://github.com/fcrepo4-labs/fcrepo_perf_analysis/blob/feature/dist-upload/dist/test4.pu.postgres-mode51/test4.pu.postgres-mode51.md11:11
Shows positive correlation
<awoods>https://wiki.duraspace.org/display/FF/Performance+and+Scalability+Test+Plans
* apb18_ joins11:17
* apb18 leaves11:19
<awoods>https://wiki.duraspace.org/display/FF/Performance+and+Scalability+Test+Plans#PerformanceandScalabilityTestPlans-TestCompletion11:20
* coblej leaves11:21
* coblej joins11:23
* bseeger joins
* dwilcox joins11:24
* coblej leaves11:27
* coblej joins
* manez leaves
* dwilcox leaves11:30
* f4jenkins leaves11:31
* manez joins11:32
* f4jenkins joins11:35
<yinlin>https://github.com/VTUL/fcrepo4-ansible11:41
public now11:42
awoods ++11:43
Danny ++ Longshou ++11:52
* apb18 joins11:54
* bseeger leaves
* apb18_ leaves11:56
* dwilcox joins11:58
<tpendragon>https://gist.github.com/escowles/43e434979c9fd3762cb1ad1225655abf11:59
* bseeger joins12:00
* jjtuttle leaves12:09
* jackhill leaves
* jjtuttle joins12:10
* dwilcox leaves12:12
* jackhill joins12:14
* bseeger leaves12:27
* bseeger joins12:44
* mohamedar joins12:50
* dwilcox joins12:57
* dwilcox leaves13:07
<grosscol>yinlin, awoods, I think I figured out what I'm going to do about the space requirements for the fcrepo perf tests. I found a decent starting point, but basically, write a custom FUSE filesystem to mount at fcrepo_home/data.13:17
<awoods>grosscol++ let us know if we can test it out13:18
<grosscol>To get the same bytes going in as out, you'd also have to read from that.
Yeah. I'll put together an example for next time.
<yinlin>grosscol++ thx!13:28
* yinlin leaves14:06
* bseeger leaves14:40
* ajs6f joins14:41
barmintor: ping14:45
* acoburn joins14:49
<ajs6f>acoburn: ping14:53
<acoburn>ajs6f: pong
<ajs6f>acoburn: If I send an LDP server a POST with Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel="type" and some RDF (say, some Turtle), should I not create an LDP-NR?14:54
<acoburn>ajs6f: yes, unless there is a constraint preventing such a thing
<ajs6f>acoburn: Sure, but let's say there isn't.14:55
<acoburn>ajs6f: you _definitely_ shouldn't create an LDP-RS
* peichman leaves
<ajs6f>acoburn: Right, right. Anyway, after creation, it behaves like any other LDP-NR, right?
<acoburn>ajs6f: yes
<ajs6f>acoburn: apb18: Doesn't this support apb18's OWL use case?14:56
<acoburn>ajs6f: yes, and that was the road I was going down last week with him
<ajs6f>acoburn: Okay, good. That removes that objection to description-as-representation, I think.14:57
acoburn: And it's also what I would say to people who want to relax the SSR on contents.
acoburn: Go nuts, just use LDP-NRs.
<barmintor>err, what
<acoburn>ajs6f: would there be a description for that LDP-NR?14:58
<barmintor>no
<ajs6f>barmintor: Why not?
acoburn: just as much as for any other LDP-NR.
<barmintor>because a LDP-NR is not a description, and can't be managed.
not as description.
<ajs6f>barmintor: We're conflating use cases here. I'm talking about the desire to stick a piece of RDF in a repository "from the wild" (e.g. like Tom Johnson at DPLA).14:59
barmintor: More importantly, why can't it be managed.
barmintor: LDP is silent on that, to my eye.
<barmintor>oh, that is why Derby, and Cavendish, and my fork of Lyo all let you specify that Link@rel=type, yeah
<ajs6f>barmintor: It talks about things that MUST be managed, but it doesn't say you CAN'T manage other stuff.15:00
barmintor: I don't know if you are being sarcastic, or what.
<barmintor>eek
<ajs6f>barmintor: What is the onbjection?
<barmintor>ajs6f: if you are storing something that happens to be RDF serialization as a LDP-NR, then you need to be able to do that. I think we agree about that.15:01
<ajs6f>barmintor: Sure. I just want to figure out which use cases that actually supports.
<barmintor>it's also why I was pushing bcak to apb18 last week about conneg for getting at the description of a LDP-NR15:02
<ajs6f>barmintor: I thought _he_ was pushing back at acoburn. Oh well. Maybe it was all just a dream.
<barmintor>ajs6f: the readiest one is the one you were just talking about, archives of digital material
<ajs6f>barmintor: Right. So let's talk about theothers. Like what are you thinking of/
?
<barmintor>I don't follow you. It's a binary. You need it to be a binary.15:03
that's orthogonal to the SSR concerns
* peichman joins15:04
<ajs6f>barmintor: I'm trying to understand the use cases for breaking the SSR, and you are someone who has repreatedly expressed didssatisfaction with it.
<barmintor>s/SSR/LDP-RS describing LDP-NR/
<ajs6f>barmintor: Yeah, this is not about that. This is a totally diff thread.
<barmintor>well, it's *sort* of different15:05
<ajs6f>barmintor: This is not about description, per se, unless you tell me that that is part of the use case that interests you and makes you want to break the SSR
barmintor: Well, it's all Fedora, and it's all turtles all the way down.
<barmintor>anyway, the first 2 breaks with SSR are description of LDP-NR and hash URI subjects15:06
<ajs6f>barmintor: Yes. The second dosn' bother me because #-uris have no independent exitsence as retrieavable things.15:07
barmintor: Description bothers me, but I don't think there is a simple answer.
barmintor: See my recent emails re: Web Annotations
<barmintor>the subsequent ones are descriptions of things, too
<ajs6f>barmintor: e.g.? Like descriptions of LDP-RSes?15:08
* apb18 leaves
<barmintor>ajs6f: I saw that email, I think it might make sense as a way to do descriptions, but I don't feel like I can respond w/o digesting that spec
ajs6f: I meant to write you an email saying that, but then it was 3pm
crap, it's 3pm
<ajs6f>barmintor: Totally. That was just me thinking out loud anyway.,
barmintor: Yeah< I need to break and do some yoga.15:09
<barmintor>everyday, neglibile progress on a million little things. sigh.
<ajs6f>barmintor: Anyway, if you have to think about I would appreciate knowing waht you think of as some good examples15:10
have time to think about it
barmintor: Every day, https://i.chzbgr.com/full/8370586368/hD283483A/
* mohamedar leaves15:18
* acoburn leaves16:20
* bseeger joins16:24
* peichman leaves16:26
* ajs6f leaves16:27
* grosscol leaves16:29
* bseeger leaves16:31
* peichman joins16:33
* coblej leaves17:16
* peichman leaves17:35
* dwilcox joins18:00
* dwilcox leaves18:34
* awoods leaves23:55

Generated by Sualtam