SourceForge : Post

Project: Editor Discussion > REC: JSDL Spec v1.0 > Directories and logical files in JSDL > List of Posts

Forum Topic - Directories and logical files in JSDL: (2 Items)

View: as

09/02/2005 11:05 AM

post4645

Directories and logical files in JSDL

In the DataStaging element JSDL does not allow distinguishing between 
(i) a regular file and a directory
(ii) a logical file identifier and its physical location.
A user (or a software acting on behalf of a user) usually is (and should be!) aware whether he transfers files or 
directory.
Besides a scheduler may often need this knowledge to perform data staging (e.g. it may have to know whether a given file
 location is a logical name and if it is the name of a regular file or directory to call appropriate methods of a data 
management system).  
This could be expressed using appropriate attributes and by alternative elements (using the choice element). For example
, the pseudo-schema for the FileName and Source/Target elements could look as follows:

<FileName isDirectory="xsd:boolean"?> 
   xsd:string 
</FileName>

<Source>
   <xs:choice>
      <URI ... />?
      <logicalID ... />?
   </xs:choice>
   <xsd:any##other>*
</Source>?

Andreas Savva

10/11/2005 5:30 AM

post4646

Re:Directories and logical files in JSDL

This was discussed at GGF15 and the consensus was that no change was needed for JSDL 1.0. 
We'll probably discuss such issues in more detail after version 1.0  when considering extensions to refine data staging.

1. Files and directories
  It was pointed out that making this distinction is not essential for correct operation. Two implementors confirmed 
that not having this additional information was not a problem.
  Also even if this additional information is included the system would have to check that the information is correct so
 the benefit is debatable.
  Finally, a scheduler may benefit from such additional information but this really points strongly that such 
description is out of scope of JSDL 1.0 which does not deal with scheduling.

2. Logical file identifiers
  The URI element itself may hold a logical file identifier, for example by using an appropriate scheme. Otherwise this 
seems to fall in the same category as an earlier comment to add EPRs as optional elements to the Source or Target. See 
also  message 1266 on this forum.

Return