W3C home > Mailing lists > Public > www-smil@w3.org > April to June 2002

Re: please review: application/smil MIME type registration

From: Martin Duerst <duerst@w3.org>
Date: Fri, 05 Apr 2002 14:42:45 +0900
Message-Id: <4.2.0.58.J.20020405144041.0262a008@localhost>
To: Philipp Hoschka <ph@w3.org>, "Anders Nohlgren (EPL)" <Anders.Nohlgren@epl.ericsson.se>
Cc: ietf-types@iana.org, www-smil@w3.org
Hello Philipp,

I had a very quick look at this. I have only one very small
suggestion:

In things like:

 >>>>
3.  Registration Information

    To: ietf-types@iana.org
    Subject: Registration of MIME media type application/smil

    MIME media type name: application

    MIME subtype name: smil

    Required parameters: none

    Optional parameters:

    charset

    All of the considerations described in RFC3023 also apply to the SMIL
    media type.

    profile

    See Section 5 of this document.

    Encoding considerations:

    All of the considerations described in RFC3023 also apply to the SMIL
    media type.
 >>>>

I would prefer to change the formatting, so that the structure is
clearer. E.g.:

 >>>>
3.  Registration Information

    To: ietf-types@iana.org
    Subject: Registration of MIME media type application/smil

    MIME media type name: application

    MIME subtype name: smil

    Required parameters: none

    Optional parameters:

      charset

        All of the considerations described in RFC3023 also apply to the
        SMIL media type.

      profile

        See Section 5 of this document.

    Encoding considerations:

      All of the considerations described in RFC3023 also apply to the
      SMIL media type.
 >>>>

Regards,    Martin.






At 14:49 02/04/04 +0200, Philipp Hoschka wrote:
>Anders,
>
>I am picking this up again - sorry for the long delay.
>
>The optional parameter that you requested has been added to
>the latest draft - see
>http://www.ietf.org/internet-drafts/draft-hoschka-smil-media-type-09.txt
>
>-Philipp
>
>"Anders Nohlgren (EPL)" wrote:
> >
> > Philipp,
> > couldn't there be an optional parameter to the SMIL MIME type 
> (indicating e.g. profile) that could be used for content-negotiation 
> purposes? I fully understand your arguments that such a parameter is not 
> absolutely necessary, but in some cases it would be a useful feature. If 
> you want to deliver an optimised SMIL file to the client you should be 
> able to indicate the supported profile. The last sentence of clause 
> 14.4.4 in the SMIL 2.0 recommendation 
> (http://www.w3.org/TR/smil20/smil-basic.html#smilBasicNS-GuidePlayer) 
> talks about processing the test attributes already on the server side. 
> When doing so it would help to know the SMIL profile that the client 
> supports. Providing this with the MIME type would be efficient I think.
> >
> > Best regards,
> >                  Anders
> >
> > > -----Original Message-----
> > > From: Philipp Hoschka [mailto:ph@w3.org]
> > > Sent: 22 June 2001 19:45
> > > To: Peter Stark (ECS)
> > > Cc: ietf-types@iana.org; www-smil@w3.org
> > > Subject: Re: please review: application/smil MIME type registration
> > >
> > >
> > > Peter,
> > >
> > > I presume your use case is that a client should be able to
> > > request a SMIL-basic document via content-negotiation ?
> > > This is not the way SMIL basic works.
> > >
> > > All SMIL 2.0 documents are also SMIL basic documents
> > > http://www.w3.org/TR/smil20/smil-basic.html#BaseGuideNS-BasicDoc
> > >
> > > However, SMIL basic user agents interpret only a well-defined
> > > subset of the markup that may occur in a SMIL 2.0 docucment (see
> > > clause 5. and 7. at
> > > http://www.w3.org/TR/smil20/smil-basic.html#BaseGuideNS-BasicUserAgent
> > >
> > > To avoid an unsatisfactory user experience, an author can
> > > 1) only use markup defined for SMIL basic
> > > http://www.w3.org/TR/smil20/smil-basic.html#smilBasicNS-Basic
> > > 2) write a "scalable document" that adapts gracefully depending
> > > on whether it is played on a SMIL 2.0 or a SMIL basic user
> > > agent:
> > > http://www.w3.org/TR/smil20/smil-basic.html#smilBasicNS-GuideDoc
> > >
> > > The same approach can be applied to any profile, not just SMIL
> > > basic, and there is thus no need to use the MIME type to distinguish
> > > between profiles.
> > >
> > > -Philipp
> > >
> > > "Peter Stark (ECS)" a 馗rit :
> > > >
> > > > How does can it be used to distinguish between full SMIL
> > > 2.0 and a profile such as SMIL Basic?
> > > >
> > > > PS
> > > >
> > > > > -----Original Message-----
> > > > > From: Philipp Hoschka [mailto:ph@w3.org]
> > > > > Sent: den 21 juni 2001 18:03
> > > > > To: ietf-types@iana.org
> > > > > Cc: www-smil@w3.org
> > > > > Subject: please review: application/smil MIME type registration
> > > > >
> > > > >
> > > > > We'd like to start the two-week review of
> > > > >
> > > > > http://search.ietf.org/internet-drafts/draft-hoschka-smil-medi
> > > > > a-type-08.txt
> > > > >
> > > > > describing the registration of the application/smil MIME type for
> > > > > SMIL 1.0 and SMIL 2.0.
> > > > >
> > > > > -Philipp Hoschka, W3C
> > > > >
> > >
>_______________________________________________
>Ietf-types mailing list
>Ietf-types@eikenes.alvestrand.no
>http://www.alvestrand.no/mailman/listinfo/ietf-types
Received on Friday, 5 April 2002 02:42:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:53:27 GMT