one of the things the IETF does that i find interesting is the use of varying "Trees" in registering their media type documents[1].
Standard
Vendor
Personal
also noting that people made up their own "X" facet, too.
some of our name conflict issues might be easier to deal with if we established something similar(just imagining here). either some part of the URI that does this (e.g. path: /STND/, /VND/, /PRS/) -- i don't really like this, BTW just asking.
maybe we can leverage community culture like the IANA link-rel vs microformats, vs. some local definition that is not reg'd for lin-rel values? IOW, the community "assumes" the IANA-reg'd value is "more official" and stable than the others.
just want to make sure we give this a thought as we set out on the path to managing a registry.
one of the things the IETF does that i find interesting is the use of varying "Trees" in registering their media type documents[1].
also noting that people made up their own "X" facet, too.
some of our name conflict issues might be easier to deal with if we established something similar(just imagining here). either some part of the URI that does this (e.g. path: /STND/, /VND/, /PRS/) -- i don't really like this, BTW just asking.
maybe we can leverage community culture like the IANA link-rel vs microformats, vs. some local definition that is not reg'd for lin-rel values? IOW, the community "assumes" the IANA-reg'd value is "more official" and stable than the others.
just want to make sure we give this a thought as we set out on the path to managing a registry.
[1] https://tools.ietf.org/html/rfc6838#section-3