You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds an accommodation marketplace profile for NIP-99 marketplace listings. The proposal keeps accommodation listings on the existing NIP-99 listing event kinds and defines the profile-specific fields clients need for lodging search, rendering, and filtering.
What this defines
The accommodation marketplace profile tag.
Accommodation-specific listing tags such as check-in/check-out times and spec details.
H3-based g location indexing for area search without requiring exact property disclosure.
Promoted compact tags for efficient relay/client filtering.
Listing anchor and client behavior guidance for accommodation listings.
Scope
This does not define a new listing event kind. Generic marketplace behavior such as auto-acceptance, negotiability, deposits, dispute periods, and cancellation policy lives in the marketplace listing extension.
The accommodation-specific profile split makes sense. One interoperability boundary still looks underspecified: availability.
This draft defines checkIn, checkOut, and uses minDuration, but it does not say how clients discover host-blocked dates, existing bookings, or otherwise unavailable stay ranges. Could the Scope or Related NIPs section explicitly state whether accommodation availability is expected to use NIP-52 or a companion availability proposal?
NIP-52 kind 31922 already models date-based intervals with inclusive start and exclusive end, and kind 31924 can group calendar events. Reusing those primitives could avoid a second incompatible calendar model, but an accommodation profile would still need to define the listing reference, authoritative publisher, privacy expectations, and how blocked periods relate to committed orders. NIP-52 RSVP events should not by themselves imply booking acceptance.
Even if availability remains out of scope here, an explicit non-goal and pointer would help prevent accommodation clients from inventing incompatible blocked-date tags.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an accommodation marketplace profile for NIP-99 marketplace listings. The proposal keeps accommodation listings on the existing NIP-99 listing event kinds and defines the profile-specific fields clients need for lodging search, rendering, and filtering.
What this defines
accommodationmarketplace profile tag.specdetails.glocation indexing for area search without requiring exact property disclosure.Scope
This does not define a new listing event kind. Generic marketplace behavior such as auto-acceptance, negotiability, deposits, dispute periods, and cancellation policy lives in the marketplace listing extension.