TC Administration comments on FFMII V1.0 csprd02

[Chet Ensign <chet.ensign@oasis-open.org>]

Members of the FFM TC, 

I apparently neglected to write up these observations and send them to you during your last public review. I am sending them now so that they can be of use to you as work on your next iteration of the specification. These are non-material changes so making them will not require another round of public reviews. 

1. Several normative references are displayed as http urls but they are not linked:

[ISO-639]  ISO 639-1:2002, Part 1: Alpha-2 Codes, "Codes for the representation of names of languages", http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=22109

[Schema2]  P. V. Biron et al. XML Schema Part 2: Datatypes. World Wide Web Consortium Recommendation, May 2001. See http://www.w3.org/TR/xmlschema-2/

[SOAP]  SOAP Version 1.2 Part 1: Messaging Framework (Second Edition), Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon, Editors. World Wide Web Consortium, 27 April 2007. This version is http://www.w3.org/TR/2007/REC-soap12-part1-20070427. The latest version is available at http://www.w3.org/TR/soap12-part1/.

[WSS]  Web Services Security: SOAP Message Security 1.1. 1 February 2006. OASIS Standard Specification. http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-SOAPMessageSecurity.pdf

[WSS-UTP]   Web Services Security: Username Token Profile 1.1. 1 February 2006. OASIS Standard Specification. http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-UsernameTokenProfile.pdf


2. The wsdl and schema filenames use the underscore (_) character. We disallow that character in names except in the case where they are generated by machine. Robin can give you extensive background on the problems the character causes in systems. 

If the files are not machine generated, I would appreciate it if you would replace the underscores with hyphens (-). 


3. Please note any namespaces declared in the wsdl or schemas on the next iteration of the specification. We will add the declared namespaces to the cover page of the spec and create a namespace document to accompany the spec. 


4. There are several links in the spec that point to documents in Kavi but that use the internal link. These will not work for public readers. I believe this is the whole list: 

2.2 Non-Normative References
[FFMII-REQ] Field Force Management Integration Interface Requirements,
Version 1.0, OASIS FFM TC, September 12, 2011,
http://www.oasis-open.org/apps/org/workgroup/ffm/download.php/43512/latest

And in Appendix B

http://www.oasis-open.org/apps/org/workgroup/ffm/email/archives/201202/msg00021.html

http://www.oasis-open.org/apps/org/workgroup/ffm/email/archives/201204/msg00018.html

http://www.oasis-open.org/apps/org/workgroup/ffm/email/archives/201204/msg00021.html

http://www.oasis-open.org/apps/org/workgroup/ffm/email/archives/201204/msg00024.html

http://www.oasis-open.org/apps/org/workgroup/ffm/email/archives/201204/msg00046.html

These can be fixed by replacing the string … apps/org/workgroup/ffm/...
with .../committees/. So, for example, changing 

http://www.oasis-open.org/apps/org/workgroup/ffm/download.php/43512/latest 

to 

http://www.oasis-open.org/committees/download.php/43512/latest

will make it available publicly. 

Thanks and let me know if you have any questions on any of these. 

/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