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

Using timezone: Eastern Standard Time
* ksclarke leaves00:07
* dwilcox joins08:34
* dwilcox leaves08:49
* dwilcox_ joins
* acoburn joins08:56
* pmurray leaves
* pmurray joins
* ksclarke joins09:25
* ajs6f joins10:10
* peichman joins10:17
<f4jenkins>Project fcrepo4-T2 build #423: UNSTABLE in 5 min 18 sec: http://jenkins.fcrepo.org/job/fcrepo4-T2/423/10:54
* jrgriffiniii joins11:01
* Guest47065 leaves11:04
* ajwagner joins
* bseeger joins11:26
* bseeger leaves11:39
* whikloj joins12:15
* lsitu joins13:00
* ajs6f leaves13:30
<lsitu>Hello everyone!13:42
When adding non-RDF contents with mix prefix properties like <mix:imageProducer>Mandeville Special Collections Library</mix:imageProducer> to binary files, I got a 400 bad request error with message “Unable to register the namespace "http://www.loc.gov/mix/v20#" with prefix "mix" because this prefix is reserved”. However, it works when changing the mix prefix to something like mix1. Does anyone know about the error and what’s the right way to deal with
Thanks.
<whikloj>lsitu: Is that because the namespace is already defined inside F4?13:45
* peichman leaves13:46
* peichman1 joins13:47
* peichman1 leaves
* peichman joins13:48
<lsitu>@whikloj: Yes, I think so. I just use fcrepo-webapp-4.4.1-SNAPSHOT-jetty-console.jar and I see a namespace “<mix = 'http://www.jcp.org/jcr/mix/1.0'>” defined in fedora-node-types.cnd. I think we would like to know whether using other namespace prefix like mix1 is the right way for it.14:09
<whikloj>lsitu: I would say so. Much like a completely separate new namespace you'll want to register a new prefix. Perhaps mix20?14:20
<lsitu>whikloj: Thanks.14:22
* dhlamb joins14:29
* ajs6f joins14:38
acoburn: http://helix.apache.org/ Better than relying on our persistence engine for cmanagement?14:39
<acoburn>ajs6f: seems a bit similar to zookeeper, no?14:40
* bseeger joins14:41
<ajs6f>acoburn: Yeah, lil' bit. Seems more high level and less concerned with genericity.
<acoburn>ajs6f: this certainly looks interesting, maybe something to discuss at the next tech call?14:44
ajs6f: ahh, it's built on top of zookeeper14:45
<ajs6f>acoburn: Ah, that makes sense.
<acoburn>ajs6f: interesting that it's basically a supervised, distributed state machine14:46
<ajs6f>acoburn: The state machine model could support the predictatability and repeatablility needed preservation workflows.
<acoburn>ajs6f: I agree. it's also really nice to work with a simple fsm14:48
<ajs6f>acoburn: It's nice to work with simple everythings. That's why I try to avoid Fedora.14:49
* peichman leaves14:59
* peichman joins15:00
<ajs6f>acoburn: Are we even doing a call Thurs (Día de Acción de Gracias de Estados Unidos)?15:16
<acoburn>ajs6f: not that I know of. I certainly won't be on the call
<ajs6f>acoburn: Oh, you meant a future call ^^^?15:17
<acoburn>ajs6f: yes, whenever the next one takes place. Dec 3?
<ajs6f>acoburn: Oh, cool.
acoburn: Dec 3 will be the 10th anniversary of the https://en.wikipedia.org/wiki/Rocket_mail#Reusable_launch_vehicles.15:18
first manned rocket aircraft delivery of U.S. Mail
* dwilcox_ leaves15:26
* bseeger leaves15:44
* bseeger joins15:45
* ajs6f leaves15:53
* dhlamb leaves15:56
* whikloj leaves15:58
* peichman leaves16:12
* peichman joins16:22
* jrgriffiniii leaves17:04
* bseeger leaves17:14
* acoburn leaves17:36
* peichman leaves17:42
* lsitu leaves18:29
* ksclarke leaves20:05
* ksclarke joins20:20
* osmandin leaves22:40
* awead leaves23:09
* ksclarke leaves00:06
* osmandin joins00:37