[mdx] Request URL format description

[Milan Sova]

On 03/08/2011 02:28 PM, Chad La Joie wrote:
> 2011/3/8 Milan Sova <sova at cesnet.cz>:
>> 3.2.1. defines the request URL format as:
>>
>> "<base_url>/entities/{ID}+{ID}+..."
>>
>> i. e. the request is constructed by concatenating  the base_url value,
>> the literal "/entities/" and the list of IDs.
>>
>>  - ( just curious, what is the purpose of inserting the string
>> "/entities/"?)
> 
> Just so that there is a well-known "collection" identifier in the URL.
>  Initially there were two such collections but we merged them together
> given a suggestions by Leif.
> 
>>  - my first reading of the format would imply that the IDs should be
>> enclosed in {}. However, in the example in 3.2.3 the ID is used without
>> them. I assume the example is correct, right? If yes, the request URL
>> format in 3.2.1. might be better described as:
> 
> The '{' and '}' were simply markers for "identifier goes here".

	Then <> (as in <base_url>) would be more obvious.

> Pretty sure the actual normative text does not say anything about
> them.

	It does not say anything about "/entites/" and "+" either and the text
before mentions special meaning of {. That lead to my confusion. I still
think that the request URL format description might be more explanatory.

	Regards
-- 
						Milan Sova
						sova at cesnet.cz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5557 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.iay.org.uk/pipermail/mdx-iay.org.uk/attachments/20110308/11807baf/attachment-0002.bin>