shibboleth-dev - entityID (or providerId)
Subject: Shibboleth Developers
List archive
- From: Tom Scavo <>
- To: Shibboleth Development <>
- Subject: entityID (or providerId)
- Date: Thu, 23 Jun 2005 09:23:34 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=q0yI1Rrq2yjN4MwbwCeXw6IRwBNjgOJrnck+FPlYz7iRaSIWQ3EiTKdRqiocSHR/h+nz+aQPy9rYxsnMFTtmpqxFfTQZaG1PHi9ygCCrWu3aViylGvri7tVNSFrRz0H4yRpPnnGRxA+gb1hV7tUkbZXXcbCxfsEzqUutuT7HhWs=
Quote of the Day:
a good URI...works as both a persistent name and an available location.
So, a URL is really just a URI with practical utility.
See:
Untangle URIs, URLs, and URNs: Naming and the problem of persistence
http://www-128.ibm.com/developerworks/xml/library/x-urlni.html
Also, I think we should start using the term "entityID" rather than
"providerId" in our documentation and writing. As Howard has pointed
out, the latter is hopelessly overloaded.
Cheers,
Tom
- entityID (or providerId), Tom Scavo, 06/23/2005
- Re: entityID (or providerId), Nate Klingenstein, 06/23/2005
- Re: entityID (or providerId), Tom Scavo, 06/23/2005
- RE: entityID (or providerId), Scott Cantor, 06/23/2005
- Re: entityID (or providerId), Tom Scavo, 06/23/2005
- RE: entityID (or providerId), Scott Cantor, 06/23/2005
- Re: entityID (or providerId), Tom Scavo, 06/23/2005
- RE: entityID (or providerId), Scott Cantor, 06/23/2005
- Re: entityID (or providerId), Tom Scavo, 06/23/2005
- Re: entityID (or providerId), Nate Klingenstein, 06/23/2005
Archive powered by MHonArc 2.6.16.