We need to agree on how to represent places in our activity stream spec. Currently we only have this: http://martin.atkins.me.uk/specs/activitystreams/activityschema#anchor14 

Places are important because: 

Actors do activities at places: Monica wrote a blog "The Ocean" at "Malibu Beach"

There are lots of activities which involve places:

• Check in to a place: Jim checked into "21st Ammendment"  
• Rate/Review a place: Chris gave "Amber India" 4 out of 5 stars
• Tag a place in a photo: John tagged "Gates Computer Science Building" in this photo
• Go to an event in a place: Martin decided to attend "American Labor Day" at "Dave Recordon's House"
• Achievement related activities: Rob hiked "Mount Rainier", jsenior is major of "Noddle Ranch"

A place has the following properties

• Name: 21st Ammendment
• Website: http://www.21st-amendment.com/
  • Alternate web pages for the place can be listed as well
• Address:  
  • Human Redable Address or Formatted Address
  • Address Fields split out
  • Geo Coordinates:
    • Lat
    • Long

So I recommend we use object notation where the

1. name is the atom:title,
2. Website of the place <link rel="alternate" type="text/html"
3. For the address I propose we use the OpenSocial namespace and elements

• http://portablecontacts.net/draft-spec.html#address_element --> What is the namespace? No lat or long
• http://microformats.org/wiki/adr --> microformat so need xcal but its nice we get all the events elements like dtStart and dtEnd
  • Namespace =urn:ietf:params:xml:ns:xcal
• http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/REST-API.html#addressElement
  • Most complete covers all Poco fields
  • Namespace=http://ns.opensocial.org/2008/opensocial