my take on a summary:
1) SVG Tiny 1.1 was agreed to be the minimum required.
Negotiation for
higher SVG support (basic and full and newer versions) is
allowed.
2) The modes of operation that will be supported are
one-to-one w/ mats
sync, muc with mats sync, and remote xmpp control entity
(i.e. server
component).
3) a MUC room attribute can be specified that let's a user
specify the
location of a whiteboard for MUC session - if jid matches
the MUC session
then muc is delivery point for wb messages, otherwise JID is
location of the
remote XMPP control entity (i.e. server component).
4) no one had objections to using a GOTO_PAGE action in
whiteboard for doing
page advances - useful in using whiteboarding for
presentations
5) jfcom agreed to write up a draft of the specification for
the community
to review. we will need mats to add his sync work to the
specification.
6) there were three main use cases for whiteboarding: free
for all (everyone
with r/w), presentation (one-to-many, presenter has r/w,
rest have read),
and auditorium (small group has r/w, rest have read)
decision was not made on the best way to notify people that
a whiteboarding
session is starting up. Both presence and invite approaches
were briefly
discussed - tabled until next meeting.
the appeared to be some general agreement if a whiteboard
board session is
associated with a MUC room, then there should be a way to
map the MUC perms
& roles directly into the whiteboard.
there was some discussion about layers and pages. svg 1.2
will add support
for pages but its finalization date is unknown, so there is
a need in the
near term to support the ability to create/delete/update
pages.
though SVG supports layering, it doesn't directly support
the traditional
concept of layers used in programs like Illustrator so we
will need to
specify a mechanism for creating, deleting, and updating
layers.
there was brief mention of the need to look into ways to do
multi user file
transfer - needed for transferring images in the
whiteboard. useful for
presentations.
as a side note: there a discussion about why some of the
jfcom user's chat
messages (from Transverse) were not visible to some members
of the session.
Remko and Keith worked on it today and should be resolved
soon. we believe
it had to do with PSI does not liking the xml:lang tag in
the 'body'
element.
boyd
On 6/27/06 6:49 PM, "Peter Saint-Andre"
<stpeter jabber.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mats Bengtsson wrote:
>> Peter,
>>
>> Perhaps you should add my memos for SVG/XMPP to the
list:
>>
>> http://coccinella.sourceforge.net/docs/MemoSVG_XMPP.txt
>> http://coccinella.sourceforge.net/docs/MemoSyncSVG-XM
PP.txt
>>
>> /Mats
>>
>> Peter Saint-Andre wrote:
>>>
>>> In essence there are three different
approaches, which we started to
>>> work on harmonizing (read the room log for
details):
>>>
>>
>
> Yes, I was going to write up a more detailed report
today but haven't
> gotten to it yet. Maybe this evening. 
>
> Peter
>
> - --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www
.jabber.org/people/stpeter.shtml
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
>
iD8DBQFEobXvNF1RSzyt3NURAsOTAJ98Yb6tekNdYvPx1+IuskPQjp1CBACd
GHIr
> rNdHm1lKMpmg3TXJoNbl+js=
> =mom8
> -----END PGP SIGNATURE-----
|