W3C home > Mailing lists > Public > public-xg-webid@w3.org > February 2011

Re: qualified "reference" FYI

From: Henry Story <henry.story@bblfish.net>
Date: Tue, 8 Feb 2011 17:47:47 +0100
Cc: "public-xg-webid@w3.org" <public-xg-webid@w3.org>
Message-Id: <A6E455F6-431D-45F6-8957-CEA100043F20@bblfish.net>
To: Peter Williams <home_pw@msn.com>

On 8 Feb 2011, at 17:34, Peter Williams wrote:

> http://www.nehta.gov.au/component/docman/doc_download/708-qualified-certificate-reference-v11-draft-2009-05-07

from the spec:

[[
A QCR allows clients to obtain an X.509 certificate, which in
turn will be used to secure messages, especially for Web services request and
response.

[snip]

This document only covers identifying parties in NEHTA specifications that use
the XML format to represent data. In particular, this includes data in NEHTA
Web services specifications.
]]

The interesting thing is that they think of referring to PEM files, the weird thing is that they have a bunch of URLs for different protocol types it seems

   http://ns.nehta.gov.au/Qcr/Ref/Http/1.0

is for certificate types which one can get using HTTP

  http://www.healthcare.com.au/pki/clinic234.cer

and
  
  http://ns.nehta.gov.au/Qcr/Ref/Ldap/1.0

is for certificates which one can get using ldap

  ldap://ldap.healthcare.com.au:6666/cn=RP%20gp2%20org%20
:2330726155,ou=
RP%20gp2%20org,o=RP%20gp2%20org,l=TUGGERANONG,st=ACT,c=AU

This looks like over the top modelling to me, something that
often happens - and in the semweb space too - to beginners.

	Henry


Social Web Architect
http://bblfish.net/
Received on Tuesday, 8 February 2011 16:48:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:22 UTC