Hi,
Johannes’ proposal seems to be a feasible way to specify conformance. I agree.
Tables that collect mandatory and optional manager (1 table) + implementation (1 table) functionality would make life easier for readers/potential
implementers. But that would require quite thorough analysis and it would probably delay us.
Best regards,
Juha
From: ffm@lists.oasis-open.org [mailto:ffm@lists.oasis-open.org]
On Behalf Of Siles, Jose (NSN - ES/Madrid)
Sent: 18. toukokuuta 2012 16:19
To: ext Johannes Lehtinen; Nguyenphu, Thinh (NSN - US/Irving)
Cc: FFM TC List
Subject: RE: [ffm] I encountered a problem with the FFMII working draft that will have to be fixed before we can put it out for public review
Hello,
I agree with Johannes’ proposal.
Regards
Jose
From: ffm@lists.oasis-open.org [mailto:ffm@lists.oasis-open.org]
On Behalf Of ext Johannes Lehtinen
Sent: Friday, May 18, 2012 7:23 AM
To: Nguyenphu, Thinh (NSN - US/Irving)
Cc: FFM TC List
Subject: Re: [ffm] I encountered a problem with the FFMII working draft that will have to be fixed before we can put it out for public review
Hi, Thinh and others!
As we have mostly already indicated the conformance rules in the spec by using the keywords "MUST", "MUST NOT", and so on, could we simply refer to these?
Pretty much similarly as it has been done here:
Perhaps something like this:
An implementation of Manager or Implementation conforms to this specification if
1) it meets the requirements indicated throughout this specification by keywords specified in Section 3.1.1, and
2) it complies with semantics and structure of operations and data types specified in Chapters 5, 6, 7 and 8, and
3) it is compatible with the web service binding specified in Chapter 9.
2012/5/17 Nguyenphu, Thinh (NSN - US/Irving) <thinh.nguyenphu@nsn.com>
Hi Chet,
Oops and thanks for bring the issue up before going in PR. I completely forgot about Chapter 10.
FFM TC members,
I will preparing an input paper for Chapter 10. Also, I will fix all of editorial changes too.
Thinh
-----Original Message-----
From: ffm@lists.oasis-open.org [mailto:ffm@lists.oasis-open.org] On Behalf Of ext Chet Ensign
Sent: Thursday, May 17, 2012 11:39 AM
To: ffm@lists.oasis-open.org
Subject: [ffm] I encountered a problem with the FFMII working draft that will have to be fixed before we can put it out for public review
Hi Thinh & FFM TC members,
I started work on the Field Force Management Integration Interface
Committee Specification Draft and Public Review requests
(http://tools.oasis-open.org/issues/browse/TCADMIN-927,
http://tools.oasis-open.org/issues/browse/TCADMIN-928 and
http://tools.oasis-open.org/issues/browse/TCADMIN-929). Unfortunately
I encountered a problem that must be fixed before we can continue
processing the documents. Since I have to return it to you, I went
through the files to see if there were any other fixes or improvements
that you can make. I found a few suggestions that I include below.
The required fix is to add the Conformance Section (section 10 in the
document). The TC Process in section 2.18 Work Product Quality
(http://www.oasis-open.org/policies-guidelines/tc-process#specQuality)
requires that a specification "approved by the TC at the Committee
Specification Public Review Draft... level must include a separate
section, listing a set of numbered conformance clauses, to which any
implementation of the specification must adhere..." So I cannot
produce the CSPRD version and release it for public review until the
clauses are there.
If it is helpful, you can find guidance on writing conformance clauses
in the TAB's white paper "Guidelines to Writing Conformance Clauses"
at
http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html.
You can also look at other CSPRDs in the OASIS Library such as
searchRetrieve (http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csprd01/part1-apd/searchRetrieve-v1.0-csprd01-part1-apd.html#_Toc313350833),
EMIX v1.0 (http://docs.oasis-open.org/emix/emix/v1.0/csprd01/emix-v1.0-csprd01.html#_Toc277718310),
WS-Calendar (http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd02/ws-calendar-spec-v1.0-csprd02.html#_Toc288305827)
or WSS Username Token Profile Version 1.1.1
(http://docs.oasis-open.org/wss-m/wss/v1.1.1/csprd01/wss-UsernameTokenProfile-v1.1.1-csprd01.html#_Toc300762945)
- or any other CSPRD in docs.oasis-open.org for examples.
Next steps:
Please follow these steps so that we can get your request back on track.
1. Prepare a new working draft (-wd02) with the conformance clauses
and any other updates you wish to make. It looks like you have change
tracking turned on in the document. Please accept all the changes and
turn tracking off before handing off to us. I prefer to touch the
content produced by TCs as little as possible and accepting changes on
my end makes me squeamish.
2. ZIP the updated -wd02 specification as well as the wsdls, xsds and
any other components of the spec, load them to Kavi, and approve them
for CSD and public review as you did before, including the Kavi URL in
the motion.
3. Send me an email with the link to the approval ballot or TC minutes
document.
I will then update the TCADMIN tickets with the links, use the link in
your motion to download the new working draft and continue processing.
I will leave your tickets open and in their place in the queue so that
we can pick up where we left off as soon as we have the updated
content from you.
Also, let me just offer my compliments on the work you all have done
so far. In going through the specification, I was struck by how much
material you have produced on an aggressive timetable. Nicely done.
Other Items:
If you wish, here are some other minor items I noticed. Please take
these as observations that you may handle as you like.
- The Normative reference to the FFM-WSDL in the references section
We put a section called Additional Artifacts on the cover pages of the
CSD when we are preparing it and we will list the WSDLs and XSDs
there. If you do want to include the reference in the body of the
spec, please put a closing "/" after wsdl
(http://docs.oasis-open.org/ffm/FFMII-SPEC/v1.0/csd01/wsdl/ ).
- At line 126, figure 3, it looks like some of the text in your
graphic is cut off. The other graphics looked very good.
- Please reapply the Heading 1 style to the header for section 5 (line
179) , section 6 (line 812), section 7 (line 991), section 8 (line
1062), and section 9 (line 1826). They show the proper style applied
but for some reason it doesn't add the page break and the line above.
If you just reapply the style to each, that will fix the problem.
- You can remove the empty Appendix B unless you plan to put something
there later
Apologies for the delay but it is a requirement. I will put the work
back on track as soon as I have the updated WD from you.
Please let me know if you have any questions about this.
Best,
/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
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
---------------------------------------------------------------------
To unsubscribe, e-mail: ffm-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ffm-help@lists.oasis-open.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ffm-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ffm-help@lists.oasis-open.org
--
Johannes Lehtinen
gsm +358 40 734 7049
Rossum Oy
|