<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>Draft: Identity Attribute Metadata - Draft 01</title>
<meta http-equiv="Expires" content="Fri, 24 Nov 2006 17:51:11 +0000">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="Identity Attribute Metadata - Draft 01">
<meta name="generator" content="xml2rfc v1.31 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.full td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Draft</td><td class="header">D. Hardt</td></tr>
<tr><td class="header"> </td><td class="header">Sxip Identity</td></tr>
<tr><td class="header"> </td><td class="header">November 24, 2006</td></tr>
</table></td></tr></table>
<h1><br />Identity Attribute Metadata - Draft 01</h1>
<h3>Abstract</h3>
<p>
An outline of the attribute metadata schema and types for
identity attributes.
</p><a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Overview<br />
<a href="#anchor2">2.</a>
Terminology<br />
<a href="#anchor3">2.1.</a>
Definitions and Conventions<br />
<a href="#anchor4">3.</a>
Metadata Format<br />
<a href="#data-format-types">3.1.</a>
Data Format Types<br />
<a href="#anchor5">3.2.</a>
Attribute Types<br />
<a href="#anchor6">3.2.1.</a>
Standard Predicates<br />
<a href="#anchor7">3.2.2.</a>
Supplemental Predicates<br />
<a href="#anchor8">3.2.3.</a>
Example<br />
<a href="#anchor9">4.</a>
Future Directions<br />
<a href="#anchor10">4.1.</a>
Compound Properties<br />
<a href="#anchor11">4.2.</a>
Equivalents<br />
<a href="#anchor12">4.3.</a>
Higgins Ontology Predicates<br />
<a href="#rfc.references1">5.</a>
References<br />
<a href="#rfc.references1">5.1.</a>
Normative References<br />
<a href="#rfc.references2">5.2.</a>
Informative References<br />
<a href="#rfc.authors">§</a>
Author's Address<br />
</p>
<br clear="all" />
<a name="anchor1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Overview</h3>
<p>
This document defines the schema used to describe identity
object data as used in such protocols as OpenID Attribute
Exchange. The schema data is intended to be resolvable at the
URI of the identity object, the attribute type identifier.
</p>
<a name="anchor2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Terminology</h3>
<p>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described
in <a class='info' href='#RFC2119'>[RFC2119]<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a>.
</p>
<a name="anchor3"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.1"></a><h3>2.1.
Definitions and Conventions</h3>
<p>
</p>
<blockquote class="text"><dl>
<dt>Identity Object</dt>
<dd>
Identity "objects" (IdO) are defined to be sets of
name-value pairs of personal identity information. They
assert the claim that, for a given identity subject, a
named property has the provided value.
</dd>
<dt>Service Provider</dt>
<dd>
Service providers (SPs) are entities that require
identification information.
</dd>
<dt>Identity Provider</dt>
<dd>
An identification provider (IdP) stores IdOs, which are
made available to an identity agent upon request.
</dd>
<dt>Identity Agent</dt>
<dd>
The identity agent (IdA) operates under the user's
control and intermediates requests for ID objects
between the identification provider and the SP.
</dd>
<dt>Identity Attribute Type</dt>
<dd>
Identity attribute types (also referred to as simply
"attribute types") are types of subject properties
expressed in an identity context. Examples are
"surname" or "birth date".
</dd>
<dt>Identity Attribute Format Type</dt>
<dd>
The identity attribute format type ("format type")
refers to the layout of the data in the value of an
identity attribute type. They may be as simple as a
normalized string or as complicated as a telephone
number format.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor4"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
Metadata Format</h3>
<a name="data-format-types"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1"></a><h3>3.1.
Data Format Types</h3>
<p>
Data format types are the primitive types used to define the
layout of the information in the attribute values. The
types are defined in XML Schema (<a class='info' href='#W3C.REC-xmlschema-2-20041028'>[W3C.REC‑xmlschema‑2‑20041028]<span> (</span><span class='info'>Biron, P. and A. Malhotra, “XML Schema Part 2: Datatypes Second Edition,” October 2004.</span><span>)</span></a>) and include the
predefined XML Schema types.
</p>
<p>
For example, here are several formats used with the OpenID
attribute exchange protocol (<a class='info' href='#OpenID.attribute-exchange-1.0'>[OpenID.attribute‑exchange‑1.0]<span> (</span><span class='info'>Hardt, D., “OpenID Attribute Exchange,” August 2006.</span><span>)</span></a>).
</p>
<blockquote class="text"><dl>
<dt>http://schema.openid.net/types/country</dt>
<dd>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<xsd:simpleType name="country">
<xsd:restriction base="xsd:NMTOKEN">
<!-- AFGHANISTAN -->
<xsd:enumeration value="AF"/>
<!-- ÅLAND ISLANDS -->
<xsd:enumeration value="AX"/>
<!-- ALBANIA -->
<xsd:enumeration value="AL"/>
<!-- ALGERIA -->
<xsd:enumeration value="DZ"/>
... etc ...
</xsd:restriction>
</xsd:simpleType>
</pre></div>
</dd>
<dt>http://schema.openid.net/types/email</dt>
<dd>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<xsd:simpleType name="email" >
<xsd:restriction base="xsd:token">
<xsd:pattern value=
"([\.a-zA-Z0-9_-])+@
([a-zA-Z0-9_-])+(([a-zA-Z0-9_-])*\.([a-zA-Z0-9_-])+)+"
/>
</xsd:restriction>
</xsd:simpleType>
</pre></div>
</dd>
<dt>http://schema.openid.net/types/gender</dt>
<dd>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<xsd:simpleType name="gender">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="M"/>
<xsd:enumeration value="F"/>
</xsd:restriction>
</xsd:simpleType>
</pre></div>
</dd>
<dt>http://schema.openid.net/types/phone</dt>
<dd>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<xsd:simpleType name="phone">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\+?[0-9]+([- ][0-9]+)*"/>
</xsd:restriction>
</xsd:simpleType>
</pre></div>
</dd>
<dt>http://schema.openid.net/types/timezone</dt>
<dd>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<xsd:simpleType name="timezone">
<xsd:restriction base="xsd:string">
<xsd:pattern value="[a-zA-Z/-]+"/>
</xsd:restriction>
</xsd:simpleType>
</pre></div>
</dd>
</dl></blockquote><p>
</p>
<a name="anchor5"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2"></a><h3>3.2.
Attribute Types</h3>
<p>
The metadata for attribute types is expressed in RDF/XML
format. It is intended to be a fairly simple way of
expressing the minimal amount of metadata needed to describe
the attribute types. More complicated ontological data is
optional but recommended.
</p>
<p>
Each attribute type record should include a stylesheet XML
directive pointing to an XSL template that translates the
metadata into a human readable format.
</p>
<a name="anchor6"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.1"></a><h3>3.2.1.
Standard Predicates</h3>
<p>
The standard predicates that MUST be in all metadata
records are:
</p>
<blockquote class="text"><dl>
<dt>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</dt>
<dd>
The rdf:type predicate has as its object the XML
Schema data type or a type defined as per <a class='info' href='#data-format-types'>Section 3.1<span> (</span><span class='info'>Data Format Types</span><span>)</span></a>.
</dd>
<dt>http://www.w3.org/2000/01/rdf-schema#label</dt>
<dd>
The label is a short description of the attribute
type. XML provides an xml:lang attribute that can be
used on this element to provide a way to describe the
language as per <a class='info' href='#RFC4646'>[RFC4646]<span> (</span><span class='info'>Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2006.</span><span>)</span></a> used for the
content of the element. Using <a href='http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-Literal'>language
tagging</a> in this way, multiple labels can be
provided for localization purposes.
</dd>
<dt>http://www.w3.org/2000/01/rdf-schema#comment</dt>
<dd>
The rdfs:comment element is used to provide a long
textual description of the attribute type. As for the
rdf:label element, multilingual documentation is
supported by the language tagging feature of RDF literals.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor7"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.2"></a><h3>3.2.2.
Supplemental Predicates</h3>
<p>
These predicates are optional and MAY be included in
metadata records:
</p>
<blockquote class="text"><dl>
<dt>http://schema.openid.net/metadata#example</dt>
<dd>
Example value data for the attribute type.
</dd>
<dt>http://www.w3.org/2000/01/rdf-schema#seeAlso</dt>
<dd>
Indicates a resource that might provide additional
information about the subject attribute type.
</dd>
<dt>http://schema.openid.net/metadata#acquisition</dt>
<dd>
The object of this predicate is a URL from which the
IdO may be acquired. Multiple URLs may be specified.
The acquisition mechanism is not specified, but would
be retrieved using a discovery mechanism specific to
the protocol being used.
</dd>
<dt>http://schema.openid.net/metadata#authority</dt>
<dd>
Except in the case of a self-asserted IdO, a list of
authority URIs for asserted claims is necessary. Each
URI is that of an assertion authority that is allowed
to make the IdO claim.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor8"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.3"></a><h3>3.2.3.
Example</h3>
<p>
A brief example of the standard predicates and the
openid:example element as applied to the <tt>http://schema.openid.net/namePerson/first</tt>
attribute type.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="schema.xslt"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:openid="http://schema.openid.net/metadata#">
<rdf:Description rdf:about="http://schema.openid.net/namePerson/first">
<rdfs:label>
First name
</rdfs:label>
<rdfs:comment>
First or given name of subject
</rdfs:comment>
<openid:example>
John
</openid:example>
<rdf:type
rdf:resource="http://www.w3.org/2001/XMLSchema#normalizedString"/>
<openid:acquisition
rdf:resource="http://example.gov/id"/>
</rdf:Description>
</rdf:RDF>
</pre></div>
<a name="anchor9"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4"></a><h3>4.
Future Directions</h3>
<p>
Additional metadata information may be added as more complex
attribute types are constructed. The following sections
outline possible extensions to the existing simple type
definitions.
</p>
<a name="anchor10"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4.1"></a><h3>4.1.
Compound Properties</h3>
<p>
The IdO may also be composed of an aggregate of other IdO
types, in which case the aggregate IdO URIs will be
referenced.
</p>
<a name="anchor11"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4.2"></a><h3>4.2.
Equivalents</h3>
<p>
An IdO may make a claim that is equivalent to the claim of
an IdO of a different type. The equivalent IdO types are
listed in this section.
</p>
<p>
An IdO may be transformed to one of a different type if it
is listed as an equivalent. This property is not
commutative.
</p>
<p>
This information may be extended to include translation
mechanisms between format types. A richer transform
specification would allow claims to be made based on a
broader equivalence domain.
</p>
<a name="anchor12"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4.3"></a><h3>4.3.
Higgins Ontology Predicates</h3>
<p>
The Higgins project has created a base ontological
vocabulary at <a class='info' href='#Higgins-Ontology'>[Higgins‑Ontology]<span> (</span><span class='info'>Trevithick, P., “Higgins Ontology v1.10,” October 2006.</span><span>)</span></a>. Use of
this vocabulary allows for the integration of the attribute
types into a broader catalog.
</p>
<a name="rfc.references"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5"></a><h3>5.
References</h3>
<a name="rfc.references1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>5.1. Normative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="OpenID.attribute-exchange-1.0">[OpenID.attribute-exchange-1.0]</a></td>
<td class="author-text"><a href="mailto:dick@sxip.com">Hardt, D.</a>, “OpenID Attribute Exchange,” August 2006 (<a href="http://www.openid.net/specs/openid-attribute-exchange-1_0-01.txt">TXT</a>, <a href="http://www.openid.net/specs/openid-attribute-exchange-1_0-01.html">HTML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
<td class="author-text"><a href="mailto:sob@harvard.edu">Bradner, S.</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,” BCP 14, RFC 2119, March 1997 (<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2119.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2119.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC4646">[RFC4646]</a></td>
<td class="author-text">Phillips, A. and M. Davis, “<a href="ftp://ftp.isi.edu/in-notes/rfc4646.txt">Tags for Identifying Languages</a>,” BCP 47, RFC 4646, September 2006.</td></tr>
<tr><td class="author-text" valign="top"><a name="W3C.REC-xmlschema-2-20041028">[W3C.REC-xmlschema-2-20041028]</a></td>
<td class="author-text">Biron, P. and A. Malhotra, “<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028">XML Schema Part 2: Datatypes Second Edition</a>,” World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004 (<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028">HTML</a>).</td></tr>
</table>
<a name="rfc.references2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>5.2. Informative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="Higgins-Ontology">[Higgins-Ontology]</a></td>
<td class="author-text">Trevithick, P., “<a href="http://www.eclipse.org/higgins/ontologies/2006/higgins.owl">Higgins Ontology v1.10</a>,” October 2006.</td></tr>
</table>
<a name="rfc.authors"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>Author's Address</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text"> </td>
<td class="author-text">Dick Hardt</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Sxip Identity</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">798 Beatty Street</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Vancouver, BC V6B 2M1</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">CA</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:dick@sxip.com">dick@sxip.com</a></td></tr>
<tr><td class="author" align="right">URI: </td>
<td class="author-text"><a href="http://sxip.com/">http://sxip.com/</a></td></tr>
</table>
</body></html>