BusinessCardExpl

This is a rather ad hoc and simple approach to identity management. Developers should consider specifications of http://www.idcommons.net/ (with awareness of privacy concerns also http://www.projectliberty.org/ and http://www-106.ibm.com/developerworks/webservices/library/ws-fed/ ) to implement more elaborarate and complete specifications. (That might incure system core extensions.)

Purpose

Each entry point (which is s place representing a natural person), should internally hold a single xml element representing the users business card. Children elements are used to it mark up the properties/attributes of the person. There is also a simple vCard data base in AdrDb2.

Access

It is recommented that the business card is delivered from the entry point without access restrictions upon a request method with a template value of business-card, which would be access via url like this:

 http://.../A....?template=business-card

This corresponds to a SOAP? message like this:

<?xml version="1.0" ?>
<env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope">
 <env:Body>
  <m:form> 
   <m:template>business-card</m:template>
  </m:form>
 </env:Body>
</env:Envelope>

which in turn is the same as:

<mind:send type="read"
           xmlns:env="http://www.w3.org/2001/09/soap-envelope">
 <to>target specification</to>
 <env:Body>
  <m:form> 
   <m:template>business-card</m:template>
  </m:form>
 </env:Body>
</mind:send>

The code snippet BusinessCardView could be used to implement an answer to this request.

Content

The element names should be taken from the vCard standard (rfc 2426). Field values also correspond to the vCard standard, except that there is no substructuring within text values (like comma or semicolon separated fields). The correspondig fields are modelled as subelements.

Fields occure zero or more times, there is no order between the elements (dtd is missing here).

Example:

warningFIXME?: This example became inconsistent. The vcard-rdf defines a different structure than what we have here.

<rdf:Description
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://www.w3.org/2001/vcard-rdf/3.0#"
  about="<oid>"
>
 <!-- formatted name -->
 <fn>Jörg F. Wittenberger</fn>
 <n>
  <surname>Wittenberger</surname>
  <firstname>Jörg</firstname>
  <middlename>F.</middlename>
  <honorific/>
 </n>
 <nickname>Jerry</nickname>
 <photo><output media-type="image/jpeg>...</output></photo>
 <photo resource="xpath value (prefered '/oid' ) "/>
 <bday>1965-12-23</bday>
 <adr>
  <affilation>softeyes</affilation>
  <street>Erlenstr. 22</street>
  <city>Dresden</city>
  <zip>01097</zip>
 </adr>
</rdf:Description>

Source code:

<p>This is a rather ad hoc and simple approach to identity management.
Developers should consider specifications of
<a href="http://www.idcommons.net/">http://www.idcommons.net/</a>
(with awareness of privacy concerns also
<a href="http://www.projectliberty.org/">http://www.projectliberty.org/</a>
and
<a href="http://www-106.ibm.com/developerworks/webservices/library/ws-fed/">http://www-106.ibm.com/developerworks/webservices/library/ws-fed/</a>
) to implement more elaborarate and complete specifications.
(That might incure system core extensions.)
</p>
<h2>Purpose</h2>
<p>Each entry point
(which is s place representing a natural person),
should internally hold a single xml element
representing the users business card.
Children elements are used to it mark up the properties/attributes
of the person.
There is also a simple vCard data base in AdrDb2.</p>
<h2>Access</h2>
<p>It is recommented that the business card is delivered from the
entry point without access restrictions
upon a request method with a template value of
<code>business-card</code>, which would be access via url like this:</p>
<pre xml:space="preserve">
 <a href="http://.../A....?template=business-card">http://.../A....?template=business-card</a>
</pre>
<p>This corresponds to a SOAP message like this:</p>
<pre xml:space="preserve">
&lt;?xml version="1.0" ?&gt;
&lt;env:Envelope xmlns:env="<a href="http://www.w3.org/2001/12/soap-envelope&quot;">http://www.w3.org/2001/12/soap-envelope"</a>&gt;
 &lt;env:Body&gt;
  &lt;m:form&gt; <!-- xmlns:m="http://askemos.org/mind"> -->
   &lt;m:template&gt;business-card&lt;/m:template&gt;
  &lt;/m:form&gt;
 &lt;/env:Body&gt;
&lt;/env:Envelope&gt;
</pre>
<p>which in turn is the same as:</p>
<pre xml:space="preserve">
&lt;mind:send type="read"
           xmlns:env="<a href="http://www.w3.org/2001/09/soap-envelope&quot;">http://www.w3.org/2001/09/soap-envelope"</a>&gt;
 &lt;to&gt;<var>target specification</var>&lt;/to&gt;
 &lt;env:Body&gt;
  &lt;m:form&gt; <!-- xmlns:m="http://askemos.org/mind"> -->
   &lt;m:template&gt;business-card&lt;/m:template&gt;
  &lt;/m:form&gt;
 &lt;/env:Body&gt;
&lt;/mind:send&gt;
</pre>
<p>The code snippet BusinessCardView could be used
to implement an answer to this request.</p>
<h2>Content</h2>
<p>The element names should be taken from the vCard standard (rfc 2426).
Field values also correspond to the vCard standard,
except that there is no substructuring within text values
(like comma or semicolon separated fields).
The correspondig fields are modelled as subelements.</p>
<p>Fields occure zero or more times,
there is no order between the elements (dtd is missing here).</p>
<p>Example:</p>
<p>*warning*FIXME: This example became inconsistent.
The vcard-rdf defines a different structure than what we have here.</p>
<pre xml:space="preserve">
&lt;rdf:Description
  xmlns:rdf="<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;">http://www.w3.org/1999/02/22-rdf-syntax-ns#"</a>
  xmlns="<a href="http://www.w3.org/2001/vcard-rdf/3.0#&quot;">http://www.w3.org/2001/vcard-rdf/3.0#"</a>
  about="<var>&lt;oid&gt;</var>"
&gt;
 &lt;!-- formatted name --&gt;
 &lt;fn&gt;Jörg F. Wittenberger&lt;/fn&gt;
 &lt;n&gt;
  &lt;surname&gt;Wittenberger&lt;/surname&gt;
  &lt;firstname&gt;Jörg&lt;/firstname&gt;
  &lt;middlename&gt;F.&lt;/middlename&gt;
  &lt;honorific/&gt;
 &lt;/n&gt;
 &lt;nickname&gt;Jerry&lt;/nickname&gt;
 &lt;photo&gt;&lt;output media-type="image/jpeg&gt;...&lt;/output&gt;&lt;/photo&gt;
 &lt;photo resource="<var>xpath value (prefered '/oid' ) </var>"/&gt;
 &lt;bday&gt;1965-12-23&lt;/bday&gt;
 &lt;adr&gt;
  &lt;affilation&gt;softeyes&lt;/affilation&gt;
  &lt;street&gt;Erlenstr. 22&lt;/street&gt;
  &lt;city&gt;Dresden&lt;/city&gt;
  &lt;zip&gt;01097&lt;/zip&gt;
 &lt;/adr&gt;
&lt;/rdf:Description&gt;
</pre>