This is very problem-dependent, but if the most likely use of the data is for positions to be plotted on a map (rather than, for example, sending mail to those places) then the data should be given as positions, rather than street addresses. This way they are unambiguous, wheras addresses may change over time, and the locations that correspond to them may depend on what lookup tool is used to convert addresses to locations.
If you're giving location data, then the most important thing is not the exact format that you give it in, but that it is clear what the format is. Coordinates should be accompanied by metadata explaining what the coordinate system is. For example,
If using lat/lon, you should ideally note what geoid is referred to
(usually WGS84 these days, since that's what GPS uses, but best to
specify if you know).
If it's something more complicated (e.g. UTM
coordinates) then that needs to be clear and the appropriate metadata
If vertical elevations are given, it's important to know
what datum is used (i.e. where is zero elevation).
With regard to your specific dataset (and without knowing the details of the likely uses) I would recommend giving position data rather than address data, and (less importantly) expressing that in degrees rather than degrees / minutes / seconds, because in many cases it will be easier for software to parse.
This post has been migrated from the Open Science private beta at StackExchange (A51.SE)