Issue 115 & 118 and Syncing X.509 profile with Interop v 1.0 document

["Hallam-Baker, Phillip" <pbaker@verisign.com>]

Changelog as follows:

The Value type for the cert is now wsse:X509v3
This means that there are two ways a new version of the QName can be
defined:

1) If there is a new X.509 data format a QName of the form wsse:X509v4 would
be appropriate
2) If the specification changes such that an X.509 token is interpreted in a
different way a new namespace prefix wsseplus might be appropriate, or a new
QName label could be defined X509v3Plus or such.

I believe that this change also closes issue 115 on the Qname for Value Type
wrt certificates.

I have changed the PKIPath value type to wsse:X509PKIPathv1 for consistency.

Note that the v3 in X.509v3 refers to the certificate data format version
number, not the specification version number which is actually a year. Since
PKIPath is also a data format it is appropriate to refer to it as version 1.
This is consistent with the handling of CRLs which are refered to as v1 and
v2, there is no v3 of the CRL data format.

There is a minor typo at line 446 & 581 of the interop spec, a space has
crept into the middle of the value type.


Issue 118 is listed as open in the issues list but was CLOSED
http://lists.oasis-open.org/archives/wss/200307/msg00045.html

    - 118: CLOSED, consensus around leaving text as is, recommending 
      PKIPath, but allowing PKCS7