--On Friday, July 11, 2003 11:48 AM -0600 Lyndon Nerenberg <[EMAIL PROTECTED]> wrote:
|> I would like to see Alexey's document recommend a best practice for |> naming of keywords in the 'private' area to avoid namespace problems: |> specifically a 'vendor.productid.xxx' convention. I'm already using |> that format for the keywords that Mulberry uses to avoid any namespace |> clash issues. If we want to formalise this we could allow IANA |> registration of the vendor tokens using the ACAP registry (that's what |> the ANNOTATE extensions do). | | I think we need to handle this a bit differently. We should publish one | document that: | | 1) reserves the $* flag namespace | 2) creates an IANA registry for flags in the $* namespace | 3) defines a policy for registering flags in the $* namespace | | The document will not itself define any $* flags. | | The document would reserve $vendor.* as described above for private | registrations. Registration of any $* flags that are not $vendor.* flags | would be by RFC. | | Alexey's document would then create the initial set of flags in the new | registry. | | Make sense? If so, I'll put together a draft to create the flag registry.
My only concern is with the length of the keywords for the $vendor.vend. space (c.f. lemonade issues). Why not just have anything without $ being in the vendor space? Or pick another character at the start, e.g. '%' and say that corresponds to a registered vendor space, without having to have 'vendor' at the start of the keyword.
-- Cyrus Daboo
