Schedule2

[saerdnaer]

breaking changes to the schedule.json schema, thereby a own new version called schedule2, see 6632bbb for an comparison between the formats

• some unused fields get dropped, e.g. public_name, daysCount, timeslot_duration, …
• Track: color -> colors to allow multiple color values e.g. for light an dark – and to be uniform to same attribute on Conference
• Track: gets a guid field
• translations of abstract, description etc. get switched from Accept header "string" to object {"en": "string", "de": "string"}, but the old way is still allowed
• Day: day_start and day_end get's unified to start and end
• events and persons get it's own top level field, and are no longer nested
  • but events still have to be sorted by date and room.order as before by the schedule generator/serializer
  • connection from Event to Person is named Participant and has a role attribute
• Images like logo and avatar are now an object {"url": "uri-string"} instead of "uri-string"
• Event has now start and end instead of date and duration, fixing Clarify duration spec #129

TODOs

• decide how the references on Event to track and room should look like
• decided if Participant.role should be an enum
• add Reference.service enum based on ucdata

[saerdnaer]

@toto Sollen wir die kompletten Services hierher in schedule2 mit übernehmen?

https://github.com/toto/conference-import/blob/e51e5a35788a6735a724ece59e84018efd18dc41/src/models/link.ts#L1-L8

service: "web" | "twitter" | "facebook" | "github" | "youtube" | "vimeo" | "mastodon" | "bluesky" | "threads" | "vimeo" | "livevoice" | "activityPub"

[toto]

Not all pick: that's historical baggage. How about

• Video: YouTube, Vimeo
• Social: Facebook, ActivityPub, LinkedIn, GitHub and threads.
  Plus "web" as the default.

[Kunsi]

If we're defining multiple colours, we should add a field for preferred colour scheme so apps know which to select in case there's no user choice.

[Kunsi]

An additional question would be if it really makes sense to have different colours for light and dark mode here, if the Conference only defines a primary and background colour.

[Kunsi]

Same as with track colours, we should have a field for the "default" language.

[Kunsi]

I'm slightly in favour to removing the string option here and to only allow objects with localized strings. This will make it easier for apps that try to parse the schedule.