search

leodido / go-urn

Parser for uniform resource names as seen on RFC 8141, RFC 2141, and RFC 7643
MIT License
88 stars 11 forks source link

Remove param from SCIM types #43

Open t2y opened 10 months ago

t2y commented 10 months ago

According to https://datatracker.ietf.org/doc/html/rfc7643#section-10.2.1, there is no param in the type definition.

 type
    The entity type, which is either "schemas" or "api".
t2y commented 10 months ago

Oh, I didn't notice that statement. It indicates that param might be added in the future. However, I couldn't find a real URN example including urn:ietf:params:scim:param when I tried to write a test code to parse it.

Either one of these is incorrect, I guess. Should we call for a report to the SCIM WG?

 type
    The entity type, which is either "schemas" or "api".
  Namespaces with type "api" (e.g., "urn:ietf:params:scim:api") and
  "param" (e.g., "urn:ietf:params:scim:param") are reserved for
  IETF-approved SCIM specifications.

Of course, you can reject this PR until the specification is clarified.

leodido commented 10 months ago

Either one of these is incorrect, I guess. Should we call for a report to the SCIM WG?

I guess that would be the best thing to do.

Of course, you can reject this PR until the specification is clarified.

No need to. We can keep it open till more clear info emerges!