Comments on the draft spec ver 0.9

["Elron, Rami" <rami_elron@bmc.com>]

I am resending the comments since the previously attached document refers
only to a subset of my comments.

 <<comments on the SPML 0.9 version spec.doc>> 

	The changed text appears in Bold & Underline

	1.	In the glossary - 5.1.1.13 (�Provisioning�): ��restoration
of a defined set of accounts��
	2.	Section 5.3 should be revised since all is included in one
file. In this respect, the XML namespace is urn:oasis:names:tc:spml:1.0
	3.	Section 6.1, line 255: ��as its formal (?) definition��
	4.	Section 7.1, line 374: ��name=(multi)value pairs.�
	5.	Section 7.1, line 374: �To complement this��
	6.	Section 7.2.1, line 400: ��issues SPML requests is said��
	7.	Section 7.2.1, line 403: �Example RAs��
	8.	Section 7.2.2, line 413: �Example PSPs��
	9.	Section 7.2.3, line 419: ��source like an NT domain�� (btw -
shouldn�t all such names be trademarked appropriately?)
	10.	Section 7.2.3, line 426: ��functioning as a PSP��. The
fragment �(or PSP)� should be revised or removed.
	11.	Section 7.2.4, line 431: ��represents a unique��. Besides, I
think that a clearer explanation should follow, before the example.
	12.	Section 7.2.4, line 453: �The PSO-ID relationship with��
	13.	Section 7.2.4, line 453: ��represents one of many possible��
	14.	Section 7.3.1, line 496 (example): �<spml:identifier
identifiertype=�� this repeats several times throughout the document.
	15.	Section 7.3.2, line 506 (example): �<spml:modification
name=�� (opening and closing)
	16.	Section 7.3.3, line 518 (example): �<spml:identifier
identifiertype=��
	17.	Section 7.3.4, line 537 (example): �<spml:searchBase
identifiertype=��
	18.	Section 7.3.4, line 537 (example): �<spml:identifier��
	19.	Section 7.3.4, line 537 (example): �<spml:attributes ��
(opening and closing)
	20.	Section 7.3.4, line 550 (example): �<spml:identifier
identifiertype=��
	21.	Section 7.3.4, line 550 (example): �<spml:identifier��
	22.	Section 7.3.5, line 557: ��of this document.�
	23.	Section 7.3.5, line 560 (example): �<spml:identifier
identifiertype=��
	24.	Section 7.3.6, line 585: ��malformedRequest to��
	25.	Section 7.3.7, line 610 (example): several things - 
			a.	the ProviderIdentifier should be added
			b.	instead of <spml:identifier
operationIDType=�� it should be �<spml:operationIdentifier type=��
			c.	instead of <spml:identifier
IdentifierType=�� it should be �<spml:Identifier type=��;
			d.	Almost the same remarks apply to examples in
line 626 and 628 (btw - why 2 examples?)
	26.	Section 7.3.7, line 612: �Using the <ExtendedResponse> ��
	27.	Section 7.3.7, line 616: ��defines a mandatory
<providerIdentifier>��
	28.	Section 7.4.1, line 641 (example): �<spml:identifier
identifiertype=��
	29.	Section 7.4.2, line 648: ��service schema definition model
both implement a <providerIdentifier> element.�
	30.	Section 7.4.2, lines 652 and 654: ��control the
globally-unique identification��
	31.	Section 7.4.2, lines 670-671: ��in which the RA holds open
its �execution� call and awaits its completion. In the asynchronous model,
the RA issues its _____��
	32.	Section 7.5.2, line 683 (example): ��statusResults=��
	33.	Section 7.5.2, line 686: ��by the <StatusReturnsType>
element��
	34.	Section 7.5.2, line 693: ��with
�statusReturns=urn:oasis:names:tc:spml:1.0#result���
	35.	Section 7.5.2, line 695 (example):
�statusReturns=urn:oasis:names:tc:spml:1.0#result���
	36.	Section 7.5.2, line 696 (example): 
			a.	Instead of �statusResults� - �Result�
			b.	instead of <spml:identifier
IdentifierType=�� it should be �<spml:identifier type=��
			c.	instead of <spml:identifier �� it should be
�<spml:id��;
			d.	<spml:SearchResultEntry> should be indented
back.
	37.	Section 7.5.5, line 726: ��a <BatchRequest> based��
	38.	Section 7.5.5, line 729: ��a <DeleteRequest> ,��
	39.	Section 7.5.5, line 738: ��both provide access to
<operationalAttributes>. RAs��
	40.	Section 7.5.5.1, line 742: ��constructs a batch request��


	
Rami.

comments on the SPML 0.9 version spec.doc