Chet, don't you also need a link for the source and for one output
format to be designated authoritative?
Kris
On 8/3/2012 6:21 PM, Chet Ensign wrote:
The "This version" directs someone to the specific
version of the document. (And I just realized that I should have
specified it for the public review version.) So that one is:
This
version:
Should
you send another updated version around later, it would be
-cnprd02 and of course when you vote the final committee note
it become -cn01, etc.
The
"Latest version" link is a symlink that we put in the
directory above the stage directory and it always points to
whatever is the most recent edition of the document. So, if
you point someone to the 'dita12xliff-v1.0.html' file, it will
take them to the -cnprd01 until that is approved and then it
will take them to the -cn01 document. It is a way to give
readers one link that will keep up to date with the document's
evolution. So it will always stay:
Latest
version:
JoAnn, the reason for publishing the links is so that
should someone come across the document 'in the wild' as Robin
likes to say, they will be able to find the original versions
of the files.
/chet
On Fri, Aug 3, 2012 at 6:13 PM, Kristen
James Eberlein <kris@eberleinconsulting.com>
wrote:
JoAnn, in this case,
"this version" and the "latest version" will be the same.
If, however, the DITA Adoption TC produces another version
of this committee note --02 -- the front matter of this 01
version will be updated so that the "latest version"
points to the 02 version.
Chet, please correct me if I am wrong. (It's been almost
two years since I went through all this for the DITA 1.2
specification ...)
Kris
On 8/3/2012 4:00 PM, JoAnn Hackos wrote:
Chet,
We
could not put the URLs into the copy because
we had no idea what that was supposed to be. I
still don’t understand why you want this
information. What is the difference between
“this version” and “latest version” supposed
to mean?
JoAnn
From:
Chet Ensign [mailto:chet.ensign@oasis-open.org]
Sent: Friday, August 03, 2012 1:57 PM
To: Kristen James Eberlein
Cc: Jordan Jones (jorjones); Frank
Miller; JoAnn Hackos
Subject: Re: Committee Note Draft for
the DITA Adoption TC
Kristen, no need for
apologies! This is the job I'm paid to do.
Here are answers
to your questions:
On Fri, Jul 27, 2012 at
12:26 PM, Kristen James Eberlein <kris@eberleinconsulting.com>
wrote:
- Both the Working
Draft # and the Committee Note Draft
Number seem to be required. This TC has
not been using the convention of
incrementing versions for a working
draft. Should Jordon just list both as
01?
Yes, that's fine. I am
redoing the tickets to clarify some of
these things. For now, 01 is fine.
- To approve a
committee note draft for public
review, we need a full majority vote
(according to the TC process, section
3.1). A full majority vote is defined
as "a TC vote in which more than 50%
(more than half) of the Voting Members
vote "yes". Obviously this requires
that we have quorum at a meeting, and
then more than a majority of the
attending voting members must vote in
the affirmative. Correct?
Not quite. The
definition says, "a
TC vote in which more than 50% (more
than half) of the Voting Members vote
"yes", regardless of the number of
Voting Members present in the meeting."
I see that DITA Adoption has 6 voting
members so you need 4 votes minimum to
pass. That is, if you have 4 voting
members present at the meeting, you meet
quorum. But then all 4 must vote to pass
the motion. 3 won't be enough.
As far as the filename
itself is concerned, we will publish it
like this:
The 'dita12xliff' is
fine but it needs to have a version number
and stage abbreviation as well.
Also, I asked several
times about putting the document URLs into
the draft and I still do not see those
added. The Notices page is full and I
imagine you don't want to clutter the
front page with them. So I would be fine
with them being at the bottom of the TOC
page, done as
This version:
I do apologize for adding work to your
plate. However, given the fact that the
DITA Adoption TC really struggled with
the new OASIS processes, I would really
appreciate your help here.
Again, no need to
apologize. Let me know if you have any
more questions on this.
Best,
Kris
-------- Original Message --------
If it's not in the minutes, we will
need to modify the minutes at our next
meeting. The approval must be minuted
or it cannot move forward. In fact,
the TC resolution to approve a
specification or committee note must
reference the precise package on Kavi
that is being approved.
Here's a link to the OASIS process
info about committee notes:
https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes
So, let's plan to move and approve
again at the next meeting. Here's
sample text for the resolution and
minutes.
Motion
that the [title, version number
and revision number] and all
associated artifacts contained in
[ZIP file link] be approved as a
Committee Note Draft and submitted
to OASIS for a publication.
Submitted by X, seconded by Y,
and approved by a majority vote
Jordon, I'll ping Chet about the other
items and include you all.
Kris
On 7/27/2012
11:38 AM, Jordan Jones (jorjones)
wrote:
Hi Frank, I've gotten back to the task of setting this up, but have a couple of questions.
The form is asking for a Working Draft Number "WD##" -- I don't see this on the document. Do I simply provide a date?
The form is asking for a Committee Note Draft Number: "CND ##". I don't see that either.
The form is asking for a link to the approval. I don't see an approval in the minutes back through June. Do you know when it was approved? Maybe I'm just missing it in the minutes.
-- Jordan
On Jul 18, 2012, at 5:41 PM, Frank Miller wrote:
Hi Jordan,
Had almost forgotten about this but just uploaded. Just lettin' you know ...
Had to post to a new location as it's the first time we'd ever bundled it.
Thanks,
Frank
-----Original Message-----
From: Jordan Jones (jorjones) [mailto:jorjones@cisco.com]
Sent: Monday, July 16, 2012 11:21 AM
To: Frank Miller
Subject: Re: location for package
I would think it would be the same location, as we have not changed the content.
But if you feel it needs to be in another location, is this something you can set up?
-- Jordan
On Jul 16, 2012, at 12:38 PM, Frank Miller wrote:
Hi Jordan,
I've got the package ready to upload but can't find the location in our TC area.
Seems like this is a new bundle so will need a newly created location? Maybe I'm misunderstanding.
Thanks,
Frank
--
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
--
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC
Administration
OASIS: Advancing open standards for the
information society
http://www.oasis-open.org
Primary: +1
973-996-2298
Mobile: +1
201-341-1393
TC Administration information and support is
available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
--
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
--
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
|