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

Add information about property transaction procedure #134

Open
ghost opened this issue Jul 6, 2020 · 4 comments · May be fixed by #151
Open

Add information about property transaction procedure #134

ghost opened this issue Jul 6, 2020 · 4 comments · May be fixed by #151
Assignees
Labels
Business need unclear Business cases are being discussed but not decided yet. Feature Request Missing functionality and changes

Comments

@ghost
Copy link

ghost commented Jul 6, 2020

Problem description
Some key indicators for the transaction of investment properties are missing in SwissRETS.
Information about the transaction type, the timeline and some general conditions for the offers are important.

Desired Solution
Add information about the property transaction procedure and timeline, minimal prices for the offers and steps to increase an offer:

Process types:
Real estate transactions can be distinguished into:

  • fixed price transaction
  • auction
  • bidding procedure

Timeline

  • Startdate (for fixed price & auction)
  • Enddate (for fixed price & auction)
  • Startdate NBO (only for bidding procedure): Startdate for non-binding offer phase. Ends with Startdate of binding offer phase.
  • Startdate BO (only for bidding procedure)
  • Enddate BO (only for bidding procedure)

Minimum price
Starting price for a transaction.
The seller only accepts offers that equal or higher than the minimum.

Offer increase
Amount by which a prospective buyer needs to increase his offer. (CHF 10'000 / CHF 20'000 / CHF 50'000 / CHF 100'000)
This is only relevant for auction based transactions

@jensstalder
Copy link
Collaborator

jensstalder commented Oct 30, 2020

##Currently already implemented version

<auction
  expiration = xs:dateTime
  start = xs:dateTime>
positiveInteger
</auction>

Timeline

  • * Startdate (for fixed price & auction) = **<action start="">**
  • * Enddate (for fixed price & auction) = **<action expiration="">**
  • * Startdate NBO (only for bidding procedure) = proposal: **<action nboStart="">**
  • * Startdate BO (only for bidding procedure) = Q: does that differ from a normal action aka **<action start="">**?
  • * Enddate BO (only for bidding procedure) = Q: does that differ from a normal action aka **<action expiration="">**?

Process types:

Q: Can the type be infered by the ginven data. F.e. defining a start end and starting bid will imply a normal auction. Defining nboStart nboEnd will define a bidding system? Or should we define this explicitly separately (see type="" in example).

Offer increase

Q: Does the offer increase require all increments to be as such (rastered), or does it mean its the minimal increase but auctioneers can increase by a arbitrary amount when minimum increase is reached?

Minimum price

Already implemented since the base integer value represents the staring price.

Full possible result example

<auction nboStart="" start="" expiration="" type="fixed|normal|bidding" minIncrement="10000">1234567</auction>

@jensstalder jensstalder self-assigned this Nov 2, 2020
@ghost
Copy link
Author

ghost commented Nov 3, 2020

What im wondering here is everything should go in an element, when only 1 of the 3 procedures is an auction?

Timeline:
I would be potentially enough to add only nboStart="" but this needs to be well documented in that case so everyone knows how where to add the values

Process types:
I would go for an explicit definition here ( type="")

Offer increase:
Should be minimal increase but auctioneers can increase by a arbitrary amount when minimum increase is reached

@jensstalder
Copy link
Collaborator

@rgutzwiller

So this then

<auction start="" bindingStart="" expiration="" type="fixed|normal|bidding" minIncrease="10000">1234567</auction>

start: Defines when the action starts
bindingStart: Defines when the bidding becomes binding. Must be after start date.
type: TODO: We need to define the types. normal is probably not a good option. Will fixed and bidding be enough?
value: Defines the starting price
minIncrease: Defines the minimum amount of increase for a bid.

Once I know the types and if this looks ok to you I can create a PR. As far as I can tell these are all required values right?

@jensstalder
Copy link
Collaborator

jensstalder commented Nov 11, 2020

Ok I think we got a solution now:

<property>
    <availability start="2018-12-13T12:12:12" expiration="2019-12-13T12:12:12">active</availability>
        <prices currency="CHF">
            <buy referring="all">
                  <price>850000</price>
                  <extra>25000</extra>
                   <wirPercentage>5</wirPercentage>
                   <yearlyOperationAndMaitenanceCosts>50123</yearlyOperationAndMaitenanceCosts>
            </buy>
            <auction start="2012-12-13T12:12:12" expiration="2012-12-13T12:12:13" minimalIncrease>745</auction>
            <bidding start="2012-12-13T12:12:12" bindingStart="2012-12-14T12:12:12" expiration="2012-12-15T12:12:13">745</auction>
            <deposit type="bank-guarantee">60000</deposit>
            <additionalOffers>
                  <offer type="parking-garage" interval="onetime">25000</offer>
            </additionalOffers>
    </prices>
</property>

What I am unsure about. Can <availability start="2018-12-13T12:12:12" expiration="2019-12-13T12:12:12" represent/replace the start and expiration dates from <action> and <bidding> or is that a seperate inromation?

@jensstalder jensstalder linked a pull request Nov 13, 2020 that will close this issue
@jensstalder jensstalder linked a pull request Nov 13, 2020 that will close this issue
@jensstalder jensstalder modified the milestones: 2.1.0, Meet-up 2020 Q4 Nov 30, 2020
@jensstalder jensstalder added the Feature Request Missing functionality and changes label Dec 7, 2020
@jensstalder jensstalder modified the milestones: 2.1.0, future Dec 7, 2020
@jensstalder jensstalder added the Business need unclear Business cases are being discussed but not decided yet. label Dec 7, 2020
@jensstalder jensstalder modified the milestones: future, Meet-up 2021 Q1 Dec 7, 2020
@ghost ghost modified the milestones: Meet-up 2021 Q1, Meet-up 2021 Q2 Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Business need unclear Business cases are being discussed but not decided yet. Feature Request Missing functionality and changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant