Agent Information

[RegMellon]

For applications that are broker specific and not agent specific, having access to the agent information is important also. Consideration should be made for passing agent email address in the meta data fields.

Really any information that could be retrieved by parsing values from the raw email should be available in the metadata tags, or else some systems will have to fall back on parsing entire emails to retrieve all the information they need which leads to the same problems that this spec is trying to avoid.

[EBashkoff]

V1.0 of the spec allows for the addition of any custom fields that you would like to add to the data set. For example, you could add:

        <meta name="lead_agent_name"   content="John Agent" />
        <meta name="lead_agent_email"  content="[email protected]" />
        <meta name="lead_agent_phone"  content="555-555-1212" />

This type of requirement (that is, to add agent information) may be somewhat application specific, so I am not sure that it makes sense to add a "standard" hard-coded field having to do with agents to the primary list of fields. However, this is a good suggestion and more discussion is welcome!

[RegMellon]

I guess the mail problem is that the information is in the email but not in the meta tags. For example realtor.com usually sends the email to an agent and can CC the brokerage.

All information that is contained in the email needs to be in the meta tags to convert code into simply using the meta tags. If it is not in the tags then traditional parsing still needs to be at least partially used. Which in turn means you still have all the drawbacks of traditional parsing, so why move over to meta tags at all?