[XCON] some useless notes I took in first half of session
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[XCON] some useless notes I took in first half of session



20 people showed up

Mary presented framework stuff

On bridge have - Brian

Policy looks like it is just Rules.

Disagreement about if template is schema or object

We need a term for the thing that thing that is one to one related to a
focus. Could call it a conference instance, or an occurrence. Need to table
this and figure out a name later.

We need be able Name for individual instance for the set of instances.

Also want to be able to say I want the next instance out of the set of
instances.

Do we want to be able to find the the instances in a set that are also in a
particular time range.

People might want to read draft-royer-calsch-cap-01.txt

The template, pattern issue .... Few differences
1) what's a document
2) what object contains what object

On 1 - this is something a human can read - it might contain and xsd - has
English that explains the semantic text.
Agree have RFC that holds some text that is registered with IANA - has
English semantics plus a schema - also has a name.

When a xcon client makes a reservation, it uses an ical object to set time
and recurrence. 

When you have a series, you can ask for meeting at a particular time range
using ical and it gives you a handle to an instance.

Can edit instances or series in same way depending on what handle you have.

We schedule a conf include an iCal that say every Tuesday. Get back handle
A. Then we do a query to get an instance and pass in  another iCal range and
get back B. Then we edit B.

Everyone though should use CPL for rules.

Need to add in a single URI that you go to to schedule new conferences.

Need security protocol relationship to make floor control work.



_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.