<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
You are correct, guid does imply RFC4122. The relevant text (from p. 7
of the document) is:<br>
<br>
We recommend using the standard "globally unique identifier" (guid) for
this. Rules for constructing a guid are given by RFC4122[3], and
implemented by several freely available libraries and the uuidgen
program (a standard utility on Windows and Unix). Guid's should be
encoded in the string representation given by RFC4122, e.g.
"5006F942-B782-4D86-9E66-63EB03269FD0". For situations where it is
important to have a smaller identifier, one can optionally use a local
identifier such as a request or transaction number. The reserved field
names are: "guid" for a guid and "id" for a local identifier. Software
processing log events should look for both "guid" and "id" fields, in
that order.<br>
<br>
So, the text implies that you had better have a proper RFC4122
identifier if you use GUID. Brian was simply letting you in on the
little "secret" that in practice we're not planning on checking guid
formats.<br>
<br>
-Dan<br>
<br>
Ben Clifford wrote:
<blockquote
cite="mid:Pine.LNX.4.64.0709112049560.7456@dildano.hawaga.org.uk"
type="cite">
<pre wrap="">
On Tue, 11 Sep 2007, Brian Tierney wrote:
</pre>
<blockquote type="cite">
<pre wrap="">There is no standard for this. Your own GUID should be fine.
</pre>
</blockquote>
<pre wrap=""><!---->
the term guid often implies a uuid in the syntax described
in RFC4122
does that hold here or no? would be useful to clarify.
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="79">--
Dan Gunter. voice:510-495-2504 fax:510-486-6363 dsd.lbl.gov/~dang
</pre>
</body>
</html>