In the Logical Files section, 

Consider a scenario where one logical file name (LFN) maps to different physical file names (PFN). The API description 
in its current form allows end user to create such LFN-PFN mappings. 
However in cases where the LFN - PFN mappings needs to be updated based on the current state / availability of the 
Physical Files, the existing API will need to be extended.  

General comments regarding the Strawman API Document: 
The Context API : To be able to seamlessly switch between different authentication and authorization mechanisms would 
enable several scenarios that would enable use of datasets and resources in practical situations where environments are 
based on heterogeneous middleware technologies. 

As an overall comment, once the strawman is finalized it would be helpful if samples with ample documentation are made 
available. There are several API constructs whose use would become clearer if sample application strategies are 
presented. One way would be an idea bank that acts as a repository for ideas on how the API would be used to solve 
different usecases, moderated by SAGA steering committee. 

Chirag Dekate