Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Contact type int optional #4

Closed
jbarbede opened this issue Apr 21, 2015 · 5 comments
Closed

Contact type int optional #4

jbarbede opened this issue Apr 21, 2015 · 5 comments
Assignees
@lifeofguenter
Labels
enhancement
Milestone
0.1.4

Comments

@jbarbede
Copy link
Contributor

Nic MX only accepts "loc" type for "contact:postalInfo" and doesn't support "int" type.

Actually "int" type is always added in ContactTrait, we probably need some configuration option to indicate what type(s) should be part of the generated frame.
@lifeofguenter
Copy link
Member

Agree, I checked the RFC and this is a optional feature

Question: does MX require the type=loc attribute? Or as in the example here: http://tools.ietf.org/html/rfc5733#section-3.2.1 without?

@lifeofguenter lifeofguenter added this to the 0.1.4 milestone Apr 21, 2015
@lifeofguenter lifeofguenter self-assigned this Apr 21, 2015
@jbarbede
Copy link
Contributor Author

Yes, MX requires type=loc.

@lifeofguenter
Copy link
Member

Do you have a link to documentation? That would help a lot. Thanks.

@jbarbede
Copy link
Contributor Author

Sent it to your Github email :-).

@lifeofguenter
Copy link
Member

Please check if works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lifeofguenter lifeofguenter

Labels
enhancement
Projects
None yet
Milestone
0.1.4
Development

No branches or pull requests
2 participants
@lifeofguenter @jbarbede