Re: [clue] Alexey Melnikov's Discuss on draft-ietf-clue-data-model-schema-15: (with DISCUSS and COMMENT)

[Spencer Dawkins at IETF <[e-mail]>]

Not my Discuss, but ...

On Fri, Jun 3, 2016 at 9:02 AM, Alexey Melnikov <[e-mail]>
wrote:

> Hi Simon,
>
> On Fri, Jun 3, 2016, at 02:11 PM, Simon Pietro Romano wrote:
> > Hello Alexey,
> >
> > please find in-line our answers to your comments (preceded by
> > [spromano]).
> >
> > > ----------------------------------------------------------------------
> > > DISCUSS:
> > > ----------------------------------------------------------------------
> > >
> > > This is generally a well written document, but I have a couple of very
> > > small points that need to be fixed:
> > >
> > > Abstract: I have no CLUE what you are talking about. Abstracts should
> be
> > > self contained, i.e. being understandable on its own. The Introduction
> > > section has more relevant text which you might want to copy here.
> >
> > [spromano] Got it. What about the following amended abstract?
> >
> >
> *****************************************************************************
> > This document provides an XML schema file
> > for the definition of CLUE data model types. the term 'CLUE' stands for
> > "ControLling mUltiple streams for tElepresence" and is the name of
> > the IETF working group in which this document, as well as other
> > companion documents, has been developed. The document defines a coherent
> > structure for information associated with the description of a
> > telepresence session.
> >
> *****************************************************************************
>
> This is much better. I am not convinced that the acronym CLUE is going
> to have much relevance after the WG is closed, but this is not a reason
> to block publication of this document.


Is there a name for the output of the CLUE working group? I did participate
in CLUE before joining the IESG, but I don't remember one.

I know we usually pull RFC references to IETF working groups (which
conclude, while RFCs remain unchanged until the earth is swallowed by the
sun), but it would be nice to have a way to refer to what the working group
did before it concluded.

If not, maybe "... and is the name of a telepresence technology developed
in the IETF"?

Spencer, just trying to be helpful ...


> > > In 11.13: you need to have a Normative Reference to the language tag
> > > document here (RFC 5646) when you describe the "lang" attribute.
> >
> > [spromano] Done.
> >
> > > ----------------------------------------------------------------------
> > > COMMENT:
> > > ----------------------------------------------------------------------
> > >
> > > In 11.24.1: A reference to xCard would be good to have here.
> >
> > [spromano] Done (the mentioned text is now in Section 16.1, btw).
> >
> > > In 16.30:
> > >
> > > MIME type name typo on the Subject line.
> >
> > [spromano] Typo corrected.
>
> Thank you for fixing these.
>
> > > "Application that use this media type: none ?"
> > >
> > > I don't think this is correct. Please provide some examples of
> > > applications that would be using this media type. If no applications
> are
> > > going to be using this media type, there is no need to register it ;-).
> >
> > [spromano] Corrected. We put "CLUE-capable telepresence systems” there.
> > Does this work for you?
>
> Yes.
>
> Best Regards,
> Alexey
>
>