search

SpaceApi / schema

SpaceAPI JSON schema files.
24 stars 14 forks source link

Make location optional (Discussion: Extend SpaceAPI to associations without physical meeting locations) #106

Closed s3lph closed 2 months ago

s3lph commented 9 months ago

@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 location to 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 the ext_habitat field to their API endpoints to signal that they are part of a larger association (which is something I'd rather see as an entry in linked_spaces instead).

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 hub is 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

dbrgn commented 2 months ago

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.

s3lph commented 2 months ago

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?

dbrgn commented 2 months ago

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!

dbrgn commented 2 months ago

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: https://github.com/SpaceApi/schema/pull/106/commits/142c3c75f6c45e26a31a3802845bcb6d32d064e7

dbrgn commented 2 months ago

Two approvals, and we discussed this at the core meeting. Merging.