>>>>> "Cantor," == Cantor, Scott E <[email protected]> writes:

    >> I think the plan was to add a new API as the existing APIs have
    >> shipped.  So, get_name_attribute_issuer.  The problem there is
    >> how to handle multi-valued name attributes with different
    >> issuers.

    Cantor,> I think I'd want to see a new type created to represent a
    Cantor,> handle to a specific name attribute, and then the ability
    Cantor,> to get those handles, and pass them back into new APIs for
    Cantor,> getting values, metadata, etc.

    Cantor,> IOW, I don't think the current APIs are right to reference
    Cantor,> them by name only, and I'd deprecate them in favor of
    Cantor,> getting it right. The old ones would still work as is, just
    Cantor,> without the ability to make such distinctions.

I'm fine with this plan for the future.  However if we're going to do
that we should publish the existing naming exts document roughly as-is
so people have something to work with while we futz.

(I note we're kind of in the wrong WG for this discussion.)
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab

Reply via email to