OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [no subject]


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_001_01C43E15.E3F8B860
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D066513202-20052004><FONT size=3D2>Before going any =
further, I=20
wanted to come back to this point once again. Since people who were not =
present=20
at NOLA f2f did not have a chance to get involved in the lengthy =
discussion=20
there, I think it is worthwhile to revisit it online. =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT size=3D2>So, what is "link" =
after all?=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT size=3D2>If I remember =
correctly, the=20
main difference from &lt;resource&gt; and &lt;link&gt; in Drummond's =
model is=20
that the later is the cached copy of the former. In another word,=20
&lt;resource&gt; is authoritative, and &lt;link&gt; is not. Is that =
right?=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>If it is the=20
real reason, then IMHO it is not a very strong reason to difine =
&lt;link&gt; as=20
the first class object, but some attribute of it e.g. &lt;resource=20
status=3D"non-authoritative"&gt; would do. </FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>I have always=20
viewd the "Contract" a very important feature of XNS because it is a =
touch point=20
of the cyber world and the real world. To be acceptable as a legal =
contract, it=20
should have certain qualities, and I believe "Link Contract" should =
satisfy=20
them. This means that we have to impose certain structure to it: more =
than just=20
what has been discribed in Drummond's draft. This precicely is the =
reason why I=20
drew up a version which had much more structure in it. =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>Let me extract=20
my version of the "LinkContract" from the uploaded meta-schema for the=20
readability. </FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>&lt;element=20
name=3D"LinkContract"&gt;<BR>&nbsp;&lt;complexContent&gt;<BR>&nbsp;&nbsp;=
=20
&lt;extension base=3D"Resource"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;element=20
name=3D"parties"=20
type=3D"Xri"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
&lt;complexType&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
&lt;sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;element name=3D"party"=20
type=3D"Xri"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
minOccurs=3D"2"=20
maxOccurs=3D"unbounded"/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/sequence&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
&lt;/complexType&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/element&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;element=20
name=3D"jurisdiction" type=3D"Xri" =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;element name=3D"templateID" type=3D"Xri"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;element name=3D"date" =
type=3D"Xri"=20
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;element name=3D"dsig"=20
type=3D"ds:Signature" /&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
&lt;/sequence&gt;<BR>&nbsp;&nbsp;=20
&lt;/extension&gt;<BR>&nbsp;&lt;/complexContent&gt;<BR>&lt;/element&gt;</=
FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>I wrote it as=20
an extension to Resource, but equally, it could be a stand alone =
element. What I=20
would like to discuss in this thread is not the construction of the =
schema=20
(there are many ways to represent objects in XML schema, as you know), =
but on=20
what kind of information the "Link Contract" should have. =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>From the above,=20
you probably can see that I am proposing following things to be included =
in the=20
"Link Contract". </FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>1) XRI of the=20
parties involved. In any contract, we need to specify the parties =
involed.=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>2) templateID:=20
this points to the contract template, in which other information like =
parties=20
can be inserted to make it a complete contract. </FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>3)=20
Jurisdiction: We need to specify in which jurisdiction this contract is=20
governed. </FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>4) date: we=20
need date in the contract</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>5) dsig:=20
Digital Signature of some form. </FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" size=3D2>Any thoughts?=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066513202-20052004><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;"=20
size=3D2>Nat</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C43E15.E3F8B860--


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]