Subject: Online Registartion at www.iana.org
From: [email-masked] (Marc Mutz)
Date: Tue, 30 Apr 2002 19:39:02 +0200

Hi!

Are Online Registrations from www.iana.org posted here?

Marc

- -- 
Marc Mutz <[email-masked]>

From: jeanluc.mc at wanadoo.fr (jeanluc)
Date: Tue Jan  3 16:22:31 2006
Subject: sp midi and nokia ringtones
Message-ID: <004401c1e499$624060c0$bb1afea9@8030cwh20156>

hi,

I'm a french composer, and I try to create an sp-midi file for nokia 3510 and communicator

I use beatnik since 2 years and I know that a mini Beatnik Audio Engine is in some nokia phones.

I'm waiting for Scalable Polyphony MIDI Specification and Device Profiles  by MMa.
 
 I try to create an sp-midi file. To do that , musician must embed at the top of the midifile a "mip "
code( in hexadecimal code )..This mip code allow to reduce or increase polyphony of a midifile
for 4-polyphony device or 8 or16- polyphony device....
This mip code is just a sys-ex message, in hexadecimal code.The hex is in the MMA's specification. Also in the spec. are the device ID's for upcoming phones.

Do you know :
How can I put the correct "'MIP" code in my sp-midi file ?

Have you in hexdecimal code thi mip code, with device ID's ?

How can I test a sp-midi file exept on a phone and beatnik editor? 

can I test a file on a desktop nkia 3510 phone emulator?

thanks,

 my website:          www.kitmusica.com (flashsound api and beatnik)

 try our beatnik mixer    www.kitmusica.com/introbeat.htm  (beatnik)

a sonified  web site     www.helentraiteur.com, by kitmusica (beatnik)

a sonified  gypsy web site    http://jeanluc.borla.free.fr/chico4/chico.htm (flashsound api)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20020415/a319cb94/attachment.html
>From [email-masked]  Tue Apr 30 19:39:02 2002
From: mutz at kde.org (Marc Mutz)
Date: Tue Jan  3 16:22:31 2006
Subject: Online Registartion at www.iana.org
Message-ID: <[email-masked]>

Hi!

Are Online Registrations from www.iana.org posted here?

Marc

- -- 
Marc Mutz <[email-masked]>

From: jeanluc" <[email-masked] (jeanluc)
Date: Mon, 15 Apr 2002 18:18:27 +0200
Subject: sp midi and nokia ringtones
Message-ID: <004401c1e499$624060c0$bb1afea9@8030cwh20156>

This is a multi-part message in MIME format.

------=_NextPart_000_003F_01C1E4A9.F096B8A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hi,

I'm a french composer, and I try to create an sp-midi file for nokia =
3510 and communicator

I use beatnik since 2 years and I know that a mini Beatnik Audio Engine =
is in some nokia phones.

I'm waiting for Scalable Polyphony MIDI Specification and Device =
Profiles  by MMa.
=20
 I try to create an sp-midi file. To do that , musician must embed at =
the top of the midifile a "mip "
code( in hexadecimal code )..This mip code allow to reduce or increase =
polyphony of a midifile
for 4-polyphony device or 8 or16- polyphony device....
This mip code is just a sys-ex message, in hexadecimal code.The hex is =
in the MMA's specification. Also in the spec. are the device ID's for =
upcoming phones.

Do you know :
How can I put the correct "'MIP" code in my sp-midi file ?

Have you in hexdecimal code thi mip code, with device ID's ?

How can I test a sp-midi file exept on a phone and beatnik editor?=20

can I test a file on a desktop nkia 3510 phone emulator?

thanks,

=20

 my website:          www.kitmusica.com (flashsound api and beatnik)

 try our beatnik mixer    www.kitmusica.com/introbeat.htm  (beatnik)

a sonified  web site     www.helentraiteur.com, by kitmusica (beatnik)

a sonified  gypsy web site    =
http://jeanluc.borla.free.fr/chico4/chico.htm (flashsound api)

------=_NextPart_000_003F_01C1E4A9.F096B8A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<P><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2><FONT =
face=3DArial=20
size=3D2>hi,</FONT></P>
<DIV><FONT face=3DArial size=3D2>
<P><FONT face=3DArial size=3D2>I'm a french composer, and I try to =
create an sp-midi=20
file for nokia 3510 and communicator</FONT></P>
<P><FONT face=3DArial size=3D2>I use beatnik since 2 years and I know =
that a mini=20
Beatnik Audio Engine is in some nokia phones.</FONT></P></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV>I'm waiting for <STRONG><EM>Scalable Polyphony MIDI Specification =
and=20
Device Profiles&nbsp; by MMa.</EM></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;I try to create an sp-midi file. To do that , musician must =
embed at=20
the top of the midifile a "mip "</FONT></DIV></DIV>
<DIV>code( in hexadecimal code )..This mip code allow to reduce or =
increase=20
polyphony of a midifile</DIV>
<DIV>for 4-polyphony device or 8 or16- polyphony device....</DIV>
<DIV>This mip code is just a sys-ex message, in hexadecimal code.The hex =
is in=20
the MMA's specification. Also in the spec. are the device ID's for =
upcoming=20
phones.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Do you know :</FONT></DIV>
<DIV>
<P><FONT face=3DArial size=3D2>How can I put the correct "'MIP" code in =
my sp-midi=20
file ?</FONT></P>
<P><FONT face=3DArial size=3D2>Have you&nbsp;in hexdecimal code thi mip =
code, with=20
device ID's ?</FONT></P>
<P><FONT face=3DArial size=3D2>How can I test a sp-midi file exept on a =
phone and=20
beatnik editor? </FONT></P>
<P><FONT face=3DArial size=3D2>can I test a file on a desktop nkia 3510 =
phone=20
emulator?</FONT></P></DIV>
<P>thanks,</P>
<P></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2>&nbsp;my=20
website:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.kitmusica.com">www.kitmusica.com</A>&nbsp;<EM>(flashso=
und api=20
and beatnik</EM>)</FONT></P>
<P><FONT face=3DArial size=3D2>&nbsp;try our beatnik =
mixer&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.kitmusica.com/introbeat.htm">www.kitmusica.com/introbe=
at.htm</A>&nbsp;=20
<EM>(beatnik)</EM></FONT></P>
<P>a sonified&nbsp;&nbsp;web site&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.helentraiteur.com">www.helentraiteur.com</A>, by =
kitmusica=20
(beatnik)</FONT></P>
<P><FONT face=3DArial size=3D2>a sonified&nbsp;&nbsp;gypsy web=20
site&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://jeanluc.borla.free.fr/chico4/chico.htm">http://jeanluc.bor=
la.free.fr/chico4/chico.htm</A>&nbsp;(flashsound=20
api)</FONT></P>
<P></FONT>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>
<OBJECT classid=3Dclsid:D27CDB6E-AE6D-11cf-96B8-444553540000=20
codeBase=3Dhttp://download.macromedia.com/pub/shockwave/cabs/flash/swflas=
h.cab#version=3D4,0,2,0=20
height=3D28 width=3D26><PARAM NAME=3D"_cx" VALUE=3D"688"><PARAM =
NAME=3D"_cy" VALUE=3D"741"><PARAM NAME=3D"FlashVars" =
VALUE=3D"688"><PARAM NAME=3D"Movie" =
VALUE=3D"http://www.kitmusica.com/swf/logomail.swf"><PARAM NAME=3D"Src" =
VALUE=3D"http://www.kitmusica.com/swf/logomail.swf"><PARAM =
NAME=3D"WMode" VALUE=3D"Window"><PARAM NAME=3D"Play" VALUE=3D"-1"><PARAM =
NAME=3D"Loop" VALUE=3D"-1"><PARAM NAME=3D"Quality" VALUE=3D"High"><PARAM =
NAME=3D"SAlign" VALUE=3D""><PARAM NAME=3D"Menu" VALUE=3D"-1"><PARAM =
NAME=3D"Base" VALUE=3D""><PARAM NAME=3D"Scale" VALUE=3D"ShowAll"><PARAM =
NAME=3D"DeviceFont" VALUE=3D"0"><PARAM NAME=3D"EmbedMovie" =
VALUE=3D"0"><PARAM NAME=3D"BGColor" VALUE=3D""><PARAM NAME=3D"SWRemote" =
VALUE=3D"">
            <embed src=3D"http://www.kitmusica.com/swf/logomail.swf" =
quality=3Dhigh=20
pluginspage=3D"http://www.macromedia.com/shockwave/download/index.cgi?P1_=
Prod_Version=3DShockwaveFlash"=20
type=3D"application/x-shockwave-flash" width=3D"26" height=3D"28">    =
</embed>  =20
</OBJECT></P></DIV></BODY></HTML>

------=_NextPart_000_003F_01C1E4A9.F096B8A0--

From: ietf-xml-use at NineByNine.org (Graham Klyne)
Date: Tue Jan  3 16:22:31 2006
Subject: Fwd: I-D ACTION:draft-swartz-rdfcore-rdfxml-mediatype-00.txt
Message-ID: <[email-masked]>

All,

The following was recently published as a work item of the W3C RDFcore 
working group.  It is our hope that when the specification documents are 
stabilized as W3C recommendations (hopefully, quite soon) we can move this 
forward promptly for RFC publication.

If there's anything here likely to be problematic, we'd appreciate knowing 
sooner rather than later.

#g
--

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : application/rdf+xml Media Type Registration
>         Author(s)       : A. Swartz
>         Filename        : draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>         Pages           :
>         Date            : 05-Apr-02
>
>This document describes a media type (application/rdf+xml) for use
>with the XML serialization of the Resource Description Framework
>(RDF).  RDF is a language designed to support the Semantic Web, by
>facilitating resource description and data exchange on the Web.  RDF
>provides common structures that can be used for interoperable data
>exchange and follows the World Wide Web Consortium (W3C) design
>principles of interoperability, evolution, and decentralization.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         [email-masked].
>In the body type:
>         "FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <[email-masked]>
>
>ENCODING mime
>FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt>

-------------------
Graham Klyne
<[email-masked]>

From: [email-masked] (Graham Klyne)
Date: Tue, 09 Apr 2002 20:14:30 +0100
Subject: Fwd: I-D ACTION:draft-swartz-rdfcore-rdfxml-mediatype-00.txt
Message-ID: <[email-masked]>

All,

The following was recently published as a work item of the W3C RDFcore 
working group.  It is our hope that when the specification documents are 
stabilized as W3C recommendations (hopefully, quite soon) we can move this 
forward promptly for RFC publication.

If there's anything here likely to be problematic, we'd appreciate knowing 
sooner rather than later.

#g
--

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : application/rdf+xml Media Type Registration
>         Author(s)       : A. Swartz
>         Filename        : draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>         Pages           :
>         Date            : 05-Apr-02
>
>This document describes a media type (application/rdf+xml) for use
>with the XML serialization of the Resource Description Framework
>(RDF).  RDF is a language designed to support the Semantic Web, by
>facilitating resource description and data exchange on the Web.  RDF
>provides common structures that can be used for interoperable data
>exchange and follows the World Wide Web Consortium (W3C) design
>principles of interoperability, evolution, and decentralization.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         [email-masked].
>In the body type:
>         "FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <[email-masked]>
>
>ENCODING mime
>FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt>

-------------------
Graham Klyne
<[email-masked]>

From: duerst at w3.org (Martin Duerst)
Date: Tue Jan  3 16:22:31 2006
Subject: please review: application/smil MIME type registration
In-Reply-To: <[email-masked]>
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <4.2.0.58.J.20020405144041.0262a008@localhost>

Hello Philipp,

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

In things like:

 >>>>
3.  Registration Information

    To: [email-masked]
    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: [email-masked]
    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:[email-masked]]
> > > Sent: 22 June 2001 19:45
> > > To: Peter Stark (ECS)
> > > Cc: [email-masked]; [email-masked]
> > > 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:[email-masked]]
> > > > > Sent: den 21 juni 2001 18:03
> > > > > To: [email-masked]
> > > > > Cc: [email-masked]
> > > > > 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
>[email-masked]
>http://www.alvestrand.no/mailman/listinfo/ietf-types

From: [email-masked] (Martin Duerst)
Date: Fri, 05 Apr 2002 14:42:45 +0900
Subject: please review: application/smil MIME type registration
In-Reply-To: <[email-masked]>
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <4.2.0.58.J.20020405144041.0262a008@localhost>

Hello Philipp,

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

In things like:

 >>>>
3.  Registration Information

    To: [email-masked]
    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: [email-masked]
    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:[email-masked]]
> > > Sent: 22 June 2001 19:45
> > > To: Peter Stark (ECS)
> > > Cc: [email-masked]; [email-masked]
> > > 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 $BqD(Brit :
> > > >
> > > > 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:[email-masked]]
> > > > > Sent: den 21 juni 2001 18:03
> > > > > To: [email-masked]
> > > > > Cc: [email-masked]
> > > > > 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
>[email-masked]
>http://www.alvestrand.no/mailman/listinfo/ietf-types

From: ph at w3.org (Philipp Hoschka)
Date: Tue Jan  3 16:22:31 2006
Subject: please review: application/smil MIME type registration
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <[email-masked]>

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:[email-masked]]
> > Sent: 22 June 2001 19:45
> > To: Peter Stark (ECS)
> > Cc: [email-masked]; [email-masked]
> > 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 ?crit :
> > >
> > > 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:[email-masked]]
> > > > Sent: den 21 juni 2001 18:03
> > > > To: [email-masked]
> > > > Cc: [email-masked]
> > > > 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
> > > >
> >

From: [email-masked] (Philipp Hoschka)
Date: Thu, 04 Apr 2002 14:49:29 +0200
Subject: please review: application/smil MIME type registration
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <[email-masked]>

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:[email-masked]]
> > Sent: 22 June 2001 19:45
> > To: Peter Stark (ECS)
> > Cc: [email-masked]; [email-masked]
> > 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 écrit :
> > >
> > > 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:[email-masked]]
> > > > Sent: den 21 juni 2001 18:03
> > > > To: [email-masked]
> > > > Cc: [email-masked]
> > > > 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
> > > >
> >

From: [email-masked] (Marc Mutz)
Date: Tue, 30 Apr 2002 19:39:02 +0200
Subject: Online Registartion at www.iana.org
Message-ID: <[email-masked]>

Hi!

Are Online Registrations from www.iana.org posted here?

Marc

- -- 
Marc Mutz <[email-masked]>

From: jeanluc" <[email-masked] (jeanluc)
Date: Mon, 15 Apr 2002 18:18:27 +0200
Subject: sp midi and nokia ringtones
Message-ID: <004401c1e499$624060c0$bb1afea9@8030cwh20156>

This is a multi-part message in MIME format.

------=_NextPart_000_003F_01C1E4A9.F096B8A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hi,

I'm a french composer, and I try to create an sp-midi file for nokia =
3510 and communicator

I use beatnik since 2 years and I know that a mini Beatnik Audio Engine =
is in some nokia phones.

I'm waiting for Scalable Polyphony MIDI Specification and Device =
Profiles  by MMa.
=20
 I try to create an sp-midi file. To do that , musician must embed at =
the top of the midifile a "mip "
code( in hexadecimal code )..This mip code allow to reduce or increase =
polyphony of a midifile
for 4-polyphony device or 8 or16- polyphony device....
This mip code is just a sys-ex message, in hexadecimal code.The hex is =
in the MMA's specification. Also in the spec. are the device ID's for =
upcoming phones.

Do you know :
How can I put the correct "'MIP" code in my sp-midi file ?

Have you in hexdecimal code thi mip code, with device ID's ?

How can I test a sp-midi file exept on a phone and beatnik editor?=20

can I test a file on a desktop nkia 3510 phone emulator?

thanks,

=20

 my website:          www.kitmusica.com (flashsound api and beatnik)

 try our beatnik mixer    www.kitmusica.com/introbeat.htm  (beatnik)

a sonified  web site     www.helentraiteur.com, by kitmusica (beatnik)

a sonified  gypsy web site    =
http://jeanluc.borla.free.fr/chico4/chico.htm (flashsound api)

------=_NextPart_000_003F_01C1E4A9.F096B8A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<P><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2><FONT =
face=3DArial=20
size=3D2>hi,</FONT></P>
<DIV><FONT face=3DArial size=3D2>
<P><FONT face=3DArial size=3D2>I'm a french composer, and I try to =
create an sp-midi=20
file for nokia 3510 and communicator</FONT></P>
<P><FONT face=3DArial size=3D2>I use beatnik since 2 years and I know =
that a mini=20
Beatnik Audio Engine is in some nokia phones.</FONT></P></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV>I'm waiting for <STRONG><EM>Scalable Polyphony MIDI Specification =
and=20
Device Profiles&nbsp; by MMa.</EM></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;I try to create an sp-midi file. To do that , musician must =
embed at=20
the top of the midifile a "mip "</FONT></DIV></DIV>
<DIV>code( in hexadecimal code )..This mip code allow to reduce or =
increase=20
polyphony of a midifile</DIV>
<DIV>for 4-polyphony device or 8 or16- polyphony device....</DIV>
<DIV>This mip code is just a sys-ex message, in hexadecimal code.The hex =
is in=20
the MMA's specification. Also in the spec. are the device ID's for =
upcoming=20
phones.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Do you know :</FONT></DIV>
<DIV>
<P><FONT face=3DArial size=3D2>How can I put the correct "'MIP" code in =
my sp-midi=20
file ?</FONT></P>
<P><FONT face=3DArial size=3D2>Have you&nbsp;in hexdecimal code thi mip =
code, with=20
device ID's ?</FONT></P>
<P><FONT face=3DArial size=3D2>How can I test a sp-midi file exept on a =
phone and=20
beatnik editor? </FONT></P>
<P><FONT face=3DArial size=3D2>can I test a file on a desktop nkia 3510 =
phone=20
emulator?</FONT></P></DIV>
<P>thanks,</P>
<P></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2>&nbsp;my=20
website:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.kitmusica.com">www.kitmusica.com</A>&nbsp;<EM>(flashso=
und api=20
and beatnik</EM>)</FONT></P>
<P><FONT face=3DArial size=3D2>&nbsp;try our beatnik =
mixer&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.kitmusica.com/introbeat.htm">www.kitmusica.com/introbe=
at.htm</A>&nbsp;=20
<EM>(beatnik)</EM></FONT></P>
<P>a sonified&nbsp;&nbsp;web site&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.helentraiteur.com">www.helentraiteur.com</A>, by =
kitmusica=20
(beatnik)</FONT></P>
<P><FONT face=3DArial size=3D2>a sonified&nbsp;&nbsp;gypsy web=20
site&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://jeanluc.borla.free.fr/chico4/chico.htm">http://jeanluc.bor=
la.free.fr/chico4/chico.htm</A>&nbsp;(flashsound=20
api)</FONT></P>
<P></FONT>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>
<OBJECT classid=3Dclsid:D27CDB6E-AE6D-11cf-96B8-444553540000=20
codeBase=3Dhttp://download.macromedia.com/pub/shockwave/cabs/flash/swflas=
h.cab#version=3D4,0,2,0=20
height=3D28 width=3D26><PARAM NAME=3D"_cx" VALUE=3D"688"><PARAM =
NAME=3D"_cy" VALUE=3D"741"><PARAM NAME=3D"FlashVars" =
VALUE=3D"688"><PARAM NAME=3D"Movie" =
VALUE=3D"http://www.kitmusica.com/swf/logomail.swf"><PARAM NAME=3D"Src" =
VALUE=3D"http://www.kitmusica.com/swf/logomail.swf"><PARAM =
NAME=3D"WMode" VALUE=3D"Window"><PARAM NAME=3D"Play" VALUE=3D"-1"><PARAM =
NAME=3D"Loop" VALUE=3D"-1"><PARAM NAME=3D"Quality" VALUE=3D"High"><PARAM =
NAME=3D"SAlign" VALUE=3D""><PARAM NAME=3D"Menu" VALUE=3D"-1"><PARAM =
NAME=3D"Base" VALUE=3D""><PARAM NAME=3D"Scale" VALUE=3D"ShowAll"><PARAM =
NAME=3D"DeviceFont" VALUE=3D"0"><PARAM NAME=3D"EmbedMovie" =
VALUE=3D"0"><PARAM NAME=3D"BGColor" VALUE=3D""><PARAM NAME=3D"SWRemote" =
VALUE=3D"">
            <embed src=3D"http://www.kitmusica.com/swf/logomail.swf" =
quality=3Dhigh=20
pluginspage=3D"http://www.macromedia.com/shockwave/download/index.cgi?P1_=
Prod_Version=3DShockwaveFlash"=20
type=3D"application/x-shockwave-flash" width=3D"26" height=3D"28">    =
</embed>  =20
</OBJECT></P></DIV></BODY></HTML>

------=_NextPart_000_003F_01C1E4A9.F096B8A0--

From: [email-masked] (Graham Klyne)
Date: Tue, 09 Apr 2002 20:14:30 +0100
Subject: Fwd: I-D ACTION:draft-swartz-rdfcore-rdfxml-mediatype-00.txt
Message-ID: <[email-masked]>

All,

The following was recently published as a work item of the W3C RDFcore 
working group.  It is our hope that when the specification documents are 
stabilized as W3C recommendations (hopefully, quite soon) we can move this 
forward promptly for RFC publication.

If there's anything here likely to be problematic, we'd appreciate knowing 
sooner rather than later.

#g
--

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : application/rdf+xml Media Type Registration
>         Author(s)       : A. Swartz
>         Filename        : draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>         Pages           :
>         Date            : 05-Apr-02
>
>This document describes a media type (application/rdf+xml) for use
>with the XML serialization of the Resource Description Framework
>(RDF).  RDF is a language designed to support the Semantic Web, by
>facilitating resource description and data exchange on the Web.  RDF
>provides common structures that can be used for interoperable data
>exchange and follows the World Wide Web Consortium (W3C) design
>principles of interoperability, evolution, and decentralization.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         [email-masked].
>In the body type:
>         "FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <[email-masked]>
>
>ENCODING mime
>FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt>

-------------------
Graham Klyne
<[email-masked]>

From: [email-masked] (Martin Duerst)
Date: Fri, 05 Apr 2002 14:42:45 +0900
Subject: please review: application/smil MIME type registration
In-Reply-To: <[email-masked]>
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <4.2.0.58.J.20020405144041.0262a008@localhost>

Hello Philipp,

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

In things like:

 >>>>
3.  Registration Information

    To: [email-masked]
    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: [email-masked]
    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:[email-masked]]
> > > Sent: 22 June 2001 19:45
> > > To: Peter Stark (ECS)
> > > Cc: [email-masked]; [email-masked]
> > > 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 $BqD(Brit :
> > > >
> > > > 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:[email-masked]]
> > > > > Sent: den 21 juni 2001 18:03
> > > > > To: [email-masked]
> > > > > Cc: [email-masked]
> > > > > 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
>[email-masked]
>http://www.alvestrand.no/mailman/listinfo/ietf-types

From: [email-masked] (Philipp Hoschka)
Date: Thu, 04 Apr 2002 14:49:29 +0200
Subject: please review: application/smil MIME type registration
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <[email-masked]>

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:[email-masked]]
> > Sent: 22 June 2001 19:45
> > To: Peter Stark (ECS)
> > Cc: [email-masked]; [email-masked]
> > 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 écrit :
> > >
> > > 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:[email-masked]]
> > > > Sent: den 21 juni 2001 18:03
> > > > To: [email-masked]
> > > > Cc: [email-masked]
> > > > 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
> > > >
> >

From: [email-masked] (Marc Mutz)
Date: Tue, 30 Apr 2002 19:39:02 +0200
Subject: Online Registartion at www.iana.org
Message-ID: <[email-masked]>

Hi!

Are Online Registrations from www.iana.org posted here?

Marc

- -- 
Marc Mutz <[email-masked]>

From: jeanluc.mc at wanadoo.fr (jeanluc)
Date: Tue Jan  3 16:22:31 2006
Subject: sp midi and nokia ringtones
Message-ID: <004401c1e499$624060c0$bb1afea9@8030cwh20156>

hi,

I'm a french composer, and I try to create an sp-midi file for nokia 3510 and communicator

I use beatnik since 2 years and I know that a mini Beatnik Audio Engine is in some nokia phones.

I'm waiting for Scalable Polyphony MIDI Specification and Device Profiles  by MMa.
 
 I try to create an sp-midi file. To do that , musician must embed at the top of the midifile a "mip "
code( in hexadecimal code )..This mip code allow to reduce or increase polyphony of a midifile
for 4-polyphony device or 8 or16- polyphony device....
This mip code is just a sys-ex message, in hexadecimal code.The hex is in the MMA's specification. Also in the spec. are the device ID's for upcoming phones.

Do you know :
How can I put the correct "'MIP" code in my sp-midi file ?

Have you in hexdecimal code thi mip code, with device ID's ?

How can I test a sp-midi file exept on a phone and beatnik editor? 

can I test a file on a desktop nkia 3510 phone emulator?

thanks,

 my website:          www.kitmusica.com (flashsound api and beatnik)

 try our beatnik mixer    www.kitmusica.com/introbeat.htm  (beatnik)

a sonified  web site     www.helentraiteur.com, by kitmusica (beatnik)

a sonified  gypsy web site    http://jeanluc.borla.free.fr/chico4/chico.htm (flashsound api)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20020415/a319cb94/attachment.html
>From [email-masked]  Tue Apr 30 19:39:02 2002
From: mutz at kde.org (Marc Mutz)
Date: Tue Jan  3 16:22:31 2006
Subject: Online Registartion at www.iana.org
Message-ID: <[email-masked]>

Hi!

Are Online Registrations from www.iana.org posted here?

Marc

- -- 
Marc Mutz <[email-masked]>

From: jeanluc" <[email-masked] (jeanluc)
Date: Mon, 15 Apr 2002 18:18:27 +0200
Subject: sp midi and nokia ringtones
Message-ID: <004401c1e499$624060c0$bb1afea9@8030cwh20156>

This is a multi-part message in MIME format.

------=_NextPart_000_003F_01C1E4A9.F096B8A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hi,

I'm a french composer, and I try to create an sp-midi file for nokia =
3510 and communicator

I use beatnik since 2 years and I know that a mini Beatnik Audio Engine =
is in some nokia phones.

I'm waiting for Scalable Polyphony MIDI Specification and Device =
Profiles  by MMa.
=20
 I try to create an sp-midi file. To do that , musician must embed at =
the top of the midifile a "mip "
code( in hexadecimal code )..This mip code allow to reduce or increase =
polyphony of a midifile
for 4-polyphony device or 8 or16- polyphony device....
This mip code is just a sys-ex message, in hexadecimal code.The hex is =
in the MMA's specification. Also in the spec. are the device ID's for =
upcoming phones.

Do you know :
How can I put the correct "'MIP" code in my sp-midi file ?

Have you in hexdecimal code thi mip code, with device ID's ?

How can I test a sp-midi file exept on a phone and beatnik editor?=20

can I test a file on a desktop nkia 3510 phone emulator?

thanks,

=20

 my website:          www.kitmusica.com (flashsound api and beatnik)

 try our beatnik mixer    www.kitmusica.com/introbeat.htm  (beatnik)

a sonified  web site     www.helentraiteur.com, by kitmusica (beatnik)

a sonified  gypsy web site    =
http://jeanluc.borla.free.fr/chico4/chico.htm (flashsound api)

------=_NextPart_000_003F_01C1E4A9.F096B8A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<P><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2><FONT =
face=3DArial=20
size=3D2>hi,</FONT></P>
<DIV><FONT face=3DArial size=3D2>
<P><FONT face=3DArial size=3D2>I'm a french composer, and I try to =
create an sp-midi=20
file for nokia 3510 and communicator</FONT></P>
<P><FONT face=3DArial size=3D2>I use beatnik since 2 years and I know =
that a mini=20
Beatnik Audio Engine is in some nokia phones.</FONT></P></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV>I'm waiting for <STRONG><EM>Scalable Polyphony MIDI Specification =
and=20
Device Profiles&nbsp; by MMa.</EM></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;I try to create an sp-midi file. To do that , musician must =
embed at=20
the top of the midifile a "mip "</FONT></DIV></DIV>
<DIV>code( in hexadecimal code )..This mip code allow to reduce or =
increase=20
polyphony of a midifile</DIV>
<DIV>for 4-polyphony device or 8 or16- polyphony device....</DIV>
<DIV>This mip code is just a sys-ex message, in hexadecimal code.The hex =
is in=20
the MMA's specification. Also in the spec. are the device ID's for =
upcoming=20
phones.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Do you know :</FONT></DIV>
<DIV>
<P><FONT face=3DArial size=3D2>How can I put the correct "'MIP" code in =
my sp-midi=20
file ?</FONT></P>
<P><FONT face=3DArial size=3D2>Have you&nbsp;in hexdecimal code thi mip =
code, with=20
device ID's ?</FONT></P>
<P><FONT face=3DArial size=3D2>How can I test a sp-midi file exept on a =
phone and=20
beatnik editor? </FONT></P>
<P><FONT face=3DArial size=3D2>can I test a file on a desktop nkia 3510 =
phone=20
emulator?</FONT></P></DIV>
<P>thanks,</P>
<P></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2>&nbsp;my=20
website:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.kitmusica.com">www.kitmusica.com</A>&nbsp;<EM>(flashso=
und api=20
and beatnik</EM>)</FONT></P>
<P><FONT face=3DArial size=3D2>&nbsp;try our beatnik =
mixer&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.kitmusica.com/introbeat.htm">www.kitmusica.com/introbe=
at.htm</A>&nbsp;=20
<EM>(beatnik)</EM></FONT></P>
<P>a sonified&nbsp;&nbsp;web site&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.helentraiteur.com">www.helentraiteur.com</A>, by =
kitmusica=20
(beatnik)</FONT></P>
<P><FONT face=3DArial size=3D2>a sonified&nbsp;&nbsp;gypsy web=20
site&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://jeanluc.borla.free.fr/chico4/chico.htm">http://jeanluc.bor=
la.free.fr/chico4/chico.htm</A>&nbsp;(flashsound=20
api)</FONT></P>
<P></FONT>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>
<OBJECT classid=3Dclsid:D27CDB6E-AE6D-11cf-96B8-444553540000=20
codeBase=3Dhttp://download.macromedia.com/pub/shockwave/cabs/flash/swflas=
h.cab#version=3D4,0,2,0=20
height=3D28 width=3D26><PARAM NAME=3D"_cx" VALUE=3D"688"><PARAM =
NAME=3D"_cy" VALUE=3D"741"><PARAM NAME=3D"FlashVars" =
VALUE=3D"688"><PARAM NAME=3D"Movie" =
VALUE=3D"http://www.kitmusica.com/swf/logomail.swf"><PARAM NAME=3D"Src" =
VALUE=3D"http://www.kitmusica.com/swf/logomail.swf"><PARAM =
NAME=3D"WMode" VALUE=3D"Window"><PARAM NAME=3D"Play" VALUE=3D"-1"><PARAM =
NAME=3D"Loop" VALUE=3D"-1"><PARAM NAME=3D"Quality" VALUE=3D"High"><PARAM =
NAME=3D"SAlign" VALUE=3D""><PARAM NAME=3D"Menu" VALUE=3D"-1"><PARAM =
NAME=3D"Base" VALUE=3D""><PARAM NAME=3D"Scale" VALUE=3D"ShowAll"><PARAM =
NAME=3D"DeviceFont" VALUE=3D"0"><PARAM NAME=3D"EmbedMovie" =
VALUE=3D"0"><PARAM NAME=3D"BGColor" VALUE=3D""><PARAM NAME=3D"SWRemote" =
VALUE=3D"">
            <embed src=3D"http://www.kitmusica.com/swf/logomail.swf" =
quality=3Dhigh=20
pluginspage=3D"http://www.macromedia.com/shockwave/download/index.cgi?P1_=
Prod_Version=3DShockwaveFlash"=20
type=3D"application/x-shockwave-flash" width=3D"26" height=3D"28">    =
</embed>  =20
</OBJECT></P></DIV></BODY></HTML>

------=_NextPart_000_003F_01C1E4A9.F096B8A0--

From: ietf-xml-use at NineByNine.org (Graham Klyne)
Date: Tue Jan  3 16:22:31 2006
Subject: Fwd: I-D ACTION:draft-swartz-rdfcore-rdfxml-mediatype-00.txt
Message-ID: <[email-masked]>

All,

The following was recently published as a work item of the W3C RDFcore 
working group.  It is our hope that when the specification documents are 
stabilized as W3C recommendations (hopefully, quite soon) we can move this 
forward promptly for RFC publication.

If there's anything here likely to be problematic, we'd appreciate knowing 
sooner rather than later.

#g
--

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : application/rdf+xml Media Type Registration
>         Author(s)       : A. Swartz
>         Filename        : draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>         Pages           :
>         Date            : 05-Apr-02
>
>This document describes a media type (application/rdf+xml) for use
>with the XML serialization of the Resource Description Framework
>(RDF).  RDF is a language designed to support the Semantic Web, by
>facilitating resource description and data exchange on the Web.  RDF
>provides common structures that can be used for interoperable data
>exchange and follows the World Wide Web Consortium (W3C) design
>principles of interoperability, evolution, and decentralization.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         [email-masked].
>In the body type:
>         "FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <[email-masked]>
>
>ENCODING mime
>FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt>

-------------------
Graham Klyne
<[email-masked]>

From: [email-masked] (Graham Klyne)
Date: Tue, 09 Apr 2002 20:14:30 +0100
Subject: Fwd: I-D ACTION:draft-swartz-rdfcore-rdfxml-mediatype-00.txt
Message-ID: <[email-masked]>

All,

The following was recently published as a work item of the W3C RDFcore 
working group.  It is our hope that when the specification documents are 
stabilized as W3C recommendations (hopefully, quite soon) we can move this 
forward promptly for RFC publication.

If there's anything here likely to be problematic, we'd appreciate knowing 
sooner rather than later.

#g
--

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : application/rdf+xml Media Type Registration
>         Author(s)       : A. Swartz
>         Filename        : draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>         Pages           :
>         Date            : 05-Apr-02
>
>This document describes a media type (application/rdf+xml) for use
>with the XML serialization of the Resource Description Framework
>(RDF).  RDF is a language designed to support the Semantic Web, by
>facilitating resource description and data exchange on the Web.  RDF
>provides common structures that can be used for interoperable data
>exchange and follows the World Wide Web Consortium (W3C) design
>principles of interoperability, evolution, and decentralization.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         [email-masked].
>In the body type:
>         "FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <[email-masked]>
>
>ENCODING mime
>FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt>

-------------------
Graham Klyne
<[email-masked]>

From: duerst at w3.org (Martin Duerst)
Date: Tue Jan  3 16:22:31 2006
Subject: please review: application/smil MIME type registration
In-Reply-To: <[email-masked]>
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <4.2.0.58.J.20020405144041.0262a008@localhost>

Hello Philipp,

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

In things like:

 >>>>
3.  Registration Information

    To: [email-masked]
    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: [email-masked]
    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:[email-masked]]
> > > Sent: 22 June 2001 19:45
> > > To: Peter Stark (ECS)
> > > Cc: [email-masked]; [email-masked]
> > > 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:[email-masked]]
> > > > > Sent: den 21 juni 2001 18:03
> > > > > To: [email-masked]
> > > > > Cc: [email-masked]
> > > > > 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
>[email-masked]
>http://www.alvestrand.no/mailman/listinfo/ietf-types

From: [email-masked] (Martin Duerst)
Date: Fri, 05 Apr 2002 14:42:45 +0900
Subject: please review: application/smil MIME type registration
In-Reply-To: <[email-masked]>
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <4.2.0.58.J.20020405144041.0262a008@localhost>

Hello Philipp,

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

In things like:

 >>>>
3.  Registration Information

    To: [email-masked]
    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: [email-masked]
    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:[email-masked]]
> > > Sent: 22 June 2001 19:45
> > > To: Peter Stark (ECS)
> > > Cc: [email-masked]; [email-masked]
> > > 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 $BqD(Brit :
> > > >
> > > > 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:[email-masked]]
> > > > > Sent: den 21 juni 2001 18:03
> > > > > To: [email-masked]
> > > > > Cc: [email-masked]
> > > > > 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
>[email-masked]
>http://www.alvestrand.no/mailman/listinfo/ietf-types

From: ph at w3.org (Philipp Hoschka)
Date: Tue Jan  3 16:22:31 2006
Subject: please review: application/smil MIME type registration
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <[email-masked]>

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:[email-masked]]
> > Sent: 22 June 2001 19:45
> > To: Peter Stark (ECS)
> > Cc: [email-masked]; [email-masked]
> > 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 ?crit :
> > >
> > > 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:[email-masked]]
> > > > Sent: den 21 juni 2001 18:03
> > > > To: [email-masked]
> > > > Cc: [email-masked]
> > > > 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
> > > >
> >

From: [email-masked] (Philipp Hoschka)
Date: Thu, 04 Apr 2002 14:49:29 +0200
Subject: please review: application/smil MIME type registration
References: <4A7000CDDBBED211994C0008C7A49825074D88C9@esealnt114>
Message-ID: <[email-masked]>

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:[email-masked]]
> > Sent: 22 June 2001 19:45
> > To: Peter Stark (ECS)
> > Cc: [email-masked]; [email-masked]
> > 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 écrit :
> > >
> > > 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:[email-masked]]
> > > > Sent: den 21 juni 2001 18:03
> > > > To: [email-masked]
> > > > Cc: [email-masked]
> > > > 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
> > > >
> >