Link targets for approvals was: Re: [odata] RE: Detail ... Minutes(Meeting#4) was: Re: Groups - OData ABNF ...

[Stefan Drees <stefan@drees.name>]

Hi Ralf,

On 24.08.12 08:47, Ralf Handl wrote:
> ... Good point!
>
> I suggest using the link
>
> 	https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-current.abnf?rev=10
>
> in the minutes. It does not contain the op=dl query option, so it
> doesn't trigger a download and instead allows in-browser viewing of the
> file and navigating to the most recent version.

For normal discussions via mail or copied into the chat, I also think 
that this is the way to go, Ralf.

But, in **this** use case "approval of a specific document revision" I 
tend to disagree.

Someone asking: "What did the tc at date so and so approve?", should be 
offered a single object as response.

If in the near future we ask the tc admins to perform process 
augmentation step N+1 on a document in step N and approved as ripe for 
step N+1 in the minutes of Meeting #X a no thrill download link is 
required and indeed very helpful for the OASIS staff and ourselves.
The latter, since we do not have to answer subsequent "nail down" 
question mails.

So let's keep the download forcing option inside the url for such notes. 
Is that agreeable? That would be nice.

All the best,
Stefan.

> ...

Historic details for context:

> > -----Original Message-----
> > From: Stefan Drees [mailto:stefan@drees.name]
> > Sent: Friday, 24. August 2012 08:03
> > To: Handl, Ralf
> > Cc: odata@lists.oasis-open.org; Ram Jeyaraman; Stefan Drees
> > Subject: Detail from next revision Minutes(Meeting#4) was: ...
> > ...  to defend the approval of the svn stored text format of the normative
> > ABNF Construction Rules we have to fix at least the revision.
> >
> > The link provided by the Kavi system is following the moving HEAD, thus
> > not helpful in that regard ;-) At the time of the meeting it pointed to
> > *the revision we approved as baseline** that is helpful.
> >
> > So I checked the commit mails and found out, that for this file (not the
> > testcases etc.) the relevant revision as of the time of the motion was
> > number ten.
> >
> > My next revision of the minutes (to be uploaded well before the next
> > meeting) will thus at least differ as follows:
> >
> > <snip/>
> >
> > $> diff -cr odata-meeting-4_on-20120823_rev0.md
> > odata-meeting-4_on-20120823_minutes.md
> > *** odata-meeting-4_on-20120823_rev0.md	2012-08-24 07:49:10.000000000 +0200
> > --- odata-meeting-4_on-20120823_minutes.md	2012-08-24 07:52:08.000000000
> > +0200
> > ***************
> > *** 194,200 ****
> >     ####4.3.7 OData ABNF Construction Rules Version 1.0 Working Draft 01####
> >
> >     Ralf:
> > ! >I **move** to close the action item AI#0012 and approve the
> > [delivered revision of OData ABNF Construction Rules Version 1.0 Working
> > Draft
> > 01](https://www.oasis-open.org/committees/download.php/46748/odata-abnf-current.abnf)
> > specification (as of today) as baseline document. (**Martin seconds**).
> >
> >     Discussion of motion:
> >
> > --- 194,200 ----
> >     ####4.3.7 OData ABNF Construction Rules Version 1.0 Working Draft 01####
> >
> >     Ralf:
> > ! >I **move** to close the action item AI#0012 and approve the
> > [delivered revision of OData ABNF Construction Rules Version 1.0 Working
> > Draft
> > 01](https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-current.abnf?op=dl&rev=10&isdir=0)
> > specification (as of today, i.e. svn revision 10) as baseline document.
> > (**Martin seconds**).
> >
> >     Discussion of motion:
> >
> > <snip/>
> > ...
> >
> > Historic details, that for the base of the revision selection:
> >
> > On 22.08.12 23:33, Ralf Handl wrote:
> > > /Submitter's message/
> > > Moved to subversion
> > > -- Dr. Ralf Handl
> > > *Document Name*: OData ABNF Construction Rules Version 1.0 Working Draft
> > > 01 in text format
> > > <https://www.oasis-open.org/apps/org/workgroup/odata/document.php?document_id=46748>
> > > ------------------------------------------------------------------------
> > > ...

Attachment: smime.p7s
Description: S/MIME Kryptografische Unterschrift