Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Branch: Acquisition #30

Open
6 tasks
annabelleee opened this issue Jun 6, 2018 · 3 comments
Open
6 tasks

Branch: Acquisition #30

annabelleee opened this issue Jun 6, 2018 · 3 comments
Assignees
Labels
model Modeling discussion

Comments

@annabelleee
Copy link
Collaborator

annabelleee commented Jun 6, 2018

Steps to completion (updated):

  • Metadata
  • Diagram (using ARM WG notation)
  • Sample Data
  • Sample Concepts
  • JSON of Arches branch based on diagram in ARM WG github repo
  • Vote in comments to officially approve branch
@azaroth42
Copy link
Collaborator

Proposed acquisition model:

acquistion_model

It's an Activity base (label, type, reference/description, partitioning, location, time, actor) that also:

  • Can have a Payment activity as a part.
  • Transfers title from the seller
  • Transfers title to the buyer
  • Transfers title of an object.

@Habennin
Copy link
Collaborator

I made a version of this in the google spreadsheet as well.

https://docs.google.com/spreadsheets/d/1EYk1yhhBNWrKbVB0jV_1j8NJ-Egi5zWha7QrVvYvw3s/edit?usp=sharing

I wonder if we should make payment itself a branch, a simple one but still a branch. What do you think?

@Habennin
Copy link
Collaborator

Does this model use the E96 class of CRM or is the payment a new class? I don't find properties for paid from or paid to. They could be represented by a role but also by new sub properties. I just don't find them on E96.

@azaroth42 azaroth42 added the model Modeling discussion label Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model Modeling discussion
Projects
None yet
Development

No branches or pull requests

3 participants