[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
=20
1) XRI of the parties involved. In any contract, we need to specify the
parties involed.=20
2) templateID: this points to the contract template, in which other
information like parties can be inserted to make it a complete contract. =
3) Jurisdiction: We need to specify in which jurisdiction this contract =
is
governed.=20
4) date: we need date in the contract
5) dsig: Digital Signature of some form.=20
=20
Any thoughts?=20
=20
Nat
------=_NextPart_000_0150_01C441CB.95DB99E0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"time"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"date"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: MS PGothic;
}
@font-face {
font-family: @MS PGothic;
}
@page {mso-endnote-separator: url("cid:header.htm\@01C441B8.72409700";) =
es; mso-endnote-continuation-separator: =
url("cid:header.htm\@01C441B8.72409700";) ecs; }
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
H1 {
FONT-SIZE: 16pt; MARGIN: 12pt 0in 3pt; FONT-FAMILY: Arial
}
H2 {
FONT-SIZE: 14pt; MARGIN: 12pt 0in 3pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial
}
H3 {
FONT-SIZE: 12pt; MARGIN: 12pt 0in 3pt; FONT-FAMILY: Arial
}
H4 {
FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt; FONT-STYLE: italic; FONT-FAMILY: =
"Times New Roman"
}
P.MsoHeader {
BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; =
PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDING-BOTTOM: 0in; MARGIN: 0in 0in =
0pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none; FONT-FAMILY: Arial
}
LI.MsoHeader {
BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; =
PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDING-BOTTOM: 0in; MARGIN: 0in 0in =
0pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none; FONT-FAMILY: Arial
}
DIV.MsoHeader {
BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; =
PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDING-BOTTOM: 0in; MARGIN: 0in 0in =
0pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none; FONT-FAMILY: Arial
}
P.MsoFooter {
BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; =
PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDING-BOTTOM: 0in; MARGIN: 0in 0in =
0pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none; FONT-FAMILY: Arial
}
LI.MsoFooter {
BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; =
PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDING-BOTTOM: 0in; MARGIN: 0in 0in =
0pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none; FONT-FAMILY: Arial
}
DIV.MsoFooter {
BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; =
PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDING-BOTTOM: 0in; MARGIN: 0in 0in =
0pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none; FONT-FAMILY: Arial
}
P.MsoTitle {
FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 0in 0in 9pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
LI.MsoTitle {
FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 0in 0in 9pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
DIV.MsoTitle {
FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 0in 0in 9pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
P.MsoBodyText {
FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoBodyText {
FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoBodyText {
FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Times New Roman"
}
P.MsoSubtitle {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0.25in; FONT-FAMILY: Arial; =
TEXT-ALIGN: center
}
LI.MsoSubtitle {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0.25in; FONT-FAMILY: Arial; =
TEXT-ALIGN: center
}
DIV.MsoSubtitle {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0.25in; FONT-FAMILY: Arial; =
TEXT-ALIGN: center
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P.Quote {
FONT-SIZE: 12pt; MARGIN: 0in 0.5in 6pt; FONT-STYLE: italic; =
FONT-FAMILY: "Times New Roman"
}
LI.Quote {
FONT-SIZE: 12pt; MARGIN: 0in 0.5in 6pt; FONT-STYLE: italic; =
FONT-FAMILY: "Times New Roman"
}
DIV.Quote {
FONT-SIZE: 12pt; MARGIN: 0in 0.5in 6pt; FONT-STYLE: italic; =
FONT-FAMILY: "Times New Roman"
}
P.Wiki {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.Wiki {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.Wiki {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
P.Graphic {
FONT-SIZE: 10pt; MARGIN: 0in 0in 6pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
LI.Graphic {
FONT-SIZE: 10pt; MARGIN: 0in 0in 6pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
DIV.Graphic {
FONT-SIZE: 10pt; MARGIN: 0in 0in 6pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
SPAN.EmailStyle26 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D092192501-25052004><FONT face=3DTahoma size=3D2>I =
think we're 90%=20
in agreement. Comments inline...</FONT></SPAN></DIV>
<DIV><SPAN class=3D092192501-25052004><FONT face=3DTahoma=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D092192501-25052004><FONT face=3DTahoma=20
size=3D2>=3DLoren</FONT></SPAN></DIV>
<DIV><SPAN class=3D092192501-25052004><FONT face=3DTahoma =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Drummond Reed=20
[mailto:drummond.reed@cordance.net] <BR><B>Sent:</B> Monday, May 24, =
2004 5:57=20
PM<BR><B>To:</B> 'Loren West'; 'Sakimura, Nat';=20
xdi@lists.oasis-open.org<BR><B>Subject:</B> RE: [xdi] What is "link" =
after=20
all?<BR><BR></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I'd propose a =
different=20
answer to this question. If you look at it in XDI graph terms, there is =
a=20
critical difference between a Link relationship and a Resource =
relationship.=20
Resource relationships are purely acyclic (hierarchical) – they =
can define only=20
trees. Link relationships are cyclic – they join two trees, or =
join the branches=20
or leaves of a single tree.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">When this =
acyclic vs.=20
cyclic model is applied to XDI as an endless acyclic graph (a web) =
capable of=20
describing all data, then the root of every tree in this web is an =
*<B><SPAN=20
style=3D"FONT-WEIGHT: bold">authority</SPAN></B>*. Exactly like the root =
of every=20
website – a home page – has an authority responsible for its =
content (both=20
technically and legally).<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">In short: the =
question=20
of link vs. resource is the question of: who's data is it? Who controls =
the=20
identifiers and assertions being made at any point in the=20
graph?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I believe =
this=20
authority control element is absolutely vital to XDI. It is the heart of =
what=20
distinguishes it from RDF, which provides very rich data description, =
XML, which=20
provides very extensible data representation, and HTTP, which provides =
very=20
flexible content exchange and negotiation.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">What XDI is =
able to=20
model that is not natively done in these other bodies of work is data =
authority=20
and agreement between data authorities (link contracts). That's why it =
is such a=20
fundamental solution to problems of privacy and data protection.<FONT=20
face=3DTahoma><FONT color=3D#0000ff><SPAN=20
class=3D092192501-25052004> </SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
face=3DTahoma><FONT=20
color=3D#0000ff><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN class=3D092192501-25052004>[Loren] - We =
are in=20
agreement with the concepts above. The flaw is in tying these =
concepts into the XML tag (or worse, into the XRI address). You =
get every=20
bit as much value by containing this information within the =
LinkContract. =20
In fact, you get more value by having it in a single place. If =
that=20
metadata is copied into 3 different places, it WILL get out of =
sync. =20
Which one's authoritative?</SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN class=3D092192501-25052004>The logical flaw is in =
the=20
<STRONG>therefore</STRONG>. You say that all this stuff is =
important,=20
<STRONG>therefore </STRONG>it's important to represent them in the XRI =
and XML=20
tag. Not so. These things are important, and representing =
them in=20
the XRI and/or XML tag has no effect on that=20
importance.</SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN class=3D092192501-25052004>I'm fairly passionate =
about not=20
polluting the XRI with this metadata. If I have a filename like=20
/usr/lib/X11/libX11.a, it shouldn't matter that /usr/lib is =
authoritative=20
for X11 or if X11 is a symbolic link. Having to represent it as=20
/usr/lib*X11/libX11.a just because X11 is a symbolic =
link really=20
screws things up (I can explain if you want). Maybe the people who =
wrote=20
symbolic links thought it important enough to deserve a different =
character, but=20
if they got their way, we'd be in a world of hurt. If anyone cares =
to=20
know, there's a way to query the=20
metadata.</SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN class=3D092192501-25052004>Maybe =
=3DLoren/BusinessCard/Address=20
is maintained by Epok, but chances are, nobody gives a rip. Also, =
chances=20
are it's maintained by me at first, then by Epok once they get on the =
XDI=20
bandwagon.</SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN class=3D092192501-25052004>Furthermore, I want the =
ability to=20
choose with whom I share that=20
metadata. </SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT><FONT><SPAN=
=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN class=3D092192501-25052004>Same argument for =
<link> vs.=20
<resource></SPAN></FONT></FONT></SPAN></FONT></P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004></SPAN></FONT></FONT></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D092192501-25052004>[/Loren]</SPAN></FONT></FONT></SPAN></FONT></P=
>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Net net: this =
is why I=20
believe links are such a vital feature of the proposed XDI metaschema, =
and also=20
the heart of link contracts.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I'm working =
on more=20
detailed examples to illustrate this but don't expect to get them posted =
until=20
late tomorrow.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">=3DDrummond=20
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Loren=20
West [mailto:loren.west@epok.net] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, <st1:date=20
style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
w:st=3D"on" ls=3D"trans" Month=3D"5" Day=3D"24" Year=3D"2004">May 24, =
2004</st1:date>=20
<st1:time w:st=3D"on" Hour=3D"16" Minute=3D"45">4:45 =
PM</st1:time><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Sakimura, Nat';=20
xdi@lists.oasis-open.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [xdi] What is "link" =
after=20
all?</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">Hello=20
XDI'ers,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">If I =
understand it=20
correctly, the difference between <link> and <resource> =
isn't as=20
much if it's cached as if the containing resource is the "owner" of the=20
contained resource (they're often the same, but it's a subtle=20
difference).</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">The presence =
or=20
absence of a LinkContract governing the relationship provides the same=20
information, and I'm with you - the XML doesn't need to be different =
based on=20
this characteristic of the =
relationship.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">This is =
similar to my=20
argument that the XRI identifier shouldn't be different because of this=20
characteristic of the relationship.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">Not to =
diminish the=20
importance of this characteristic, it's just that neither the identifier =
nor the=20
XML tag should change when this attribute of the relationship =
(inevitably)=20
changes.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">As far as =
your=20
proposal for LinkContract portion, I see two different=20
threads:</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">1) Where =
does it go=20
within the XDI document, and</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">2) What is =
its=20
structure</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">I propose we =
handle=20
these in two separate email threads because each has a life of it's=20
own.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Tahoma">=3DLoren</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3DTahoma =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Sakimura,=20
Nat [mailto:n-sakimura@nri.co.jp] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, <st1:date=20
style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
w:st=3D"on" ls=3D"trans" Month=3D"5" Day=3D"19" Year=3D"2004">May 19, =
2004</st1:date>=20
<st1:time w:st=3D"on" Hour=3D"19" Minute=3D"55">7:55 =
PM</st1:time><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
xdi@lists.oasis-open.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [xdi] What is "link" =
after=20
all?</SPAN></FONT><o:p></o:p></P>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">Before going any further, I wanted to come =
back to this=20
point once again. Since people who were not present at NOLA f2f did not =
have a=20
chance to get involved in the lengthy discussion there, I think it is =
worthwhile=20
to revisit it online. </SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">So, what is "link" after all?=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">If I remember correctly, the main difference =
from=20
<resource> and <link> in Drummond's model is that the later =
is the=20
cached copy of the former. In another word, <resource> is =
authoritative,=20
and <link> is not. Is that right? =
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">If it is the real =
reason,=20
then IMHO it is not a very strong reason to difine <link> as the =
first=20
class object, but some attribute of it e.g. <resource=20
status=3D"non-authoritative"> would do. =
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">I have always viewd =
the=20
"Contract" a very important feature of XNS because it is a touch point =
of the=20
cyber world and the real world. To be acceptable as a legal contract, it =
should=20
have certain qualities, and I believe "Link Contract" should satisfy =
them. This=20
means that we have to impose certain structure to it: more than just =
what has=20
been discribed in Drummond's draft. This precicely is the reason why I =
drew up a=20
version which had much more structure in it. =
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">Let me extract my =
version of=20
the "LinkContract" from the uploaded meta-schema for the readability.=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"><element=20
name=3D"LinkContract"><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt"> </SPAN></FONT><FONT face=3D"MS PGothic" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS =
PGothic'"><complexContent><BR></SPAN></FONT><FONT=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt"> </SPAN></FONT><FONT =
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <extension=20
base=3D"Resource"><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
<sequence><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <element =
name=3D"parties"=20
type=3D"Xri"><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT=
><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
<complexType><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> &=
nbsp;</SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
<sequence><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> &=
nbsp; </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <element =
name=3D"party"=20
type=3D"Xri"<BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> &=
nbsp; </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> minOccurs=3D"2"=20
maxOccurs=3D"unbounded"/><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> &=
nbsp;</SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
</sequence><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT=
><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
</complexType><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
</element><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <element=20
name=3D"jurisdiction" type=3D"Xri" /><BR></SPAN></FONT><FONT =
size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <element=20
name=3D"templateID" type=3D"Xri" /><BR></SPAN></FONT><FONT =
size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <element =
name=3D"date"=20
type=3D"Xri" /><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'"> <element =
name=3D"dsig"=20
type=3D"ds:Signature" /><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt"> </SPAN></FONT><FONT=20
face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
</sequence><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt"> </SPAN></FONT><FONT face=3D"MS =
PGothic"=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">=20
</extension><BR></SPAN></FONT><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt"> </SPAN></FONT><FONT face=3D"MS PGothic" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS =
PGothic'"></complexContent><BR></element></SPAN></FONT><o:p><=
/o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">I wrote it as an =
extension to=20
Resource, but equally, it could be a stand alone element. What I would =
like to=20
discuss in this thread is not the construction of the schema (there are =
many=20
ways to represent objects in XML schema, as you know), but on what kind =
of=20
information the "Link Contract" should have. =
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">From the above, you =
probably=20
can see that I am proposing following things to be included in the "Link =
Contract". </SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">1) XRI of the =
parties=20
involved. In any contract, we need to specify the parties involed.=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">2) templateID: this =
points to=20
the contract template, in which other information like parties can be =
inserted=20
to make it a complete contract. </SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">3) Jurisdiction: We =
need to=20
specify in which jurisdiction this contract is governed.=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">4) date: we need =
date in the=20
contract</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">5) dsig: Digital =
Signature of=20
some form. </SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS PGothic'">Any thoughts?=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"MS PGothic" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'MS =
PGothic'">Nat</SPAN></FONT><o:p></o:p></P></DIV></DIV></BODY></HTML>
------=_NextPart_000_0150_01C441CB.95DB99E0--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]