Hi Chet,
Yes, that would work as long as the latest version of the link does
not carry over to the next major version, say XACML 4.0, which might
be entirely different, and not compatible with the XACML 3.0
version, which of course would remain posted even after 4.0 has been
released.
Best regards,
Erik
On 2014-08-04 15:57, Chet Ensign wrote:
Hi Erik,
Ok, got it. So is there any reason not to cite to the
Latest version link so that it automatically stays up to date?
In other words:
[xacml-3.0-multiple-v1.0]
XACML
v3.0 Multiple Decision Profile Version 1.0. Edited by
Erik Rissanen. Latest version: http://docs.oasis-open.org/xacml/3.0/multiple/v1.0/xacml-3.0-multiple-v1.0.html.
Citing it that way in your references section ensures that
the reader will always be taken to the most recent version of
the spec. In other words, if this is the version that is cited
in Hierarchial and Multiple was a Candidate OASIS Standard
when Hierarchial was published but has since been approved as
an OASIS Standard, someone clicking on the link will get the
OS.
To me that seems the simplest solution. And you can get
these references easily enough - just go to the end of the
cover page we put on the spec you want to cite, copy the
citation format block (that's what I did above), then cut out
the current date, stage and link and just leave the Latest
version link.
Will that work?
/chet
On Fri, Aug 1, 2014 at 5:49 PM, Chet
Ensign <>
wrote:
Hi Erik,
One way to avoid this is to use the Latest version
links when you update a profile. For example, to cite
the Export Compliance Profile, you could use this
format:
[xacml-ec-us-v1.0] XACML 3.0 Export Compliance US
(EC-US) Profile Version 1.0. Latest version: http://docs.oasis-open.org/xacml/3.0/ec-us/v1.0/xacml-3.0-ec-us-v1.0.html
That way, your references will always go to the most
recent approved version of the document.
Alternately, you can ask TC Admin to update OASIS
citations during publishing with a designated
cross-reference motion as part of your approval. To do
that, when the document is approved for CS (e.g.)
include language like this:
"I move to approve the Chair requesting that TC
Administration hold a Special Majority Vote to approve
<Committee Specification Draft title and version
number> contained in <URL to Committee
Specification Draft> as a Committee Specification,
******-> and to approve the Chair requesting that
TC Administration update the following Designated
Cross-References during publication of the Committee
Specification:
- Current reference to be updated: <text of
OASIS work product cross-reference to be updated?
Expected approval status and date: <expected
approval stage>, <expected month/year of
approval>
- <repeat references as needed> "
With that sort of explicit instruction in the
motion, I'll update the cross-references as part of
the publication. It is the only time that I'll go in
and change what the TC wrote - I stay out of TC
content in general.
Does this answer the question or are you looking at
something different?
Best,
/chet
On Tue, Jul 29, 2014 at 10:09
AM, Erik Rissanen <>
wrote:
Hi,
I noticed that some of the CS profiles have cross
references to old versions of other profiles. Does
someone know what the process is for updating them
nowadays? I remember in the past we did votes on
the topic.
Ideally, I would like to make the updates only as
they becomes published as OASIS standard since
some of the profiles refer to each other, so there
would be a chicken and egg type of problem if we
had to make the changes as part of working draft
editing.
Best regards,
Erik
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave
the OASIS TC that generates this mail. Follow
this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
/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
Check your work using the Support Request Submission
Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
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
--
/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
Check your work using the Support Request Submission
Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
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
