STR vs. CA areas ?

[markams]

Discuss:

Is needed?

• What is the functional difference
• What is the legislation (where is the specification documented

If needed:

• How to implement it, e.g.
• Duplicate entity (not preferred, as it adds complexity and leads to duplicate code); or
• Add a flag (e.g. areaType); or
• Keep the responsibility outside SDEP and let CA filter this by herself);
• Or ...

[markams]

FR
We understand that there is a mutualization between the localization of areas that implement the STR regulation and the areas that ask for activity data (also because the PwC endpoint GET /str/str-area has no equivalent). But we do not see how the distinction and information taken in the API related to the sending of activity data. Can you explain the overall logic between the need to understand the areas where the STR regulation, applies, the areas that ask for activity data (and are authorized to do it) and the actual sending of activity data to the right areas ?

[DionTheo]

Proposal: add indicator requiresActivityData; default True, unless overwritten by CA-client.

Implication 1: When STR invokes GET /str/areas, they observe requiresActivityData and if requiresActivityData == True then activity data has to be submitted by the platforms.

Implication 2: When CA invokes GET /ca/activities, they will only get activities for which requiresActivityData == True

Implication 3: When requiresActivityData == False, regulation still applies (hosts have to enter a registration number on the platforms). Only this is applicable for the platforms in this case.

[christopherbheDV]

This is needed as stipulated by the Regulation, Article 13

• The first type of area, "where the registration procedure applies", defines for the platforms the areas for which they need to perform random checks and enforce registration numbers to be when hosts create listings.
• The second type of area, "for which competent authorities have requested data ...", defines for the platforms the areas for which they need to forward activity data to the SDEP. Logically, this is a subset of the first type of area.

Depending on Member State context, it is possible that not only the areas are not equal, but also that the authority for defining these areas do not lie with the same entity. (for example, it could be that the tourism agency or other central entity defines the registration procedure and it's area, but that local municipalities define whether or not they wish to receive activity data for their local area).

Therefore, it is not sufficient to only flag "requiresActivityData" at the level of the first type of area. It must be possible to provide area files for each type of area (however, the area type can be defined through flags so that a single endpoint can be used without code duplication)

[fernandrouwendaal]

OK, thus the same area can be supplied by two mutually exclusive CAs, for a different purpose.

Propose in that case to add the field Area.regulation { listing, activity }

As mandatory field, where one or both values apply.