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 properties for detailed real-estate description incl bathrooms #2373

Closed
danbri opened this issue Oct 22, 2019 · 7 comments
Closed

Add properties for detailed real-estate description incl bathrooms #2373

danbri opened this issue Oct 22, 2019 · 7 comments
Assignees

Comments

@danbri
Copy link
Contributor

@danbri danbri commented Oct 22, 2019

We are missing some properties for things such as number of bathrooms, although we do have https://schema.org/numberOfRooms as a start.

Bathrooms

https://schema.org/numberOfRooms is defined as

The number of rooms (excluding bathrooms and closets) of the accommodation or lodging business. Typical unit code(s): ROM for room or C62 for no unit. The type of room can be put in the unitText property of the QuantitativeValue.

It would be useful to have ability to be clearer about the number of bathrooms, including notions of "full" and "half" bathroom as used in real estate rental and sales industry.

other

  • We should be able to indicate when an image is a floor layout image e.g. by dedicated property like accomodationLayoutImage
  • Propose a subproperty of /category, /accomodationCategory to indicate kinds of accomodation, drawing on values from https://ddwiki.reso.org/display/DDW17/PropertySubType+Field
    and https://ddwiki.reso.org/display/DDW17/PropertyType+Field (a new subproperty lets us document this more clearly)
  • How do document the length of a lease? @mfhepp what modeling idiom would you suggest? e.g. where would a /leaseLength property best be attached? Offer has temporal properties like eligibleDuration but they naturally apply to the offer and not the thing offered. But we do not model leases as explicit things, just as a enumeration option in businessFunction. An OfferForLease property would be a possibility, but that weighs against treating OfferForLease purely as a shorthand for GR. Suggestions?
  • On /Apartment, a property for representing /floorLevel relative to local standards. Definition could point to Wikipedia's entry for explanation. https://en.wikipedia.org/wiki/Storey#Consecutive_number_floor_designations
  • We could make some amenities easier to describe with a dedicated property. See also https://schema.org/amenityFeature. e.g.
    • hardwood floors
    • Washer dryer options (hookups vs in-unit vs on-premises)
    • Dishwasher
    • AC\Cooling\Heating
    • Balcony
    • Furnished
    • End unit - is this unit an endcap or share both walls
    • Utilities included
  • Add to ApartmentComplex: Total number of units; Number of available units.
    • Maybe make some community level amenities easier to describe with a dedicated property:
      Pool
    • Potentially a new type for FloorPlan/Model, including total number of units, number of available units.
  • Clarify how RealEstateListing relates to these and existing GoodRelations fundamental patterns (e.g. via mainEntity), including how to indicate when a listing was posted.
@danbri
Copy link
Contributor Author

@danbri danbri commented Oct 29, 2019

see also eg. https://webschemas.org/floorLevel (currently under review for november release), alongside accommodationCategory, floorLevel, leaseLength, numberOfBathroomsTotal, numberOfFullBathrooms. A "floor plan" property for floor plan images likely to be proposed here too.

@marcelolara10
Copy link

@marcelolara10 marcelolara10 commented Dec 22, 2019

see also eg. https://webschemas.org/floorLevel (currently under review for november release), alongside accommodationCategory, floorLevel, leaseLength, numberOfBathroomsTotal, numberOfFullBathrooms. A "floor plan" property for floor plan images likely to be proposed here too.

Hello @danbri they were released or still pending? I want to know if i can use them

thanks

@danbri
Copy link
Contributor Author

@danbri danbri commented Jan 2, 2020

also e7a09e6

@danbri
Copy link
Contributor Author

@danbri danbri commented Jan 2, 2020

@marcelolara10 these are being queued for review/release as schema.org version 6.0. Currently they are only on the pre-review staging site, webschemas.org. Nothing stops you using them but be aware change is possible, and as these are early days, they might not be widely understood yet.

@danbri
Copy link
Contributor Author

@danbri danbri commented Feb 25, 2020

Some additional improvements:

  • Add petsAllowed to ApartmentComplex
  • Add petsAllowed, amenityFeature and floorSize to FloorPlan
  • Create an explicit numberOfBedRooms and allow it in Accommodation, ApartmentComplex and FloorPlan.
  • In ApartmentComplex and FloorPlan the value might be a range to allow describing all apartments under that entity, so the value should allow both Number and QuantitativeValue
  • Add a "book a tour" (/tourBookingPage) property - url value allowed on Accommodation and ApartmentComplex

(todo)

  • CONSIDER allowing numberOfBathroomsTotal, numberOfFullBathrooms, numberOfPartialBathrooms and floorSize on ApartmentComplex
    so long as semantics were clear.

@nicolastorzec
Copy link
Contributor

@nicolastorzec nicolastorzec commented Feb 26, 2020

We may want to clarify the definition for bathroom?

  • Wikipedia: "In some countries, the toilet is usually included in the bathroom, whereas other cultures consider this insanitary or impractical, and give that fixture a room of its own."
  • For example in France you would typically get two different numbers: one for the number of rooms with a sink/bathtub/shower, and another one for the number of rooms with a toilet.

Regarding the todo item:

  • I understand why numberOfBathroomsTotal, numberOfFullBathrooms, numberOfPartialBathrooms and floorSize can be useful for an hostel or B&B, but what's the use case for ApartmentComplex?

danbri added a commit that referenced this issue Mar 16, 2020
danbri added a commit that referenced this issue Mar 16, 2020
@RichardWallis
Copy link
Contributor

@RichardWallis RichardWallis commented Jul 1, 2020

Implemented in several commits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants