<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
openid/sharedsignals event <br>
<br>
Issue opened <br>
Issue Title: Provide Guidance and Examples for Edge Cases in Complex Subject Matching
<br>
https://github.com/openid/sharedsignals/issues/282 <br>
<br>
Section 8.1.3.1 (Subject Matching) defines rules for matching Complex Subjects, stating that two subjects match if all fields are undefined or identical. However, it lacks guidance on edge cases, such as nested Complex Subjects or fields with multiple values
(e.g., `ip-addresses`). This could lead to inconsistent matching logic. **Nested Complex Subjects** _Subject 1:_ { "format": "complex", "tenant": { "format": "opaque", "id": "example-a38h4792-uw2" }, "user": { "format": "complex", "email": { "format": "email",
"email": "jdoe@example.com" } } } _Subject 2:_ { "format": "complex", "tenant": { "format": "opaque", "id": "example-a38h4792-uw2" }, "user": { "format": "complex", "email": { "format": "email", "email": "jdoe@example.com" }, "role": { "format": "opaque",
"id": "admin" } } } **IP Address:** _Subject 1:_ { "format": "complex", "device": { "format": "ip-addresses", "ip-addresses": ["10.29.37.75", "10.29.37.76"] } } _Subject 2:_ { "format": "complex", "device": { "format": "ip-addresses", "ip-addresses": ["10.29.37.75"]
} }
</body>
</html>