valueflows merge requestshttps://lab.allmende.io/valueflows/valueflows/-/merge_requests2019-10-06T20:36:25Zhttps://lab.allmende.io/valueflows/valueflows/-/merge_requests/383example: bungalow rental and usage2019-10-06T20:36:25Zelf Pavlikexample: bungalow rental and usage### example good practices
* it includes full JSON-LD `@context` and doesn't rely on any external context
* it includes all the data under `@graph` and doesn't try to frame it as a tree with a single root #123
### VF impact
* ex...### example good practices
* it includes full JSON-LD `@context` and doesn't rely on any external context
* it includes all the data under `@graph` and doesn't try to frame it as a tree with a single root #123
### VF impact
* example proposes new action `vf:lend` to represent lend/borrow flows (instead of discussed on chat *possess*)
* for time based flows, it uses quantity to represent quantity of the involved/affected resource and uses Time to represent duration
* it uses proposed in #293 `vf:includedIn` to relate short usage during working session with longer usage between checking-in and checking-out of rented bungalow
### open issues
* we can observe start of 1 year lend event when it starts but we can't observe the whole event yet, related to #336
* we can record fulfilled quantity of a resource for 'ongoing event' but can record the fulfilled time yetscheduleshttps://lab.allmende.io/valueflows/valueflows/-/merge_requests/387initial examples for shared use of independently controlled studios2019-10-06T20:35:58Zelf Pavlikinitial examples for shared use of independently controlled studiosBased on https://github.com/valueflows/valueflows/wiki/Use-Cases-and-Requirements#independent-shared-therapy-studios
Making commitment to oneself serves purpose of reserving the time and not making conflicting commitment to someone el...Based on https://github.com/valueflows/valueflows/wiki/Use-Cases-and-Requirements#independent-shared-therapy-studios
Making commitment to oneself serves purpose of reserving the time and not making conflicting commitment to someone else.
I plan to add another variants where agents can exchange commitments. So when Alice makes commitment to Daniel for use of Alice's studio and then she gets commitment from Bob for use of his studio. Possibly she could exchange those commitments with Daniel and use the studio she controls while Daniel gets to use studio that Bob controls. scheduleshttps://lab.allmende.io/valueflows/valueflows/-/merge_requests/446Example time-based quantities and times2019-09-29T21:36:36ZLynn FosterExample time-based quantities and timesThis is just the beginning of this PR, exploring examples for the scheduling milestone. Focusing on getting the quantity and time properties defined for different use cases, irrespective of transfers or composition.
Started with work...This is just the beginning of this PR, exploring examples for the scheduling milestone. Focusing on getting the quantity and time properties defined for different use cases, irrespective of transfers or composition.
Started with work, as possibly the simplest, want to make usage be as similar as possible.
Things to note:
* calendar property
* observedQuantity name change
* all the time properties can be = or > than the quantity properties (the quantity properties are what is counted, the time properties are what relates to scheduling)scheduleshttps://lab.allmende.io/valueflows/valueflows/-/merge_requests/458first draft ouikits2019-09-29T21:34:30ZLynn Fosterfirst draft ouikitsRough draft, thinking while doing.
Some experiments:
* checkin and checkout actions (kinds of transfers imo)
* put the (give) and the (receive) into one flow (eg. checkin), added resource for the receiver
* the availability of kits...Rough draft, thinking while doing.
Some experiments:
* checkin and checkout actions (kinds of transfers imo)
* put the (give) and the (receive) into one flow (eg. checkin), added resource for the receiver
* the availability of kits requires the checkout and checkin commitments to calculate, didn't see where a duration would fit in (this happens in manufacturing too, NRP calculates availability based on current quantity and commitments that will either decrement or increment, when creating a plan from recipe)
* same name for quantity and time for all flows
* in this use case, I didn't have a need for more than one quantity, since the unit of use I think is still Number. - time based units didn't seem useful for this kind of resource as quantities - seemed like the time durations could take care of any availability issues within the org's event, say if they used some of the kits in one process and some in another process that overlapped times
scheduleshttps://lab.allmende.io/valueflows/valueflows/-/merge_requests/462Core attributes (was: affects > involves, affectedQuantity > observedQuantity)2019-09-29T21:32:47ZLynn FosterCore attributes (was: affects > involves, affectedQuantity > observedQuantity)working with core attributes for a minimal PR, started with 'affects' and 'affectedQuantity'
question: On the time properties, if we think they will be either an Instant or a TemporalEntity (Instant being a subclass of TemporalEntity)...working with core attributes for a minimal PR, started with 'affects' and 'affectedQuantity'
question: On the time properties, if we think they will be either an Instant or a TemporalEntity (Instant being a subclass of TemporalEntity), should we explicitly define the rdfs:range to be both of those, or leave it at TemporalEntity and let the examples speak?schedules