RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC



Hi Pete,

After consulting with my co-authors our view is that industry implemented the solution as specified in the example, so we need to revise the schema based on Pete's suggestion to

 

<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified" id="TightMediaControl">

      <xs:element name="media_control">

            <xs:complexType>

                  <xs:sequence>

                        <xs:element name="vc_primitive" type="vc_primitive" minOccurs="0" maxOccurs="unbounded"/>

                        <xs:element name="general_error" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>

                  </xs:sequence>

            </xs:complexType>

      </xs:element>

      <!-- Video control primitive.  -->

      <xs:complexType name="vc_primitive">

            <xs:sequence>

                  <xs:element name="to_encoder" type="to_encoder"/>

                  <xs:element name="stream_id" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>

            </xs:sequence>

      </xs:complexType>

      <!-- Encoder Command:

                Picture Fast Update

           -->

      <xs:complexType name="to_encoder">

            <xs:choice>

                  <xs:element name="picture_fast_update"/>

            </xs:choice>

      </xs:complexType>

</xs:schema>

 

 

This also means that we will not have the target name space so we do not need to register it with IANA as specified in section 9.2.

 

If this is correct I will submit a revised revsion.

 

Thanks

Roni Even

 

 

 

> -----Ores at ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Il1oz-0005e5-EB; Thu, 25 Oct 2007 08:28:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Il1ot-0005UB-Tr
	for ietf at ietf.org; Thu, 25 Oct 2007 08:28:16 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il1oo-00057L-A1
	for ietf at ietf.org; Thu, 25 Oct 2007 08:28:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 25 Oct 2007 14:29:35 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C0501B822 at IsrExch01.israel.polycom.com>
In-Reply-To: <001501c809b6$a1f9a710$5d00a8c0 at Codalogic>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for
	Media Control) to Informational RFC
Thread-Index: AcgJttiXYh+FocjRR8y1vcE7nBfRgAK3CjzQ
From: "Even, Roni" <roni.even at polycom.co.il>
To: "Pete Cordell" <pete at codalogic.com>,
	<ietf at ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 914259abaa14125df0511c5458bea061
Cc: Cullen Jennings <fluffy at cisco.com>, oritl at microsoft.com,
	pierre at radvision.com, jo at acm.org, jf.mule at cablelabs.com,
	Colin Perkins <csp at csperkins.org>
Subject: RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for
	Media Control) to Informational RFC
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="==============95827320=="
Errors-To: ietf-bounces at ietf.org

This is a multi-part message in MIME format.

Hi Pete,

After consulting with my co-authors our view is that industry implemented the solution as specified in the example, so we need to revise the schema based on Pete's suggestion to

 

<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" id="TightMediaControl">

      <xs:element name="media_control">

            <xs:complexType>

                  <xs:sequence>

                        <xs:element name="vc_primitive" type="vc_primitive" minOccurs="0" maxOccurs="unbounded"/>

                        <xs:element name="general_error" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>

                  </xs:sequence>

            </xs:complexType>

      </xs:element>

      <!-- Video control primitive.  -->

      <xs:complexType name="vc_primitive">

            <xs:sequence>

                  <xs:element name="to_encoder" type="to_encoder"/>

                  <xs:element name="stream_id" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>

            </xs:sequence>

      </xs:complexType>

      <!-- Encoder Command:

                Picture Fast Update

           -->

      <xs:complexType name="to_encoder">

            <xs:choice>

                  <xs:element name="picture_fast_update"/>

            </xs:choice>

      </xs:complexType>

</xs:schema>

 

 

This also means that we will not have the target name space so we do not need to register it with IANA as specified in section 9.2.

      <!-- Video control primitive.  -->

      <xs:complexType name="vc_primitive">

            <xs:sequence>

                  <xs:element name="to_encoder" type="to_encoder"/>

                  <xs:element name="stream_id" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>

            </xs:sequence>

      </xs:complexType>

      <!-- Encoder Command:

                Picture Fast Update

           -->

      <xs:complexType name="to_encoder">

            <xs:choice>

                  <xs:element name="picture_fast_update"/>

            </xs:choice>

      </xs:complexType>

</xs:schema>

 

 

This also means that we will not have the target name space so we do not need to register it with IANA as specified in section 9.2.

 

If this is correct I will submit a revised revsion.

 

Thanks

Roni Even

 

 

 

> -----Original Message-----

> From: Pete Cordell [mailto:pete at codalogic.com]

> Sent: Monday, October 08, 2007 4:22 PM

> To: ietf at ietf.org

> Cc: oritl at microsoft.com; Even, Roni; pierre at radvision.com

> Subject: Re: Last Call: draft-levin-mmusic-xml-media-control (XML Schema

> for Media Control) to Informational RFC

>

> I quickly looked at this and noticed that the XML instance examples don't

> match the schema because the instance does not make reference to the

> namespace.  i.e., to match the schema, the example should be:

>

>    <media_control xmlns="urn:ietf:params:xml:ns:media_control">

>

>       <vc_primitive>

>        <to_encoder>

>     &nb style='font-size: 10.0pt'> 

If this is correct I will submit a revised revsion.

 

Thanks

Roni Even

 

 

 

> -----Original Message-----

> From: Pete Cordell [mailto:pete at codalogic.com]

> Sent: Monday, October 08, 2007 4:22 PM

> To: ietf at ietf.org

> Cc: oritl at microsoft.com; Even, Roni; pierre at radvision.com

> Subject: Re: Last Call: draft-levin-mmusic-xml-media-control (XML Schema

> for Media Control) to Informational RFC

>

> I quickly looked at this and noticed that the XML instance examples don't

> match the schema because the instance does not make reference to the

> namespace.  i.e., to match the schema, the example should be:

>

>    <media_control xmlns="urn:ietf:params:xml:ns:media_control">

>

>       <vc_primitive>

>        <to_encoder>

>          <picture_fast_update/>

>        </to_encoder>

>      </vc_primitive>

>

>    </media_control>

>

> My expectation is that the instance is actually more authorative in terms

> of

> what the authors are looking for. If that is the case, the schema should

> be

> modified along the lines of:

>

>    <xsd:schema id="TightMediaControl"

>     xmlns:xsd="http://www.w3.org/2001/XMLSchema">

>     ...

>

> i.e. remove the targetNamespace declarations.

>

> You may have your reasons not to, but if not, you may want to consider

> using

> schema's documentation features instead of the XML comments; e.g.:

>

> <xsd:complexType name="vc_primitive">

>     <xsd:annotation><xsd:documentation>

>     sp;    <picture_fast_update/>

>        </to_encoder>

>      </vc_primitive>

>

>    </media_control>

>

> My expectation is that the instance is actually more authorative in terms

> of

> what the authors are looking for. If that is the case, the schema should

> be

> modified along the lines of:

>

>    <xsd:schema id="TightMediaControl"

>     xmlns:xsd="http://www.w3.org/2001/XMLSchema">

>     ...

>

> i.e. remove the targetNamespace declarations.

>

> You may have your reasons not to, but if not, you may want to consider

> using

> schema's documentation features instead of the XML comments; e.g.:

>

> <xsd:complexType name="vc_primitive">

>     <xsd:annotation><xsd:documentation>

>         Video control primitive.

>     </xsd:documentation></xsd:annotation>

>

>     <xsd:sequence>

>      ...

>

> HTH,

>

> Pete.

> --

> =============================================

> Pete Cordell

> Codalogic

> for XML Schema to C++ data binding visit

>  http://www.codalogic.com/lmx/

> =============================================

> ----- Original Message -----

> From: "The IESG" <iesg-secretary at ietf.org>

> To: "IETF-Announce" <ietf-announce at ietf.org>

> Sent: Monday, October 08, 2007 2:29 PM

> Subject: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for

> Media Control) to Informational RFC

>

>

> > The IESG has received    Video control primitive.

>     </xsd:documentation></xsd:annotation>

>

>     <xsd:sequence>

>      ...

>

> HTH,

>

> Pete.

> --

> =============================================

> Pete Cordell

> Codalogic

> for XML Schema to C++ data binding visit

>  http://www.codalogic.com/lmx/

> =============================================

> ----- Original Message -----

> From: "The IESG" <iesg-secretary at ietf.org>

> To: "IETF-Announce" <ietf-announce at ietf.org>

> Sent: Monday, October 08, 2007 2:29 PM

> Subject: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for

> Media Control) to Informational RFC

>

>

> > The IESG has received a request from an individual submitter to consider

> > the following document:

> >

> > - 'XML Schema for Media Control '

> >   <draft-levin-mmusic-xml-media-control-11.txt> as an Informational RFC

> >

> > The IESG plans to make a decision in the next few weeks, and solicits

> > final comments on this action.  Please send substantive comments to the

> > ietf at ietf.org mailing lists by 2007-11-05. Exceptionally,

> > comments may be sent to iesg at ietf.org instead. In either case, please

> > retain the beginning of the Subject line to allow automated sorting.

> >

> > The file can be obtained via

> > http://www.ietf.org/internet-drafts/draft-levin-mmusic-xml-media-

> control-11.txt

> >

> >

> > IESG discussion can be tracked via

> >

> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=93

> 91&rfc_flag=0

> >

> >

> > _______________________________________________

> > the following document:

> >

> > - 'XML Schema for Media Control '

> >   <draft-levin-mmusic-xml-media-control-11.txt> as an Informational RFC

> >

> > The IESG plans to make a decision in the next few weeks, and solicits

> > final comments on this action.  Please send substantive comments to the

> > ietf at ietf.org mailing lists by 2007-11-05. Exceptionally,

> > comments may be sent to iesg at ietf.org instead. In either case, please

> > retain the beginning of the Subject line to allow automated sorting.

> >

> > The file can be obtained via

> > http://www.ietf.org/internet-drafts/draft-levin-mmusic-xml-media-

> control-11.txt

> >

> >

> > IESG discussion can be tracked via

> >

> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=93

> 91&rfc_flag=0

> >

> >

> > _______________________________________________

> > IETF-Announce mailing list

> > IETF-Announce at ietf.org

> > https://www1.ietf.org/mailman/listinfo/ietf-announce

> >

>

 

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.