Re: [XCON] Cloning: Additional data in the data model
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [XCON] Cloning: Additional data in the data model
Hi Oscar,
sorry for the late reply. IMHO, we might need in the data model:
1. information about the father/son relationship. This might be an
attribute, e.g.:
<xs:attribute name="fatherEntity" type="xs:anyURI" use="optional"/>
2. information about the conference/sidebar relationship, e.g.:
<xs:attribute name="sidebarOf" type="xs:anyURI" use="optional"/>.
As to the "parent enforceable" relationship, I would leave it outside
of the data model.
Cheers,
Simon
Quoting Oscar Novo <oscar.novo at ericsson.com>:
Hi folks,
In IETF-73 has been a proposal to expand the data model to support the
cloning method defined in the framework. At the moment, the data model
supports the cloning method though the 'cascaded-focus' element which
contains a 'parent' conference URI but it might be needed to add few
more elements to be align with CCMP.
Some elements that could be added are:
- An element that contains all the 'non-independent' children
conferences
- A policy attribute/element that indicates the "parent enforceable" of
every element. However, it would make more sense to add it in a draft
that discusses conference policies.
It would be nice to know the opinion of the WG whether we want to
support entirely this property or not.
Cheers,
Oscar
--
_\\|//_
( O-O )
~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
Simon Pietro Romano
Universita' di Napoli Federico II
Computer Science Department
Phone: +39 081 7683823 -- Fax: +39 081 7684219
e-mail: spromano at unina.it
<<Molti mi dicono che lo scoraggiamento è l'alibi degli
idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
oooO
~~~~~~~~~~~~~~~~~~~~~~( )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
\ ( ( )
\_) ) /
(_/
_______________________________________________
XCON mailing list
XCON at ietf.org
https://www.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.