Planning mode

[toto]

One thing to consider is, if we want to allow sessions without time/date in sort of a planning mode.

This would enable a few use cases we have not covered and is typical for all conferences I know of:

• You could do something like halfnarp with re-data
• For an app I would imagine that it would go into a "planning mode" where you can pre-pick your fav sessions before the final timeslots are selected.

Technically I would make two adjustments:

• Make day and begin, end optional for sessions
• Add some kind of state to the event so that an API consumer can easily tell that state the conference is in and whether he supports it (not all apps make sense in planning mode, some only there).

What do you say?

[yetzt]

seems to be a legit use case

[axxg]

I think this is a bad idea. A session should always have these attributes. If a session doesn't have these attributes, it isn't a session rather a draft. In my opinion that's a function of the planning tool and not the task of a standardized API.

[yetzt]

i think having a list of proposed or not yet scheduled sessions could have interesting use cases. maybe providing a state-value could be agreeable?

[axxg]

I think this is the system architecture:

• The congress-app has only final data and displays it, without rights restrictions.
• The plan-app has management functions, a upload/export function, a rights management and various other feature.

So, what is our goal?

[MichaelKreil]

I have some problems/ideas too.
Let us discuss it on Wednesday, after our re:data meeting, ok? :)

Michael