Hi,
On Mon, Aug 11, 2014 at 09:43:21PM -0700, Ned Freed wrote:
I am concerned that there are close to an infinite number of such
headers that might be requested, some neutral, some potentially of some
concern, but there is not the bandwidth to make them all RFCs.
I accept this point without any argument. This draft shows the use case I
was looking at, but I didn't think that this would ever become an RFC as it
is. It was published as an ID to solicit comments, and it has achieved its
goal.
I am not sure what others exist, but if there is not yet one for
hamradio there will be a request as soon as I get back from vacation.
As far as radio goes, if you're referring to callsign, I think this belongs
either in the from field as part of the name string. If you mean radio club,
then I would say that it fits nicely with the "Affiliation:" field described
below.
Then I am sure there will be requests for pretty much every social
grouping and identity.
This is definitely not my intention. I am aiming for a generic approach.
Like, say, an Affiliation: field? Whose value can have multiple levels on a
par
with the Organization/Organizational Unit structure you find in LDAP or X.500
directories? And which can appear more than once if you're a joiner like Snug?
This has been the best suggestion, and most popular.
The key is to seperate it from the Organisation: header's usage (even though
technically it shouldn't be appearing in mail).
The Organisation: header suggests (according to a quick poll of e-mail users
I've spoken to) that you represent the organisation. This is not the case
when it comes to a hackerspace (or radio club). You simply want to show that
you're a member of the group.
I suppose you could then have a FCFS value registry if you felt like there's
some need to have at least some pain assocated with this idea. Or better
yet, don't.
This would go too far and be outside the scope of what I'm aiming for.
So, taking things into consideration, I will be working on a new draft that
aims to do the following:
* Look at current use of the Organisation: header and formalise its usage
in the message header registry
* Introduce an Affiliation: header and formalise its usage in the message
header registry
* Suggest a format for the string that may be used that includes both a
name and a URL that can be used to identify the organisation
* Suggest that the URL MAY contain some semantic web (RDFa or similar)
resources that can tell you more about the organisation but that the way
that that would be done is outside the scope of the document
The reason I would only suggest a format for the string used is that
Organisation headers are already in use and it would be unrealistic to ask
everyone to switch to using a specific format.
Thanks,
Iain.
--
e: irl(_at_)fsfe(_dot_)org w: iain.learmonth.me
x: irl(_at_)jabber(_dot_)fsfe(_dot_)org t: +447875886930
c: MM6MVQ g: IO87we
p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49
pgpIsMcl_z6qT.pgp
Description: PGP signature