Recommendations to golfml spec.

17 views
Skip to first unread message

Dean Forant

unread,
Mar 26, 2015, 1:53:51 AM3/26/15
to golf-marku...@googlegroups.com
Hi all,

First off I would like to say that I'm currently working on a .NET MVC project that is going to incorporate the golfml specification.

During my model creation phase of my development I did notice that in the address element there is only one street element. This is fine for actual single family dwellings but in the case of apartments its not uncommon to have either another field called address2 or apartment number. 

I'm not sure what the process is for making any recommendations for changes in the specification but I would like to suggest that there be an additional element in the address element that holds an apartment number (in the cases where the address element is being used in the player element of golfml.

Thanks,
Dean

GolfML

unread,
Mar 26, 2015, 1:56:30 AM3/26/15
to golf-marku...@googlegroups.com
Thank you for your interest in the Golf Markup Language.

Google recently sent an end-of-service notice to google code users.

I migrated the whole project on github.

I just performed an automatic migration of the whole project, but it needs a little clean-up and restructuring to fit github’s requirement.

I suggest we continue this conversation at github.

Best regards,

Pierre

--
You received this message because you are subscribed to the Google Groups "Golf Markup Language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golf-markup-lang...@googlegroups.com.
To post to this group, send email to golf-marku...@googlegroups.com.
Visit this group at http://groups.google.com/group/golf-markup-language.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages