Re: [Simple] Liaison Statement from the Open Mobile Alliance

["Thomson, Martin" <Martin.Thomson at andrew.com>]

Having dealt with a similar problem in an OMA group just recently, their approach requires a published location.

I support Jari's approach.  In general, managing schema documents is the responsibility of an implementation.  It's not really all that hard.

--Martin

> -----Original Message-----
> From: simple-bounces at ietf.org [mailto:simple-bounces at ietf.org] On
> Behalf Of Rauschenbach, Uwe (NSN - DE/Munich)
> Sent: Friday, 16 October 2009 9:43 PM
> To: ext Jari Urpalainen; ext Ben Campbell
> Cc: Louise.Clarke at forapolis.com; Simple WG; Dean Willis
> Subject: Re: [Simple] Liaison Statement from the Open Mobile Alliance
> 
> Hi all,
> 
> SchemaLocation refers to where documents are stored.
> 
> Therefore it makes sense to add it to the schema document instances in
> the IANA repository, but it is not required to add it to the RFC.
> 
> Kind regards,
> Uwe
> 
> 
> 
> 
> > -----Original Message-----
> > From: simple-bounces at ietf.org
> > [mailto:simple-bounces at ietf.org] On Behalf Of ext Jari Urpalainen
> > Sent: Friday, October 16, 2009 11:56 AM
> > To: ext Ben Campbell
> > Cc: Louise.Clarke at forapolis.com; Simple WG; Dean Willis
> > Subject: Re: [Simple] Liaison Statement from the Open Mobile Alliance
> >
> > On Thu, 2009-10-15 at 22:39 +0200, ext Ben Campbell wrote:
> > > On Oct 9, 2009, at 3:00 AM, Jari Urpalainen wrote:
> > >
> > > > On Fri, 2009-10-02 at 20:12 +0200, ext Ben Campbell wrote:
> > > >> (as SIMPLE co-chair)
> > > >>
> > > >> OMA sent a liaison statement to the SIMPLE working group. The
> > > >> statement's overview reads as follows:
> > > >
> > >
> > > [...]
> > >
> > > > I looked at the statement, and except the copy-paste bugs
> > of IANA
> > > > files
> > > > from rfc4826, there's a proposal to add a
> > "schemaLocation" attribute
> > > > to
> > > > rls-services schema. This attribute value provides a hint from
> the
> > > > author to a processor regarding the location of a schema
> > document.
> > > > It is
> > > > an optional value which may help the validation task. Typically
> > > > however,
> > > > validators have some means to combine multiple schemas (e.g.
> > > > <http://validate.openlaboratory.net/> does also some magic with
> > > > multiple
> > > > schemas), and as such it has also security implications
> > (if tools e.g.
> > > > try to fetch some external schemas). So imo, in any sane
> practical
> > > > service, you'll disable these hints. So they _can_ exist
> > in specs, but
> > > > they don't help practical work where you must most likely
> > anyhow tweak
> > > > with these uris. (and fyi, my preference is to use the
> > registered
> > > > urn's
> > > > which don't much help practical work either)
> > > >
> > >
> > > Am I correct in assuming the schemaLocation attribute is
> > also not in
> > > the version in the RFC? (I guess that would be a tricky
> > thing to put
> > > in an RFC due to document lifetime issues.)
> > >
> > > Thanks!
> > >
> > > Ben.
> > Right, it is not there, i.e. the rfc is ok.
> >
> > br, Jari
> >
> >
> > _______________________________________________
> > Simple mailing list
> > Simple at ietf.org
> > https://www.ietf.org/mailman/listinfo/simple
> >
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www.ietf.org/mailman/listinfo/simple