Versioning Teleconference February 28, 2000 Present: Henry Harbury, Jim Amsden, Jim Whitehead, Geoff Clemm, Tim Ellison Minutes recorded by Jim Whitehead *** Note that decisions made during the teleconference are always subject to review on the mailing list. The mailing list is the final arbiter of consensus on any issue. *** To discuss: live properties vs. methods, default revision selection, repositories, namespace control of versioning resources, i18n of labels i18n of headers: Agree that labels need to be able to express ISO10646 characters. For labels in XML, can use standard XML character set encodings (UTF-8 or UTF-16). For labels in HTTP headers, we will use a simple encoding for UTF-8 in headers (%xx, etc.) namespace control of versioning resources: One server may have constraints on the names of versioning resources, another may not. One proposal is that clients need to discover where versioning resources need to be created, and that this information will be conveyed using the REPORT method. Some uneasiness with conveying this information using REPORT. User need is to find out where the workspace resources are located. This topic is closely related to the issue of what happens when a client approaches a DeltaV server for the first time. What kind of configuration information does the user have to type in? Some discussion over whether DASL will be ready in time to use it. But, DASL just tells you that something is there, not whether that is the normative place to put things. Two issues: where do I put my workspace? (use a REPORT for this). Different from: where are the workspaces? Might need two different mechanisms here. *** End of Teleconference ***