OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [office] auto-play presentation file format like PPS

It's not just a WHAT. I don't think that the concept applies to other
document types. The idea of starting a presentation automatically is
not the same as using a word processor document in an ebook-like mode.
There may be some similarities, but it is definitely not the same.

David has made a good case for the validity of the use case of
ebook-like functionality. Having said that, I don't have a good
description for it. We could always reserve the mode name and not
explicitly define what it does. It would allow the apps to innovate
and develop a best practice before we standardize it.

Here's how I classify the current proposed modes:

Modes I can define:
* edit
* read-only
* presentation-auto-start

Modes I don't have a good enough feel of to define:
* wordprocessor-ebook

Here's my summary of the situation as I understand it:

Issues with consensus:
* the tag should be called "preferred-view-mode"
* possible values for "preferred-view-mode" tag
  * edit
  * readonly
* the "preferred-view-mode" will have no default
* apps should be able to define custom values of "preferred-view-mode"

Unresolved issues:
* how applications represent custom values for "preferred-view-mode"
(maybe prepend with x- like email headers to avoid pollution of global
(i.e. spec defined) namespace)
* other standard defined values of the "preferred-view-mode" tag
(presentation-auto-start, play, wordprocessor-ebook)
* there should be a mode to represent a presentation that starts automatically
* there should be a mode that is something like an ebook for word processor docs


On Sun, May 4, 2008 at 10:51 AM, Ming Fei Jia <jiamingf@cn.ibm.com> wrote:
> Warren,
>  I don't think we have disagreement in nature about the understanding of the
> preferred view mode "auto-play". Yes, this attribute  would indicate that
> the author wants the presentation to start as soon as possible after the
> file is opened. But I emphasize presentation will start "WHAT" upon the file
> is opened. I understand it should be "start playing" or "start presenting".
> Also I don't think this situation is different from "edit" and "read-only"
> modes, just like "start editing" after the file is opened, and "start
> viewing without allowing modification" after the file is opened. We can call
> the other 2 modes as "edit" and "read-only", why can not we call the third
> mode as "play"? This "WHAT" is just the mode name. Additionally, I
> understand "auto" here means "as soon as possible after the file is opened",
> which can be put into description part. So I think "presentation-auto-start"
> surely describes the user scenario accurately, but it is not appropriate to
> be a view mode name.
>  Another issue is whether or not the preferred view mode contains the
> application name. I understand that your idea is to let future applications
> customize the preferred view mode by a flexible way. That's a good idea. But
> I think that will lead to trivial definitions like
> "X1-play","X2-play","X3-play",etc. It'd better just define a generic "play"
> there, which could cover the future requirements, just like "edit" now could
> cover many applications which have editing features.
>  Your suggestions and comments help me understand the preferred view modes
> clearly. Till now, with many suggestions from TC members, this proposal
> almost achieves consensus only with the above minor naming issues. I think
> we need to move on productively, and should not block here for the minor
> issues. I guess maybe this is why Rob explained and suggested the
> alternative in previous notes. Actually, it does not matter for me what the
> mode name is. When 2 options are both reasonable, I agree with most of TC
> members.
>  BTW, "readonly" need to change to "read-only".
>  Sincerely,
>  _________________________________________________________
>  Mingfei Jia
>  Symphony Common Apps and Performance | jiamingf@cn.ibm.com
>  IBM Corporation | Lotus Software
>  8610-8245-2493 (phone) | 915-2493 (tie-line)
> Re: [office] auto-play presentation file format like PPS
> Re: [office] auto-play presentation file format like PPS
>  Warren Turkal
>  to:
>  robert_weir
> 2008-05-01 06:17
>  Cc:
>  office
>  ________________________________
> On Wed, Apr 30, 2008 at 1:52 PM,  <robert_weir@us.ibm.com> wrote:
>  > "The foo attribute, when set to true, indicates that the document should
> be
>  > loaded and displayed using a presentation-oriented user experience mode
>  > rather than an authoring-oriented user experience mode.  The details of
>  > these two modes are implementation-dependent, but typically a
>  > presentation-oriented mode will suppress an editing user interface and
> will
>  > instead be optimized for viewing and navigating the document."
>  Are you suggesting that, instead of defining another value for
>  "preferred-view-mode", we have we have a completely separate
>  attribute? I don't think that'd be needed. I do think that this should
>  be implemented as a preferred-view-mode.
>  In my view of the world, the value of "foo" on the attribute
>  "preferred-view-mode" would indicate that the author wants the
>  presentation to start as soon as possible after the file is opened. It
>  would be something like opening a presentation in OO Impress and a
>  ghost pressing F5 immediately.
>  This behavior isn't intended to bypass security checks. E.g. if the
>  presentation document contains scripts, the app would still have to
>  authorize the execution of those scripts somehow.
>  wt
>  ---------------------------------------------------------------------
>  To unsubscribe from this mail list, you must leave the OASIS TC that
>  generates this mail.  You may a link to this group and all your TCs in
>  at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]