FYI: An improved version of the text above has been merged to the original text (see here).

BEP-0004 is available here for input and discussion: https://github.com/BONSAMURAIS/enhancements/blob/bep4-communications/beps/0004-bonsai-communication-strategy.md Feel free to reply here. Kind

Thanks Tom, this is really exciting! I would like to remind people of the process around BEPs. The BEP is a draft, meaning that it is still under development. It doesn't need an editor yet. The

Thanks Tom. Just a few update that should be in the text of the BEP: the google drive has been removed and the file added to an Archive section of bonsai.uno as agreed. That bullet point could be

Not trying to start a flame war or anything, but "flow object" is just... not great. It is inconsistent with all our other core terms, it rolls off the tongue like a porcupine, and I guarantee you

So the issue is back! Well I did raise the point about terms like flow and 'flow object' being confusing and likely that someone new to the ontology might have some difficulty in understanding the

Hi group, Exchange is actually what’s being used in the ecospold2 and ILCD data formats as well. They have flows as well, though they include compartment too. In theSimaPro platform, we don’t

Hi all, the BEP seems fine to me. I have only 2 comments: - I would have preferred it to be called "BEP000" for vanity reasons :) - I think each future BEP should include a link to the rules in

Hi all, like John Snow, I know nothing. From an outsider perspective the current definition is extremely clear, as it related the Flow and the Object of the Flow (aka Flow Object). While all other

The important issue is to distinguish between the observation of a specific flow (e.g. 22 kg input of steel) and the abstract flow-object ("steel"). This distinction was not made clear in

Thank you Chris; I agree and would add that ‘Flow-object’ is also not too perfect. No other element is called “object”. And exchange just says: see flow. Proposal from my side: Flow object

>>> The important issue is to distinguish between the observation of a specific flow (e.g. 22 kg input of steel) and the abstract flow-object ("steel"). >>> I do not think it makes much difference if

Hi group, Bo is right, I looked at the ecospold2 source files to refresh my memory and they indeed call their master data elementary exchanges and intermediate exchanges. So it is actually only in

Item is fine... /Søren

My suggestions are similar to what is given in the ILCD Just to reiterate I suggest to change: Flow object (abstract ) to Flow (a thing that exists) Flow (specific) to Exchange (a relationship

To re-iterate: Flow is a verb, and should remain as the central term for our observations. There seems to be a tendency towards preferring flow-item (instead of flow-object). If we

Dear all- As many of you have already realized, we need to organize and document our infrastructure a bit better. Specifically, I see a need for: Standard practice guidelines on maintaining the RDF

Yes, I'll coordinate this.

Hi Chris, I can imagine that some of my tests may have deleted some data from the database. Sorry for that. To be honest, I was under the impression that the data in jken I would expect the database