[gfs-wg] RNS telecon, 13 Oct

[Osamu Tatebe]

Hi all,

Minutes Attached.  If there is any comment or modification, please
let me know.

Thanks,
Osamu

>> On Tue, 11 Oct 2005 17:00:49 +0900 (JST), Osamu Tatebe <o.tatebe at aist.go.jp> said:

>> We will have the teleconference to finalize the RNS spec on Thursday,
>> October 13, 2005 at 4pm in California time.
-------------- next part --------------
GFS-WG telecon
October 13, 2005 at 4pm in California time

Note taker: Osamu Tatebe (AIST)

Participant:

Manuel Pereira (IBM)
Arun Jagatheesan (SDSC)
Osamu Tatebe (AIST)

Agenda
------
1. RNS update
2. RNS spec discussion

Meeting
-------
1. RNS update

 - equality issue of EPR

 - information issue embedding in EPR
   root level custom tag will be dropped in some implementation
   including apache axis
   -> rns:PathRemainder is moved to reference property level from
      root level

2. RNS spec discussion

 - In the section 1.1.3.2.3, "Name MUST NOT Be greater than 255
   characters in length (Unicode)".  Is this restriction really
   necessary?
   -> Unnecessary restriction is better to be avoided for wider
      applicability.  On the other hand, allowing unlimited length can
      cause an interoperability problem, since limit of length is
      implementation dependent.  FYI - length of filename is limited
      to 239 characters in Windows, and 256 characters in NFS.

 - In the section 1.1.3.1.2 Absolute Path, there is no description how
   to specify the root directory
   -> add description, but it is basically out of the scope of the
      spec.

 - In the figure on page 41, PathRemainder does not start with '/'.
   -> fix

 - Example on page 41 shows referral case that points to the top
   directory of another RNS service.  It might be better that the
   referral points to a particular virtual directory not the top
   directory within the service, since more complex example can cover
   more complex case.
   -> try to change the example

 - Referral reference cannot be returned by other operations than
   lookup and list, since ChangeResponse cannot return EPR.
   -> add xsd:any to ChangeResponse to enable to return EPR.

* Action plan

 - RNS spec that reflects thd discussion will be out in a week
 - final review until October 28
 - submit the RNS spec on October 28