Final: OpenID Attribute Exchange 1.0 – Final : 3.1 , 3.2, 3.3 : 俺約/メモ


3.1.  Subject Identifier (サブジェクト識別子)

An identifier for a set of attributes. It MUST be a URI. The subject identifier corresponds to the end-user identifier in the authentication portion of the messages. In other words, the subject of the identity attributes in the attribute exchange part of the message is the same as the end-user in the authentication part. The subject identifier is not included in the attribute exchange.





3.2.  Attribute Type Identifier(属性タイプ識別子)

An attribute type identifier MUST be a URI, which is used for referring to property values. (属性タイプはURIで、プロパティ値を示すために使う。)

If an attribute type identifier URI can be resolved then it MAY be dereferenced to retrieve a description of the property. OpenID Providers can use the metadata obtained through dereferencing new or unknown attribute types to dynamically assist the user in providing the attribute.



This provides for flexibility and extensibility. Flexibility in that both URNs and URLs can be used to refer to property values. Extensibility allows any individual site, or consortium of sites, to define their own attribute types with agreements on the syntax and semantics of their associated attribute values.


[OpenID.axschema] (Hardt, D., “Schema for OpenID Attribute Exchange,” May 2007.) outlines an example method of defining new attribute type URIs, and also provides a set of attribute types with their associated metadata schema and data formats.


3.3.  Attribute Value(属性値)

A attribute value MUST be a UTF-8 (Yergeau, F., “UTF-8, a transformation format of ISO 10646,” November 2003.) [RFC3629] string. In order to comply with the data formats defined by the underlying [OpenID.authentication‑2.0] (, “OpenID Authentication 2.0 – Final,” August 2007.) protocol, attribute values MUST NOT contain newlines (UCS codepoint 10, "\n").

(UTF-8。 改行(\n)を含んではいけません)

OpenID Attribute Exchange can be used to transfer any kind of data. If the data contains newlines, is not a UTF-8 string or it is so desired by the parties transferring the data, the data MUST be encoded to a UTF-8 string without newlines.


3.3.1.  Attribute-Specific Encodings (属性固有のエンコーディング)

Attribute-specific encodings can be defined using the attribute metadata descriptions and may be applied by the protocol layer above OpenID Attribute Exchange.

Optionally, attribute-specific encodings may use language tags [OpenID.value‑lang‑1.0] (Wahl, M., “Language Tags for OpenID Values,” April 2007.) for localization.


Final: OpenID Attribute Exchange 1.0 – Final

カテゴリー: 未分類 パーマリンク


以下に詳細を記入するか、アイコンをクリックしてログインしてください。 ロゴ アカウントを使ってコメントしています。 ログアウト /  変更 )

Google+ フォト

Google+ アカウントを使ってコメントしています。 ログアウト /  変更 )

Twitter 画像

Twitter アカウントを使ってコメントしています。 ログアウト /  変更 )

Facebook の写真

Facebook アカウントを使ってコメントしています。 ログアウト /  変更 )


%s と連携中