[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: CD 01 PR package
|
Copying response to the TC list. Regards, Mary From: Mary McRae
[mailto:mary.mcrae@oasis-open.org] Hi Marc et al, Each time the TC Process
is updated it is announced on the Chairs list. The Specification Checklist (http://docs.oasis-open.org/templates/QAChecklistV2.html)
is intended to serve as a quick guide to requirements and to be used as a
self-check prior to submission. #1 and #2 have been in effect
since at least June of 2004 (when I joined OASIS Staff). #3 - the “authoritative”
designation went into effect on March 1
(http://lists.oasis-open.org/archives/chairs/200803/msg00000.html). #4 below has been in effect for
quite some time (well before the formation of WSFED) and is stated in the
Naming Guidelines policy (03-31-2007)
http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNaming.html.
#5 has been in practice since
June 07 (use of /ns in path); this is not a required change – the namespace is
fine but the documents/schemas can’t live “under” it. The namespace will
resolve to the actual namespace document (which will also live elsewhere, in
the same dir as the specs) #6 the date in the running
footer must correspond to the approval date (see #1 and #2 above); a templating
error with regard to the copyright slug was made and fixed back in April of
2007 (before WS-FED’s first meeting) #7 TC Process requires a
separate section (not subsection) for Conformance; best practice is to make
this the last numbered section. This is not a required change. #8 is required because of #4
above I’m always open to any
and all suggestions about how to better “get the word out” regarding template
updates, TC Process updates, etc. Maybe a meeting with the editors as soon as
they start drafting? Quarterly editor webinars? I’d much prefer that the
specifications come in with no work required so I could turn them around
quickly – ideas? Mary From: Marc Goodner
[mailto:mgoodner@microsoft.com] Mary, the TC decided that namespace a long time ago. You are
asking for a breaking change to our approved specification based on what
appears to be a policy that has not been announced. This is certainly the first
I have heard of it. These sort of changes need to be introduced much earlier to
TCs than at approval time. Many of us work on implementations for interop
events prior to the approval of the specs using the namespace. Changing it now
is extremely diruptive when it wouldn't have been if introduced sooner. In
fact, its a violation of our own namespace policy. Introducing a new namespace
policy for the organization seems like something that should be subject to
more discussion than just instituting it retrocctively. When
did the rest of these new rules go into effect? I never saw an announcement
about any of these. If
I sound frustrated I am. It seems any time we put a package up that there are
new rules in place that weren't before. Why do we only hear about new
publication rules after we approve specifications for publication? From: Mary McRae [marypmcrae@gmail.com] On Behalf
Of Mary McRae [mary.mcrae@oasis-open.org] Hi Marc, I’m attaching a
change-tracked/commented version of the spec – experiment: is this more helpful
than just a list of comments? Changes needed: 1.
Need to identify the specific committee
draft version (Committee Draft 01, 02, etc.) 2.
Need the exact approval date (25 June 2008,
etc.) 3.
TC needs to declare one of the three formats
as authoritative; needs to be noted following the specific URI in parens
“(Authoritative)” 4.
Documents are not allowed to be “hidden”
under namespaces acting as directories. Documents/schemas must be located under
the prescribed path
(docs.oasis-open.org/wsfed/federation/v1.2/{cd01}/[filename] – where “cd01” is
optional but preferred 5.
We are migrating to a system where
namespaces are explicitly identified by the use of ‘ns’ in the URI path (which
avoids the confusion identified in #4 above). The ns should either immediately
precede or follow the tc shortname (i.e. /ns/wsfed/ or /wsfed/ns/) 6.
Date needs to be added to running footer;
also remove “OASIS trademark, IPR and other policies apply.” 7.
Conformance section needs to be the last
numbered section in the spec immediately preceding Appendix A. 8.
Corresponding changes to the namespace
document to reflect the proper file URIs Regards, Mary From: Marc Goodner
[mailto:mgoodner@microsoft.com] Mary, please let me know if everything looks in order. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]