Make location optional (Discussion: Extend SpaceAPI to associations without physical meeting locations) #106
Conversation
This file contains 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
dbrgn
reviewed
Sep 24, 2023
dbrgn
changed the title
|
As discussed in today's SpaceAPI core team meeting:
This enables groups without a physical location to be added to the SpaceAPI by simply omitting the location. |
dbrgn
previously approved these changes
Apr 11, 2024
|
Should we amend the description of the location key with an explicit hint that it can be omitted if the entity does not have a physical location? |
Good idea! |
|
I'll rebase and squash the commits in this PR. In case someone wants to take a look at the original proposal, it can still be accessed here: 142c3c7 |
rnestler
approved these changes
Apr 12, 2024
dbrgn
approved these changes
Apr 12, 2024
…ical location Examples include: - Groups meeting regularly without a fixed location (e.g. LUGs) - Umbrella organizations
|
Two approvals, and we discussed this at the core meeting. Merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@SpaceApi/core The idea for this PR comes from a discussion at the CCC Regiowochenende 2023, and is supposed to serve as a starting point for further discussion.
Apart from hacker- and makerspaces, which have a (more or less) permanent, fixed location in the physical world, there are also other types of groups which cannot be properly represented by the current SpaceAPI schema. Concrete examples of such groups are:
One such regional umbrella association has recently created a dedicated SpaceAPI endpoint where they publish news and calendar feeds for events organized by the umbrella organization. Their endpoint currently contains a
locationto be schema compliant, but it doesn't point to a meaningful location. In addition, the endpoints of the individual spaces (which are part of the umbrella organization) have started adding theext_habitatfield to their API endpoints to signal that they are part of a larger association (which is something I'd rather see as an entry inlinked_spacesinstead).Members of another supra-regional association have expressed that they would like to offer a SpaceAPI endpoint, so that their news and calendar feeds could be ingested by SpaceAPI aggregators such as spaceapi.ccc.de.
I'm not yet entirely happy with this PR (I don't think
hubis the best term to use, and I'm not sure how many types of organizations we would want to distinguish), but I'd like to get the discussion started about whether we want to extend SpaceAPI to include associations without physical meeting locations.CC @cyroxx