text:
Memorial Day Weekend Means AIS Inspections
The Memorial Day Weekend is the first busy boating weekend of the year and Wyoming Game and fish Aquatic Invasive Species (AIS) inspectors will have inspection crews at Wyoming's most popular waters
E-Filing Campaign Reports Workshops Available
The Wyoming Secretary of State's Office will conduct regional workshops aimed at assisting state candidates, candidate committees, political action committees, organizations, and political parties with e-filing their campaign finance disclosure reports.
The workshops will be offered at seven locations around the state from June 6 to June 20. State Election's Director Peggy Nighswonger says the goal in offering regional hands-on training is to ensure that everyone understands the legal requirements of campaign finance reporting and how easily and efficiently people can file online.
Gov. Mead Appoints Task Force
Drought Conditions Cut Riverton's Water Supply [AUDIO]
Riverton's water supply is being cut by nearly 40 percent because of drought conditions. Doug Randall reports. Charges are pending against several individuals after Wyoming Game and Fish Department game wardens conducted increased law enforcement efforts on southwest Wyoming crucial big game winter ranges, before the May 1st antler season opener. Click past the jump to listen to Wyoming Radio News.
Patrol Joins Seatbelt Enforcement Campaign
The Wyoming Highway Patrol will be participating in the national "Click it or Ticket May Mobilization" campaign to step up enforcement in the area of seat belt use. Wyoming Hi
Luke Martinez to Speak At Reservation Schools
University of Wyoming men's basketball student-athlete Luke Martinez has been invited by the Northern Arapaho Tribal Education Department to speak at two schools on the Wind River Reservation this weekend.
LCCC Seeking Public Comments Ahead of Evaluation
Laramie County Community College is seeking comments from the public about the college in preparation for its periodic evaluation by its regional accrediting agency. The college will host a visit July 18-20, with a team representing the Higher Learning Commission of the North Central Association.
Wyoming Short Film Contest Winner
A short film by Preston Randolph called "The Summer of 81," filmed near Meeteetse, Wyoming is the winner of this year's Wyoming Short Film Contest. The short tells the story of Wyoming man, Bob Taylor and the spirit and struggles of his life's journey. From teaching in the city, to being a Cowboy in Wyoming, to raising his family without electricity in the cabin he built by hand, and of course baseball.
Law Enforcement Memorial & Parade Set for Saturday
The Cheyenne Police Department will join the Laramie County Sheriff's Department, the Wyoming Highway Patrol and the USAF/90th Security Forces Group from FE Warren AFB this Saturday to honor all Wyoming Peace Officers who have died in the line of duty...
Powwows And Rodeo's This Spring in Wind River Country
Native American powwows and rodeos are among some of the offerings around Wind River Country this May & June.
In June, there are weekly cultural programs of authentic Indian Dance and Storytelling Exhibitions (Northern Arapaho Cultural Experience) providing special insights to the Arapaho way of life.
WHP Trooper Helps Mom Save Her Two Kids
On April 25th just after 7:00 p.m. Wyoming Highway Patrol Trooper William Kirkman was patrolling south of Casper when he overheard a radio dispatch of an ATV crash on the Ratter Q Ranch which is located on WYO 487 approximately 23 miles south of Casper.
Cheyenne Officer To Represent Wyoming At Special Olympics World Games
Officer Zachary Johnson of the Cheyenne Police Department was selected to represent Special Olympics Wyoming and the Law Enforcement Torch Run (LETR) at the Special Olympic World Winter Games in PyeongChang, South Korea in January of 2013.
Johnson was selected to the Global Law Enforcement Torch Run Final Leg Team after being nominated by Special Olympics Wyoming staff and LETR co-directors.


text:
Video Series: Our Team
Health Topics: General Health and Pediatrics
Children's National Health System's Kathy Woodward, MD, shares her insight on how adolescents can use long acting reversible contraceptives to avoid unintended pregnancy.For more information, go to: www.childrensnational.org
Invest in future cures for some of life's most devastating diseases
Run or walk with us on October 3rd and help local kids!
In this video, Kathy Woodward, MD, shares her insight on how adolescents can use long-acting reversible contraceptives to avoid unintended pregnancy, specifically the single implant rod and intra-uterine device.
The Adolescent Medicine Program at Children's National Health System/George Washington University is approved by ACGME and involves clinical, academic and research training.

subset: commoncrawl


text:
|Network Working Group
|M. Nottingham, Editor
|Request for Comments: 4287
|R. Sayre, Editor
|Category: Standards Track
|December 2005
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright © The Internet Society (2005). All Rights Reserved.
This document specifies Atom, an XML-based Web content and metadata syndication format.
Atom is an XML-based document format that describes lists of related information known as "feeds". Feeds are composed of a number of items, known as "entries", each with an extensible set of attached metadata. For example, each entry has a title.¶
The primary use case that Atom addresses is the syndication of Web content such as weblogs and news headlines to Web sites as well as directly to user agents.¶
A brief, single-entry Atom Feed Document:
<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> <title>Example Feed</title> <link href="http://example.org/"/> <updated>2003-12-13T18:30:02Z</updated> <author> <name>John Doe</name> </author> <id>urn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6</id> <entry> <title>Atom-Powered Robots Run Amok</title> <link href="http://example.org/2003/12/13/atom03"/> <id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id> <updated>2003-12-13T18:30:02Z</updated> Some text. </entry> </feed>
A more extensive, single-entry Atom Feed Document:
<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> <title type="text">dive into mark</title> <subtitle type="html"> A lot of effort went into making this effortless </subtitle> <updated>2005-07-31T12:29:29Z</updated> <id>tag:example.org,2003:3</id> <link rel="alternate" type="text/html" hreflang="en" href="http://example.org/"/> <link rel="self" type="application/atom+xml" href="http://example.org/feed.atom"/> <rights>Copyright (c) 2003, Mark Pilgrim</rights> <generator uri="http://www.example.com/" version="1.0"> Example Toolkit </generator> <entry> <title>Atom draft-07 snapshot</title> <link rel="alternate" type="text/html" href="http://example.org/2005/04/02/atom"/> <link rel="enclosure" type="audio/mpeg" length="1337" href="http://example.org/audio/ph34r_my_podcast.mp3"/> <id>tag:example.org,2003:3.2397</id> <updated>2005-07-31T12:29:29Z</updated> <published>2003-12-13T08:29:29-04:00</published> <author> <name>Mark Pilgrim</name> <uri>http://example.org/</uri> <email>firstname.lastname@example.com</email> </author> <contributor> <name>Sam Ruby</name> </contributor> <contributor> <name>Joe Gregorio</name> </contributor> <content type="xhtml" xml:lang="en" xml:base="http://diveintomark.org/">

[Update: The Atom draft is finished.]

 </content> </entry> </feed>
The XML Namespaces URI [W3C.REC-xml-names-19990114] for the XML data format described in this specification is:¶
For convenience, this data format may be referred to as "Atom 1.0". This specification uses "Atom" internally.¶
This specification describes conformance in terms of two artifacts: Atom Feed Documents and Atom Entry Documents. Additionally, it places some requirements on Atom Processors.¶
This specification uses the namespace prefix "atom:" for the Namespace URI identified in Section 1.2, above. Note that the choice of namespace prefix is arbitrary and not semantically significant.¶
Atom is specified using terms from the XML Infoset [W3C.REC-xml-infoset-20040204]. However, this specification uses a shorthand for two common terms: the phrase "Information Item" is omitted when naming Element Information Items and Attribute Information Items. Therefore, when this specification uses the term "element," it is referring to an Element Information Item in Infoset terms. Likewise, when it uses the term "attribute," it is referring to an Attribute Information Item.¶
Some sections of this specification are illustrated with fragments of a non-normative RELAX NG Compact schema [RELAX-NG]. However, the text of this specification provides the definition of conformance. A complete schema appears in Appendix B.¶
This specification describes two kinds of Atom Documents: Atom Feed Documents and Atom Entry Documents.¶
An Atom Feed Document is a representation of an Atom feed, including metadata about the feed, and some or all of the entries associated with it. Its root is the atom:feed element.¶
An Atom Entry Document represents exactly one Atom entry, outside of the context of an Atom feed. Its root is the atom:entry element.¶
Both kinds of Atom Documents are specified in terms of the XML Information Set, serialized as XML 1.0 [W3C.REC-xml-20040204] and identified with the "application/atom+xml" media type. Atom Documents MUST be well-formed XML. This specification does not define a DTD for Atom Documents, and hence does not require them to be valid (in the sense used by XML).¶
Atom allows the use of IRIs [RFC3987]. Every URI [RFC3986] is also an IRI, so a URI may be used wherever below an IRI is named. There are two special considerations: (1) when an IRI that is not also a URI is given for dereferencing, it MUST be mapped to a URI using the steps in Section 3.1 of [RFC3987] and (2) when an IRI is serving as an atom:id value, it MUST NOT be so mapped, so that the comparison works as described in Section 220.127.116.11.¶
Any element defined by this specification MAY have an xml:base attribute [W3C.REC-xmlbase-20010627]. When xml:base is used in an Atom Document, it serves the function described in Section 5.1.1 of [RFC3986], establishing the base URI (or IRI) for resolving any relative references found within the effective scope of the xml:base attribute.¶
Any element defined by this specification MAY have an xml:lang attribute, whose content indicates the natural language for the element and its descendents. The language context is only significant for elements and attributes declared to be "Language-Sensitive" by this specification. Requirements regarding the content and interpretation of xml:lang are specified in XML 1.0 [W3C.REC-xml-20040204], Section 2.12. ¶
atomCommonAttributes = attribute xml:base { atomUri }?, attribute xml:lang { atomLanguageTag }?, undefinedAttribute*
Atom is an extensible format. See Section 6 of this document for a full description of how Atom Documents can be extended.¶
Atom Processors MAY keep state sourced from Atom Feed Documents and combine them with other Atom Feed Documents, in order to facilitate a contiguous view of the contents of a feed. The manner in which Atom Feed Documents are combined in order to reconstruct a feed (e.g., updating entries and metadata, dealing with missing entries) is out of the scope of this specification.¶
Many of Atom's elements share a few common structures. This section defines those structures and their requirements for convenient reference by the appropriate element definitions.¶
When an element is identified as being a particular kind of construct, it inherits the corresponding requirements from that construct's definition in this section.¶
Note that there MUST NOT be any white space in a Date construct or in any IRI. Some XML-emitting implementations erroneously insert white space around values by default, and such implementations will emit invalid Atom Documents.¶
A Text construct contains human-readable text, usually in small quantities. The content of Text constructs is Language-Sensitive. ¶
atomPlainTextConstruct = atomCommonAttributes, attribute type { "text" | "html" }?, text atomXHTMLTextConstruct = atomCommonAttributes, attribute type { "xhtml" }, xhtmlDiv atomTextConstruct = atomPlainTextConstruct | atomXHTMLTextConstruct
Text constructs MAY have a "type" attribute. When present, the value MUST be one of "text", "html", or "xhtml". If the "type" attribute is not provided, Atom Processors MUST behave as though it were present with a value of "text". Unlike the atom:content element defined in Section 4.1.3, MIME media types [MIMEREG] MUST NOT be used as values for the "type" attribute on Text constructs.¶
Example atom:title with text content: ¶
... <title type="text"> Less: < </title> ...
If the value is "text", the content of the Text construct MUST NOT contain child elements. Such text is intended to be presented to humans in a readable fashion. Thus, Atom Processors MAY collapse white space (including line breaks) and display the text using typographic techniques such as justification and proportional fonts.¶
Example atom:title with HTML content: ¶
... <title type="html"> Less:  <  </title> ...
If the value of "type" is "html", the content of the Text construct MUST NOT contain child elements and SHOULD be suitable for handling as HTML [HTML]. Any markup within MUST be escaped; for example, "
" as "
". HTML markup within SHOULD be such that it could validly appear directly within an HTML
 element, after unescaping. Atom Processors that display such content MAY use that markup to aid in its display.¶
Example atom:title with XHTML content: ¶
... <title type="xhtml" xmlns:xhtml="http://www.w3.org/1999/xhtml"> <xhtml:div> Less: <xhtml:em> < </xhtml:em> </xhtml:div> </title> ...
If the value of "type" is "xhtml", the content of the Text construct MUST be a single XHTML div element [XHTML] and SHOULD be suitable for handling as XHTML. The XHTML div element itself MUST NOT be considered part of the content. Atom Processors that display the content MAY use the markup to aid in displaying it. The escaped versions of characters such as "&" and ">" represent those characters, not markup.
Examples of valid XHTML content: ¶
...
 This is XHTML content.
  ...  <xhtml:div xmlns:xhtml="http://www.w3.org/1999/xhtml"> This is <xhtml:b>XHTML</xhtml:b> content. </xhtml:div>  ...
The following example assumes that the XHTML namespace has been bound to the "xh" prefix earlier in the document: ¶
...  <xh:div> This is <xh:b>XHTML</xh:b> content. </xh:div>  ...
A Person construct is an element that describes a person, corporation, or similar entity (hereafter, 'person'). ¶
atomPersonConstruct = atomCommonAttributes, (element atom:name { text } & element atom:uri { atomUri }? & element atom:email { atomEmailAddress }? & extensionElement*)
This specification assigns no significance to the order of appearance of the child elements in a Person construct. Person constructs allow extension Metadata elements (see Section 6.4).¶
The "atom:email" element's content conveys an e-mail address associated with the person. Person constructs MAY contain an atom:email element, but MUST NOT contain more than one. Its content MUST conform to the "addr-spec" production in [RFC2822].¶
A Date construct is an element whose content MUST conform to the "date-time" production in [RFC3339]. In addition, an uppercase "T" character MUST be used to separate date and time, and an uppercase "Z" character MUST be present in the absence of a numeric time zone offset. ¶
atomDateConstruct = atomCommonAttributes, xsd:dateTime
Such date values happen to be compatible with the following specifications: [ISO.8601.1988], [W3C.NOTE-datetime-19980827], and [W3C.REC-xmlschema-2-20041028].¶
Example Date constructs: ¶
<updated>2003-12-13T18:30:02Z</updated> <updated>2003-12-13T18:30:02.25Z</updated> <updated>2003-12-13T18:30:02+01:00</updated> <updated>2003-12-13T18:30:02.25+01:00</updated>
Date values SHOULD be as accurate as possible. For example, it would be generally inappropriate for a publishing system to apply the same timestamp to several entries that were published during the course of a single day.¶
The "atom:feed" element is the document (i.e., top-level) element of an Atom Feed Document, acting as a container for metadata and data associated with the feed. Its element children consist of metadata elements followed by zero or more atom:entry child elements. ¶
atomFeed = element atom:feed { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContributor* & atomGenerator? & atomIcon? & atomId & atomLink* & atomLogo? & atomRights? & atomSubtitle? & atomTitle & atomUpdated & extensionElement*), atomEntry* }
This specification assigns no significance to the order of atom:entry elements within the feed.¶
The following child elements are defined by this specification (note that the presence of some of these elements is required):¶
If multiple atom:entry elements with the same atom:id value appear in an Atom Feed Document, they represent the same entry. Their atom:updated timestamps SHOULD be different. If an Atom Feed Document contains multiple entries with the same atom:id, Atom Processors MAY choose to display all of them or some subset of them. One typical behavior would be to display only the entry with the latest atom:updated timestamp.¶
Experience teaches that feeds that contain textual content are in general more useful than those that do not. Some applications (one example is full-text indexers) require a minimum amount of text or (X)HTML to function reliably and predictably. Feed producers should be aware of these issues. It is advisable that each atom:entry element contain a non-empty atom:title element, a non-empty atom:content element when that element is present, and a non-empty atom:summary element when the entry contains no atom:content element. However, the absence of atom:summary is not an error, and Atom Processors MUST NOT fail to function correctly as a consequence of such an absence.¶
The "atom:entry" element represents an individual entry, acting as a container for metadata and data associated with the entry. This element can appear as a child of the atom:feed element, or it can appear as the document (i.e., top-level) element of a stand-alone Atom Entry Document. ¶
atomEntry = element atom:entry { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContent? & atomContributor* & atomId & atomLink* & atomPublished? & atomRights? & atomSource? & atomSummary? & atomTitle & atomUpdated & extensionElement*) }
This specification assigns no significance to the order of appearance of the child elements of atom:entry.¶
The following child elements are defined by this specification (note that it requires the presence of some of these elements):¶
The "atom:content" element either contains or links to the content of the entry. The content of atom:content is Language-Sensitive. ¶
atomInlineTextContent = element atom:content { atomCommonAttributes, attribute type { "text" | "html" }?, (text)* } atomInlineXHTMLContent = element atom:content { atomCommonAttributes, attribute type { "xhtml" }, xhtmlDiv } atomInlineOtherContent = element atom:content { atomCommonAttributes, attribute type { atomMediaType }?, (text|anyElement)* } atomOutOfLineContent = element atom:content { atomCommonAttributes, attribute type { atomMediaType }?, attribute src { atomUri }, empty } atomContent = atomInlineTextContent | atomInlineXHTMLContent | atomInlineOtherContent | atomOutOfLineContent
On the atom:content element, the value of the "type" attribute MAY be one of "text", "html", or "xhtml". Failing that, it MUST conform to the syntax of a MIME media type, but MUST NOT be a composite type (see Section 4.2.6 of [MIMEREG]). If neither the type attribute nor the src attribute is provided, Atom Processors MUST behave as though the type attribute were present with a value of "text".¶
atom:content MAY have a "src" attribute, whose value MUST be an IRI reference [RFC3987]. If the "src" attribute is present, atom:content MUST be empty. Atom Processors MAY use the IRI to retrieve the content and MAY choose to ignore remote content or to present it in a different manner than local content.¶
If the "src" attribute is present, the "type" attribute SHOULD be provided and MUST be a MIME media type [MIMEREG], rather than "text", "html", or "xhtml". The value is advisory; that is to say, when the corresponding URI (mapped from an IRI, if necessary) is dereferenced, if the server providing that content also provides a media type, the server-provided media type is authoritative.¶
Atom Documents MUST conform to the following rules. Atom Processors MUST interpret atom:content according to the first applicable rule.¶
XHTML inline:¶
... <content type="xhtml">
 This is XHTML content.
 </content> ... <content type="xhtml"> <xhtml:div xmlns:xhtml="http://www.w3.org/1999/xhtml"> This is <xhtml:b>XHTML</xhtml:b> content. </xhtml:div> </content> ...
The following example assumes that the XHTML namespace has been bound to the "xh" prefix earlier in the document: ¶
... <content type="xhtml"> <xh:div> This is <xh:b>XHTML</xh:b> content. </xh:div> </content> ...
The "atom:category" element conveys information about a category associated with an entry or feed. This specification assigns no meaning to the content (if any) of this element. ¶
atomCategory = element atom:category { atomCommonAttributes, attribute term { text }, attribute scheme { atomUri }?, attribute label { text }?, undefinedContent }
The "term" attribute is a string that identifies the category to which the entry or feed belongs. Category elements MUST have a "term" attribute.¶
The "scheme" attribute is an IRI that identifies a categorization scheme. Category elements MAY have a "scheme" attribute.¶
The "label" attribute provides a human-readable label for display in end-user applications. The content of the "label" attribute is Language-Sensitive. Entities such as "&" and "<" represent their corresponding characters ("&" and "<", respectively), not markup. Category elements MAY have a "label" attribute.¶
The "atom:contributor" element is a Person construct that indicates a person or other entity who contributed to the entry or feed. ¶
atomContributor = element atom:contributor { atomPersonConstruct }
The "atom:generator" element's content identifies the agent used to generate a feed, for debugging and other purposes. ¶
atomGenerator = element atom:generator { atomCommonAttributes, attribute uri { atomUri }?, attribute version { text }?, text }
The content of this element, when present, MUST be a string that is a human-readable name for the generating agent. Entities such as "&" and "<" represent their corresponding characters ("&" and "<" respectively), not markup.¶
The atom:generator element MAY have a "uri" attribute whose value MUST be an IRI reference [RFC3987]. When dereferenced, the resulting URI (mapped from an IRI, if necessary) SHOULD produce a representation that is relevant to that agent.¶
The atom:generator element MAY have a "version" attribute that indicates the version of the generating agent.¶
The "atom:icon" element's content is an IRI reference [RFC3987] that identifies an image that provides iconic visual identification for a feed. ¶
atomIcon = element atom:icon { atomCommonAttributes, (atomUri) }
The image SHOULD have an aspect ratio of one (horizontal) to one (vertical) and SHOULD be suitable for presentation at a small size.¶
The "atom:id" element conveys a permanent, universally unique identifier for an entry or feed. ¶
atomId = element atom:id { atomCommonAttributes, (atomUri) }
Its content MUST be an IRI, as defined by [RFC3987]. Note that the definition of "IRI" excludes relative references. Though the IRI might use a dereferencable scheme, Atom Processors MUST NOT assume it can be dereferenced.¶
When an Atom Document is relocated, migrated, syndicated, republished, exported, or imported, the content of its atom:id element MUST NOT change. Put another way, an atom:id element pertains to all instantiations of a particular Atom entry or feed; revisions retain the same content in their atom:id elements. It is suggested that the atom:id element be stored along with the associated resource.¶
Because of the risk of confusion between IRIs that would be equivalent if they were mapped to URIs and dereferenced, the following normalization strategy SHOULD be applied when generating atom:id elements:¶
Instances of atom:id elements can be compared to determine whether an entry or feed is the same as one seen before. Processors MUST compare atom:id elements on a character-by-character basis (in a case-sensitive fashion). Comparison operations MUST be based solely on the IRI character strings and MUST NOT rely on dereferencing the IRIs or URIs mapped from them.¶
As a result, two IRIs that resolve to the same resource but are not character-for-character identical will be considered different for the purposes of identifier comparison.¶
For example, these are four distinct identifiers, despite the fact that they differ only in case:¶
Likewise, these are three distinct identifiers, because IRI %-escaping is significant for the purposes of comparison:¶
The "atom:link" element defines a reference from an entry or feed to a Web resource. This specification assigns no meaning to the content (if any) of this element. ¶
atomLink = element atom:link { atomCommonAttributes, attribute href { atomUri }, attribute rel { atomNCName | atomUri }?, attribute type { atomMediaType }?, attribute hreflang { atomLanguageTag }?, attribute title { text }?, attribute length { text }?, undefinedContent }
atom:link elements MAY have a "rel" attribute that indicates the link relation type. If the "rel" attribute is not present, the link element MUST be interpreted as if the link relation type is "alternate".¶
The value of "rel" MUST be a string that is non-empty and matches either the "isegment-nz-nc" or the "IRI" production in [RFC3987]. Note that use of a relative reference other than a simple name is not allowed. If a name is given, implementations MUST consider the link relation type equivalent to the same name registered within the IANA Registry of Link Relations (Section 7), and thus to the IRI that would be obtained by appending the value of the rel attribute to the string "http://www.iana.org/assignments/relation/". The value of "rel" describes the meaning of the link, but does not impose any behavioral requirements on Atom Processors.¶
This document defines five initial values for the Registry of Link Relations: ¶
<link rel="related" href="http://search.example.com/"/>An identical link might appear as a child of any atom:entry whose content contains a discussion of that same search engine.
On the link element, the "type" attribute's value is an advisory media type: it is a hint about the type of the representation that is expected to be returned when the value of the href attribute is dereferenced. Note that the type attribute does not override the actual media type returned with the representation. Link elements MAY have a type attribute, whose value MUST conform to the syntax of a MIME media type [MIMEREG].¶
The "title" attribute conveys human-readable information about the link. The content of the "title" attribute is Language-Sensitive. Entities such as "&" and "<" represent their corresponding characters ("&" and "<", respectively), not markup. Link elements MAY have a title attribute.¶
The "length" attribute indicates an advisory length of the linked content in octets; it is a hint about the content length of the representation returned when the IRI in the href attribute is mapped to a URI and dereferenced. Note that the length attribute does not override the actual content length of the representation as reported by the underlying protocol. Link elements MAY have a length attribute.¶
The "atom:logo" element's content is an IRI reference [RFC3987] that identifies an image that provides visual identification for a feed. ¶
atomLogo = element atom:logo { atomCommonAttributes, (atomUri) }
The image SHOULD have an aspect ratio of 2 (horizontal) to 1 (vertical).¶
The "atom:published" element is a Date construct indicating an instant in time associated with an event early in the life cycle of the entry. ¶
atomPublished = element atom:published { atomDateConstruct}
Typically, atom:published will be associated with the initial creation or first availability of the resource.¶
The "atom:rights" element is a Text construct that conveys information about rights held in and over an entry or feed. ¶
atomRights = element atom:rights { atomTextConstruct }
The atom:rights element SHOULD NOT be used to convey machine-readable licensing information.¶
If an atom:entry element does not contain an atom:rights element, then the atom:rights element of the containing atom:feed element, if present, is considered to apply to the entry.¶
If an atom:entry is copied from one feed into another feed, then the source atom:feed's metadata (all child elements of atom:feed other than the atom:entry elements) MAY be preserved within the copied entry by adding an atom:source child element, if it is not already present in the entry, and including some or all of the source feed's Metadata elements as the atom:source element's children. Such metadata SHOULD be preserved if the source atom:feed contains any of the child elements atom:author, atom:contributor, atom:rights, or atom:category and those child elements are not present in the source atom:entry. ¶
atomSource = element atom:source { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContributor* & atomGenerator? & atomIcon? & atomId? & atomLink* & atomLogo? & atomRights? & atomSubtitle? & atomTitle? & atomUpdated? & extensionElement*) }
The atom:source element is designed to allow the aggregation of entries from different feeds while retaining information about an entry's source feed. For this reason, Atom Processors that are performing such aggregation SHOULD include at least the required feed-level Metadata elements (atom:id, atom:title, and atom:updated) in the atom:source element.¶
The "atom:subtitle" element is a Text construct that conveys a human-readable description or subtitle for a feed. ¶
atomSubtitle = element atom:subtitle { atomTextConstruct }
The "atom:summary" element is a Text construct that conveys a short summary, abstract, or excerpt of an entry. ¶
atomSummary = element atom:summary { atomTextConstruct }
It is not advisable for the atom:summary element to duplicate atom:title or atom:content because Atom Processors might assume there is a useful summary when there is none.¶
The "atom:title" element is a Text construct that conveys a human-readable title for an entry or feed. ¶
atomTitle = element atom:title { atomTextConstruct }
The "atom:updated" element is a Date construct indicating the most recent instant in time when an entry or feed was modified in a way the publisher considers significant. Therefore, not all modifications necessarily result in a changed atom:updated value. ¶
atomUpdated = element atom:updated { atomDateConstruct}
Publishers MAY change the value of this element over time.¶
Because Atom is an XML-based format, existing XML security mechanisms can be used to secure its content.¶
Producers of feeds and/or entries, and intermediaries who aggregate feeds and/or entries, may have sound reasons for signing and/or encrypting otherwise-unprotected content. For example, a merchant might digitally sign a message that contains a discount coupon for its products. A bank that uses Atom to deliver customer statements is very likely to want to sign and encrypt those messages to protect their customers' financial information and to assure the customer of their authenticity. Intermediaries may want to encrypt aggregated feeds so that a passive observer cannot tell what topics the recipient is interested in. Of course, many other examples exist as well.¶
The algorithm requirements in this section pertain to the Atom Processor. They require that a recipient, at a minimum, be able to handle messages that use the specified cryptographic algorithms. These requirements do not limit the algorithms that the sender can choose.¶
The root of an Atom Document (i.e., atom:feed in an Atom Feed Document, atom:entry in an Atom Entry Document) or any atom:entry element MAY have an Enveloped Signature, as described by XML-Signature and Syntax Processing [W3C.REC-xmldsig-core-20020212].¶
Atom Processors MUST NOT reject an Atom Document containing such a signature because they are not capable of verifying it; they MUST continue processing and MAY inform the user of their failure to validate the signature.¶
In other words, the presence of an element with the namespace URI "http://www.w3.org/2000/09/xmldsig#" and a local name of "Signature" as a child of the document element MUST NOT cause an Atom Processor to fail merely because of its presence.¶
Other elements in an Atom Document MUST NOT be signed unless their definitions explicitly specify such a capability.¶
Section 6.5.1 of [W3C.REC-xmldsig-core-20020212] requires support for Canonical XML [W3C.REC-xml-c14n-20010315]. However, many implementers do not use it because signed XML documents enclosed in other XML documents have their signatures broken. Thus, Atom Processors that verify signed Atom Documents MUST be able to canonicalize with the exclusive XML canonicalization method identified by the URI "http://www.w3.org/2001/10/xml-exc-c14n#", as specified in Exclusive XML Canonicalization [W3C.REC-xml-exc-c14n-20020718].¶
Intermediaries such as aggregators may need to add an atom:source element to an entry that does not contain its own atom:source element. If such an entry is signed, the addition will break the signature. Thus, a publisher of individually-signed entries should strongly consider adding an atom:source element to those entries before signing them. Implementers should also be aware of the issues concerning the use of markup in the "xml:" namespace as it interacts with canonicalization.¶
Section 4.4.2 of [W3C.REC-xmldsig-core-20020212] requires support for DSA signatures and recommends support for RSA signatures. However, because of the much greater popularity in the market of RSA versus DSA, Atom Processors that verify signed Atom Documents MUST be able to verify RSA signatures, but do not need be able to verify DSA signatures. Due to security issues that can arise if the keying material for message authentication code (MAC) authentication is not handled properly, Atom Documents SHOULD NOT use MACs for signatures.¶
The root of an Atom Document (i.e., atom:feed in an Atom Feed Document, atom:entry in an Atom Entry Document) MAY be encrypted, using the mechanisms described by XML Encryption Syntax and Processing [W3C.REC-xmlenc-core-20021210].¶
Section 5.1 of [W3C.REC-xmlenc-core-20021210] requires support of TripleDES, AES-128, and AES-256. Atom Processors that decrypt Atom Documents MUST be able to decrypt with AES-128 in Cipher Block Chaining (CBC) mode.¶
Encryption based on [W3C.REC-xmlenc-core-20021210] does not ensure integrity of the original document. There are known cryptographic attacks where someone who cannot decrypt a message can still change bits in a way where part or all the decrypted message makes sense but has a different meaning. Thus, Atom Processors that decrypt Atom Documents SHOULD check the integrity of the decrypted document by verifying the hash in the signature (if any) in the document, or by verifying a hash of the document within the document (if any).¶
When an Atom Document is to be both signed and encrypted, it is generally a good idea to first sign the document, then encrypt the signed document. This provides integrity to the base document while encrypting all the information, including the identity of the entity that signed the document. Note that, if MACs are used for authentication, the order MUST be that the document is signed and then encrypted, and not the other way around.¶
This specification describes Atom's XML markup vocabulary. Markup from other vocabularies ("foreign markup") can be used in an Atom Document. Note that the atom:content element is designed to support the inclusion of arbitrary foreign markup.¶
The Atom namespace is reserved for future forward-compatible revisions of Atom. Future versions of this specification could add new elements and attributes to the Atom markup vocabulary. Software written to conform to this version of the specification will not be able to process such markup correctly and, in fact, will not be able to distinguish it from markup error. For the purposes of this discussion, unrecognized markup from the Atom vocabulary will be considered "foreign markup".¶
Atom Processors that encounter foreign markup in a location that is legal according to this specification MUST NOT stop processing or signal an error. It might be the case that the Atom Processor is able to process the foreign markup correctly and does so. Otherwise, such markup is termed "unknown foreign markup".¶
When unknown foreign markup is encountered as a child of atom:entry, atom:feed, or a Person construct, Atom Processors MAY bypass the markup and any textual content and MUST NOT change their behavior as a result of the markup's presence.¶
When unknown foreign markup is encountered in a Text Construct or atom:content element, software SHOULD ignore the markup and process any text content of foreign elements as though the surrounding markup were not present.¶
Atom allows foreign markup anywhere in an Atom document, except where it is explicitly forbidden. Child elements of atom:entry, atom:feed, atom:source, and Person constructs are considered Metadata elements and are described below. Child elements of Person constructs are considered to apply to the construct. The role of other foreign markup is undefined by this specification.¶
A Simple Extension element MUST NOT have any attributes or child elements. The element MAY contain character data or be empty. Simple Extension elements are not Language-Sensitive. ¶
simpleExtensionElement = element * - atom:* { text }
The element can be interpreted as a simple property (or name/value pair) of the parent element that encloses it. The pair consisting of the namespace-URI of the element and the local name of the element can be interpreted as the name of the property. The character data content of the element can be interpreted as the value of the property. If the element is empty, then the property value can be interpreted as an empty string.¶
The root element of a Structured Extension element MUST have at least one attribute or child element. It MAY have attributes, it MAY contain well-formed XML content (including character data), or it MAY be empty. Structured Extension elements are Language-Sensitive. ¶
structuredExtensionElement = element * - atom:* { (attribute * { text }+, (text|anyElement)*) | (attribute * { text }*, (text?, anyElement+, (text|anyElement)*)) }
The structure of a Structured Extension element, including the order of its child elements, could be significant.¶
This specification does not provide an interpretation of a Structured Extension element. The syntax of the XML contained in the element (and an interpretation of how the element relates to its containing element) is defined by the specification of the Atom extension.¶
An Atom Document, when serialized as XML 1.0, can be identified with the following media type:¶
Additional information:¶
This registry is maintained by IANA and initially contains five values: "alternate", "related", "self", "enclosure", and "via". New assignments are subject to IESG Approval, as outlined in [RFC2434]. Requests should be made by email to IANA, which will then forward the request to the IESG, requesting approval. The request should use the following template:¶
Text constructs and atom:content allow the delivery of HTML and XHTML. Many elements in these languages are considered 'unsafe' in that they open clients to one or more types of attack. Implementers of software that processes Atom should carefully consider their handling of every type of element when processing incoming (X)HTML in Atom Documents. See the security sections of [RFC2854] and [HTML] for guidance.¶
Atom Processors should pay particular attention to the security of the IMG, SCRIPT, EMBED, OBJECT, FRAME, FRAMESET, IFRAME, META, and LINK elements, but other elements might also have negative security properties.¶
(X)HTML can either directly contain or indirectly reference executable content.¶
Atom Processors should be aware of the potential for spoofing attacks where the attacker publishes an atom:entry with the atom:id value of an entry from another feed, perhaps with a falsified atom:source element duplicating the atom:id of the other feed. For example, an Atom Processor could suppress display of duplicate entries by displaying only one entry from a set of entries with identical atom:id values. In that situation, the Atom Processor might also take steps to determine whether the entries originated from the same publisher before considering them duplicates.¶
Atom Documents can be encrypted and signed using [W3C.REC-xmlenc-core-20021210] and [W3C.REC-xmldsig-core-20020212], respectively, and are subject to the security considerations implied by their use.¶
Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality.¶
|Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01 Specification", W3C REC REC-html401-19991224, December 1999, <http://www.w3.org/TR/1999/REC-html401-19991224>.
|Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005.
|Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
|Resnick, P., "Internet Message Format", RFC 2822, April 2001.
|Connolly, D. and L. Masinter, "The 'text/html' Media Type", RFC 2854, June 2000.
|Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
|Alvestrand, H., "Tags for the Identification of Languages", BCP 47, RFC 3066, January 2001.
|Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, July 2002.
|Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 3548, July 2003.
|Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
|Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005.
|Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)", W3C REC REC-xml-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-20040204>.
|Boyer, J., "Canonical XML Version 1.0", W3C REC REC-xml-c14n-20010315, March 2001, <http://www.w3.org/TR/2001/REC-xml-c14n-20010315>.
|Eastlake, D., Boyer, J., and J. Reagle, "Exclusive XML Canonicalization Version 1.0", W3C REC REC-xml-exc-c14n-20020718, July 2002, <http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718>.
|Cowan, J. and R. Tobin, "XML Information Set (Second Edition)", W3C REC REC-xml-infoset-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-infoset-20040204>.
|Hollander, D., Bray, T., and A. Layman, "Namespaces in XML", W3C REC REC-xml-names-19990114, January 1999, <http://www.w3.org/TR/1999/REC-xml-names-19990114>.
|Marsh, J., "XML Base", W3C REC REC-xmlbase-20010627, June 2001, <http://www.w3.org/TR/2001/REC-xmlbase-20010627>.
|Solo, D., Reagle, J., and D. Eastlake, "XML-Signature Syntax and Processing", W3C REC REC-xmldsig-core-20020212, February 2002, <http://www.w3.org/TR/2002/REC-xmldsig-core-20020212>.
|Reagle, J. and D. Eastlake, "XML Encryption Syntax and Processing", W3C REC REC-xmlenc-core-20021210, December 2002, <http://www.w3.org/TR/2002/REC-xmlenc-core-20021210>.
|Altheim, M., Boumphrey, F., McCarron, S., Dooley, S., Schnitzenbaumer, S., and T. Wugofski, "Modularization of XHTML™", W3C REC REC-xhtml-modularization-20010410, April 2001, <http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410>.
|International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
|Clark, J., "RELAX NG Compact Syntax", December 2001, <http://www.oasis-open.org/committees/relax-ng/compact-20021121.html>.
|Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
|Wolf, M. and C. Wicksteed, "Date and Time Formats", W3C NOTE NOTE-datetime-19980827, August 1998, <http://www.w3.org/TR/1998/NOTE-datetime-19980827>.
|Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Second Edition", W3C REC REC-xmlschema-2-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
The following people contributed to preliminary versions of this document: Tim Bray, Mark Pilgrim, and Sam Ruby. Norman Walsh provided the Relax NG schema. The content and concepts within are a product of the Atom community and the Atompub Working Group.¶
The Atompub Working Group has dozens of very active contributors who proposed ideas and wording for this document, including:¶
Danny Ayers, James Aylett, Roger Benningfield, Arve Bersvendsen, Tim Bray, Dan Brickley, Thomas Broyer, Robin Cover, Bill de hOra, Martin Duerst, Roy Fielding, Joe Gregorio, Bjoern Hoehrmann, Paul Hoffman, Anne van Kesteren, Brett Lindsley, Dare Obasanjo, David Orchard, Aristotle Pagaltzis, John Panzer, Graham Parks, Dave Pawson, Mark Pilgrim, David Powell, Julian Reschke, Phil Ringnalda, Antone Roundy, Sam Ruby, Eric Scheid, Brent Simmons, Henri Sivonen, Ray Slakinski, James Snell, Henry Story, Asbjorn Ulsberg, Walter Underwood, Norman Walsh, Dave Winer, and Bob Wyman.¶
This appendix is informative.¶
The Relax NG schema explicitly excludes elements in the Atom namespace that are not defined in this revision of the specification. Requirements for Atom Processors encountering such markup are given in Sections 6.2 and 6.3.¶
# -*- rnc -*- # RELAX NG Compact Syntax Grammar for the # Atom Format Specification Version 11 namespace atom = "http://www.w3.org/2005/Atom" namespace xhtml = "http://www.w3.org/1999/xhtml" namespace s = "http://www.ascc.net/xml/schematron" namespace local = "" start = atomFeed | atomEntry # Common attributes atomCommonAttributes = attribute xml:base { atomUri }?, attribute xml:lang { atomLanguageTag }?, undefinedAttribute* # Text Constructs atomPlainTextConstruct = atomCommonAttributes, attribute type { "text" | "html" }?, text atomXHTMLTextConstruct = atomCommonAttributes, attribute type { "xhtml" }, xhtmlDiv atomTextConstruct = atomPlainTextConstruct | atomXHTMLTextConstruct # Person Construct atomPersonConstruct = atomCommonAttributes, (element atom:name { text } & element atom:uri { atomUri }? & element atom:email { atomEmailAddress }? & extensionElement*) # Date Construct atomDateConstruct= atomCommonAttributes, xsd:dateTime # atom:feed atomFeed = [ s:rule [ context = "atom:feed" s:assert [ test = "atom:author or not(atom:entry[not(atom:author)])" "An atom:feed must have an atom:author unless all " ~ "of its atom:entry children have an atom:author." ] ] ] element atom:feed { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContributor* & atomGenerator? & atomIcon? & atomId & atomLink* & atomLogo? & atomRights? & atomSubtitle? & atomTitle & atomUpdated & extensionElement*), atomEntry* } # atom:entry atomEntry = [ s:rule [ context = "atom:entry" s:assert [ test = "atom:link[@rel='alternate'] " ~ "or atom:link[not(@rel)] " ~ "or atom:content" "An atom:entry must have at least one atom:link element " ~ "with a rel attribute of 'alternate' " ~ "or an atom:content." ] ] s:rule [ context = "atom:entry" s:assert [ test = "atom:author or " ~ "../atom:author or atom:source/atom:author" "An atom:entry must have an atom:author " ~ "if its feed does not." ] ] ] element atom:entry { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContent? & atomContributor* & atomId & atomLink* & atomPublished? & atomRights? & atomSource? & atomSummary? & atomTitle & atomUpdated & extensionElement*) } # atom:content atomInlineTextContent = element atom:content { atomCommonAttributes, attribute type { "text" | "html" }?, (text)* } atomInlineXHTMLContent = element atom:content { atomCommonAttributes, attribute type { "xhtml" }, xhtmlDiv } atomInlineOtherContent = element atom:content { atomCommonAttributes, attribute type { atomMediaType }?, (text|anyElement)* } atomOutOfLineContent = element atom:content { atomCommonAttributes, attribute type { atomMediaType }?, attribute src { atomUri }, empty } atomContent = atomInlineTextContent | atomInlineXHTMLContent | atomInlineOtherContent | atomOutOfLineContent # atom:author atomAuthor = element atom:author { atomPersonConstruct } # atom:category atomCategory = element atom:category { atomCommonAttributes, attribute term { text }, attribute scheme { atomUri }?, attribute label { text }?, undefinedContent } # atom:contributor atomContributor = element atom:contributor { atomPersonConstruct } # atom:generator atomGenerator = element atom:generator { atomCommonAttributes, attribute uri { atomUri }?, attribute version { text }?, text } # atom:icon atomIcon = element atom:icon { atomCommonAttributes, (atomUri) } # atom:id atomId = element atom:id { atomCommonAttributes, (atomUri) } # atom:logo atomLogo = element atom:logo { atomCommonAttributes, (atomUri) } # atom:link atomLink = element atom:link { atomCommonAttributes, attribute href { atomUri }, attribute rel { atomNCName | atomUri }?, attribute type { atomMediaType }?, attribute hreflang { atomLanguageTag }?, attribute title { text }?, attribute length { text }?, undefinedContent } # atom:published atomPublished = element atom:published { atomDateConstruct} # atom:rights atomRights = element atom:rights { atomTextConstruct } # atom:source atomSource = element atom:source { atomCommonAttributes, (atomAuthor* & atomCategory* & atomContributor* & atomGenerator? & atomIcon? & atomId? & atomLink* & atomLogo? & atomRights? & atomSubtitle? & atomTitle? & atomUpdated? & extensionElement*) } # atom:subtitle atomSubtitle = element atom:subtitle { atomTextConstruct } # atom:summary atomSummary = element atom:summary { atomTextConstruct } # atom:title atomTitle = element atom:title { atomTextConstruct } # atom:updated atomUpdated = element atom:updated { atomDateConstruct } # Low-level simple types atomNCName = xsd:string { minLength = "1" pattern = "[^:]*" } # Whatever a media type is, it contains at least one slash atomMediaType = xsd:string { pattern = ".+/.+" } # As defined in RFC 3066 atomLanguageTag = xsd:string { pattern = "[A-Za-z]{1,8}(-[A-Za-z0-9]{1,8})*" } # Unconstrained; it's not entirely clear how IRI fit into # xsd:anyURI so let's not try to constrain it here atomUri = text # Whatever an email address is, it contains at least one @ atomEmailAddress = xsd:string { pattern = ".+@.+" } # Simple Extension simpleExtensionElement = element * - atom:* { text } # Structured Extension structuredExtensionElement = element * - atom:* { (attribute * { text }+, (text|anyElement)*) | (attribute * { text }*, (text?, anyElement+, (text|anyElement)*)) } # Other Extensibility extensionElement = simpleExtensionElement | structuredExtensionElement undefinedAttribute = attribute * - (xml:base | xml:lang | local:*) { text } undefinedContent = (text|anyForeignElement)* anyElement = element * { (attribute * { text } | text | anyElement)* } anyForeignElement = element * - atom:* { (attribute * { text } | text | anyElement)* } # XHTML anyXHTML = element xhtml:* { (attribute * { text } | text | anyXHTML)* } xhtmlDiv = element xhtml:div { (attribute * { text } | text | anyXHTML)* } # EOF
Mark Nottingham
EMail: email@example.com
URI: http://www.mnot.net/
Robert Sayre
EMail: firstname.lastname@example.com
URI: http://boswijck.com
Copyright © The Internet Society (2005).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at firstname.lastname@example.com.
Funding for the RFC Editor function is currently provided by the Internet Society.


text:
Google has bought Wildfire Interactive, a social media marketing start-up that provides a platform for organisations to manage all of their social media output on one system.
The software is used to help companies run and measure their social engagement and advertising campaigns across the internet, and integrates with social media websites including Facebook, Twitter, YouTube, Google+, Pinterest and LinkedIn.
Financial terms of the deal were not disclosed. However, according to Reuters, a source has said that the deal is worth close to $250m (£159.9m).
Wildfire was launched in 2008 and is headquartered in Redwood City, California. It has offices in New York, Los Angeles, Chicago, London, Munich, Paris and Singapore.
In a blog post, Google's product management director Jason Miller explained the rationale behind the acquisition.
"In a complex and changing landscape, businesses want to manage and measure [social] efforts in an integrated way. We've been working towards this end for some time," he said.
"With Wildfire, we're looking forward to creating new opportunities for our clients to engage with people across all social services. We believe that better content and more seamless solutions will help unlock the full potential of the web for people and businesses," he added.
A Wildfire blog post attributed to its co-founder Victoria Ransom and Alain Chuard said:
"We believe that over time the combination of Wildfire and Google can lead to a better platform for managing all digital media marketing. To this end, Wildfire will operate as usual, and there will be no changes to our service and support for our customers."
The acquisition follows similar investments by other technology vendors. In May, Oracle bought social marketing platform Virtue for $300m (£194m), and in June, Salesforce.com bought social media marketing firm Buddy Media for $689m (£447m).
Oracle then continued its summer software spending spree with the acquisition of social media platform provider Involver, for an undisclosed sum.


text:
ACHICA > Room in Bloom
Sale closes in
Room in Bloom
Bring beautiful flowers indoors with this radiant collection of floral cushions. Choose from an array of colours and designs featuring delicate and vibrant floral prints, weaves and embroidery. From warming and passionate reds and pinks to the cooling and calming blues and greens, there are designs to complement every scheme. This collection provides the perfect excuse for you to spruce up your sofas and embellish your beds this summer.


text:
The Grand Canyon Caverns is your Gateway to the Havasupai Nation and Waterfalls
The Grand Canyon Caverns can help arrange and organize your visit to the spectacular Supai waterfalls. We are the closest place to stay to the "Hill Top" (the starting and ending point) before and after your Supai adventure. Please contact us to help setup this amazing adventure.
ONE DAY TRIP TO SUPAIThis is a long but very fulfilling brief trip to Supai and the amazing waterfalls deep in Grand Canyon.
This journey can be hiked both ways…limits your time at Supai and at waterfalls but is totally worth it, hike in and helicopter out, or hike in and horseback out. If you helicopter or horseback at least one of the ways that will leave you with more hours to explore and enjoy the world class waterfalls. If you are able we hope you hike at least one direction to be able to get a feel for the canyon walls in all their glory.
Stay with us at Grand Canyon Caverns before and after your Supai adventure.. We can link you up to the Supai services you will need and can help you book a room far in advance for the Lodge at Supai or the camp ground between the waterfalls. These both fill up fast.


text:
Kids and Computers
Little Tikes Young Explorer Computer: Ga Ga or Gag?
Like us on Facebook
With an estimated 16 million US children between the ages of two and 11 went online just in the month of May last year, it is no surprise that the company is focusing attention on preschool computer users. The Young Explorer seats two tots, has both left- and right-handed mousepads built in and comes equipped with Microsoft Windows. At $2,600, the piece is more likely to be found in a preschool, than an individual's home, but tell us, would you even want one at home?


text:
Adult singles better off unattractive than only mildly attractivePosted: June 20, 2012 | Author: Nudist Colony Tailor | Filed under: Buying and Selling, Dating and Relationships, Everyday Observations, Gender Affairs | Tags: 30 and single, dating, economics, L20E30, lemons, markets, single life |2 Comments
Consider these odds for a single play:
- 95% chance to win $50 and 5% chance to lose $80.
- 80% chance to win $100 and 20% chance to lose $80.
Most people are risk averse in these situations therefore you'd expect option 1 to win out even though option 2 has a higher expected return ($64 vs. $43.50). Now lets consider a third option.
- 70% chance to win $200 and 30% chance to lose $80.
In order to bribe risk-averse humans into accepting a greater probability of losing $80 the upside offered must be sufficiently large. Option 3 is essentially option 2 plus bribery. Option 3 with an expected return of $116 could overcome its higher probability of loses by offering a very tempting $200 pay day to the naturally loss averse. Depending on the risk profile of subjects, 1 or 3 may be favored. This makes option 2 a quite lonely middle ground although it is logically the most preferable option to a real person for whom an $80 loss would be a significant albeit a non-life changing event.
What does this all have to do with being kind of attractive and single? Okay lets consider the winnings in each option as a measure of attractiveness.
- Option 3 ($200 prize) ——> Very attractive
- Option 2 ($100 prize) ——> Above average attractive
- Option 1 ($50 prize) ——> Average to below average attractive.
Just like in the odds offered above the worst possible position to be in as a member of the coalition of the single is position 2. Although you offer a higher expected return than position 1 and a lesser probability of loses than position 3 (consider loses to be the probability of rejection or unforeseen negative surprises), the market for you is quite depressed. This effect is most pronounced in the late 20s and early 30s (L20E30) singles demo which I have written about in the past and will continue to write about because I find their predicament a very fascinating muse.
Alright lets plod on.
What is unique about the L20E30 group is that they are at a crucial stage in the human pair bonding progression when they're just old enough for most of the good ones to be identified and taken off the market but not quite old enough to have necessarily given up on the quest to find a partner and start a family and certainly not old enough to be on their second lap around the marriage and family circuit.
The top and bottom end (options 3 & 1) of the singles market that emerges after the early and mid 20s game of musical chairs appeal to established constituencies. The penthouse slices or the very attractive L20E30 singles attract the bold and beautiful, lottery ticket buyers, dreamy gold prospectors, creeps and the like. The below average L20E30s or the bottom floor slice of the market attract the timid and unattractive, bargain hunters, illogically risk averse and naturally creeps.
What is unaccounted for is the constituency composed of the non-creepy, reasonable and relatively logical who have reasonably assessed the high and low ends of the available pool of singles and find them either froth with risk (option 3 or very attractive) or just not good quite attractive enough (option 1). These level headed shoppers are able to appreciate the higher expected return of option 2 over 1 and the smaller probability of loses offered by option 2 over 3.
Here's the meat of theory: The same sanity that predisposes this group to linger on option 2 or the just above average attractive singles group precludes them from actually choosing them. The reason for this is a unique information asymmetry problem associated with occupying the dangerous middle to upper floors of the L20E30 singles high rise. The two key pieces of information unavailable to the outsider in this case are:
- Current relationship status
- The dimensions and weight of` baggage in tow.
Reasonable prospectors who lack the core competencies of creeps are keenly aware that they're late arriving to the party therefore there should be a reasonable expectation of an accepted bid given the apparent relative attractiveness of the singles in this middle group. In the event that there are no bidders, one can only reasonably assume that since enough time has been afforded for discovery a plausible explanation for lack of suitors could be product damage, lemons perhaps, so stay away. Both the accepted bid and no bid scenarios inspire inaction.
How is this any different for the very attractive you ask? Well like option 3 above suggests if the potential reward is sufficiently high our appetite for risk rises accordingly. In this situation the greater attractiveness encourages engagement at the risk of hitting on a girl who is quarter to engagement or halfway batshizz crazy. Moderately attractive singles just don't offer enough temptation to overcome the risks.
This is all very similar to a theory first presented by economist George Akerlof in "The Market for Lemons: Quality Uncertainty and the Market Mechanism" of which he later shared a Nobel prize for. Simply put the theory suggests that in markets where there is information asymmetry such as the used car market where the sellers know far more about the product than the buyers or the health insurance market where information is concentrated on the side of the buyers, market forces may conspire to discourage owners of good products from bringing them to market.
This happens because the side of the market on the wrong end of the information disparity will either leave the market in fear of getting ripped off or drive the prices to an extreme that reflects a market where every product is a lemon. Under these conditions the very top end of the market would command enough confidence to attract a fair price, the lemons would be all too happy to settle for lemon prices and the slightly above average would either have to trade at a significant discount to objective worth or not at all. The potential losses due to participation in such a market increase as the product quality departs from the average lemon without approaching premium status.
In conclusion as an adult straddles 30 in singlehood its surprisingly beneficial to be decidedly below average attractive which reduces the information problem by providing a plausible thesis for the relationship status and inspire interest from bargain hunters and the like or be strikingly attractive in which case information asymmetry be damned.
I devised this theory while I was at the gym today looking a girl who was sufficiently attractive to get my attention but not enough to risk making a fool of myself given that I figured she looked just good enough to justify some expectation of a boyfriend somewhere. As I observed my internal deliberations and risk analysis of each course of action I realized that her biggest fault was being around my age and only kind of attractive.
2 Comments on "Adult singles better off unattractive than only mildly attractive"
myatheistlife says:
The agnostic forcefully abstains from an argument with actual definition. Humans invented gods and claimed them to be real despite their inability to prove this. The agnostic does them a favor and gives them credit by stating they cannot know the theist is wrong for proffering this folly.
The point that the entire universe has not been searched is hubris. The theist claims their god is supernatural and so cannot be part of the natural world. Further, the theist claims that their god is omnipresent and so detection should not require leaving your seat, never mind this planet. The theist still needs to back up their claims with evidence. Agnostics might want to abstain but the evidence as we know it shows their position to be disdain rather than one of abstention.
Nudist Colony Tailor says:
You commented on the wrong post… I've replied on the next post which can be found here http://nudistcolonytailor.com/2012/06/22/atheists-theists-agnostics/


text:
Got this costume? Want your photo to appear here? Tag your Instagrams with @jokersmasquerade and #jokers61842. How do I tag my photos?
Our sexy Burlesque Victorian Vampire Costume includes an attractive black and burgundy dress with lace sleeves, collar with choker and hat. This outfit would make a perfect Halloween costume.
Sizes for this costume are:
November 5, 2014, by Samantha L - Cardiff, UK - United Kingdom
Once again another brilliantly made outfit, absolutely pleased! And again got it at a super duper deal.
November 5, 2014, by Michelle S - Kent, UK - United Kingdom
I couldn't believe how quickly the costume arrived and how good it was. Would recommend.
November 4, 2014, by Julie H - South Yorkshire, UK - United Kingdom
Arrived on time, was a lot better than I thought it would, everyone said how good it looked overall very impressed with the service and product. Would use this website again.
November 1, 2014, by Nicola W - West Midlands, UK - United Kingdom
Firstly I paid for next day delivery which costs a whopping 10.99 and it came two days later which is disgusting. Then when the dress came up on the day of my party it was torn on the sleeve where the velvet meets the lace and it was also torn where the collar is attached to the lace at the back. I spent the entire day making adjustments and sowing it back together. Also the 'basque' that comes with the costume is about two sizes smaller then the costume so I had to buy that extra as well. Very disappointed to say the least, I will not be using this store again! Only decent part of the costume was the hat!
December 13, 2013, by Lynda H - East Yorkshire, UK - United Kingdom
Absolutely brilliant. Really quick delivery and the dress itself is extremely good quality. All accessories came with it too. Highly impressed. Thank you :)
November 6, 2013, by Carol B - Tyne And Wear, UK - United Kingdom
Excellent all round service. Knowledgeable staff and good value for money. Costume was a better quality than I anticipated.
October 31, 2013, by Rebecca M - Exeter, UK - United Kingdom
excellent service, excellent response and excellent delivery time.
Have a question about this product? Why not get in touch by completing the boxes below.
No, the velvet pieces are rigid, so this costume is not stretchy.
The colour is definitely burgundy. The bright red in the photo may be due to the camera flash or photo editing by the customer.
Items are considered "oversize" which exceed 610mm x 460mm x 460mm or over 5kg in weight and cannot be dispatched via Royal Mail or Click and Collect. Oversize packages can only be dispatched via courier. We will only display the delivery options available to you, based on your location and the items in your basket.


text:
RUDD DRAW. Rudd Draw, a valley with an intermittent stream, rises (at 31°52' N, 103°31' W) in north central Loving County eight miles south of the New Mexico state line and runs southwest for thirteen miles to end in a playaqv (at 31°44' N, 103°29' W) a mile south of State Highway 302 and five miles northeast of Mentone, Texas. The course of the draw crosses steep to gentle slopes and flat to rolling prairies of caliche, alluvial sands and silts, windblown sand, and playa clays and silts. The soils of the area are fine-grained brownish-red loamy sands and gravelly loams. Vegetation consists primarily of small mesquite, greasewood, creosote bush, cacti, and sparse range grasses.
The following, adapted from the Chicago Manual of Style, 15th edition, is the preferred citation for this article."RUDD DRAW," Handbook of Texas Online (http://www.tshaonline.org/handbook/online/articles/rbrcs), accessed October 09, 2015. Uploaded on June 15, 2010. Published by the Texas State Historical Association.


text:
|Announcements Check here for important announcements made by site administrators.
|Thread Tools
|Display Modes
Unique Opportunity For Collectors
Hello Everyone,
As I trust we have proven already, Goldin Auctions works as hard as anyone to promote our auctions to generate bids for our consignors. From our appearances on CNBC to Bloomberg Television, ESPN, Fox News and various other news agencies, people often tell us they are amazed at just how visible we are in the marketplace. Further, based on independent tracking of web traffic, the Goldin Auctions website currently receives significantly more web traffic than all of its major competitors whose primary focus is sports memorabilia auctions. This is determined by visits per day, page-views per day, etc. This, of course, has translated into incredible realized prices that have benefited our consignors and enabled us to create a great deal of consignor loyalty.
With that said, we have a unique opportunity right now for potential consignors to our upcoming July Babe Ruth auction. As you may already know, we are planning an enormous event for this July that will be one of the biggest auction events our industry has seen in some time. With this auction, in addition to all the media coverage we will be getting -- obviously we will likely once again be on all the major news networks, etc. -- we will also be doing some other marketing that is somewhat staggering. With respect to catalog distribution, we currently have one of the 3 most widely distributed catalogs in the sports industry. However, for the Babe Ruth auction we expect our catalog distribution to TRIPLE, far exceeding any auction conducted in our industry. In addition, we will be sending out over 1 million brochures to promote the auction as well. Please note that is NOT A TYPO. We will be sending out over 1 million brochures with the distribution to include:
a) Approximately 150,000 to our database;
b) Approximately 150,000 to the PSA database;
c) Approximately 150,000 through the Dupont Registry;
d) Over 300,000 through other sources targeting high net worth individuals; and
e) 250,000 thru Major League Baseball sources, stadiums, museums, and card dealers.
Needless to say, this is a unique opportunity for you to place your items in one of the most visible auctions our industry has seen in some time. If you have any items you are considering consigning, please contact us right away so we can try to reserve placement for your items in this auction. As you can imagine, we are already getting tons of items and we cannot guarantee placement of your items if you wait until the last minute to consign.
In addition, if you have any VERY HIGH-END items you would like to consign we might have a unique marketing opportunity for them if you contact us right away.
We look forward to hearing back from you and hopefully having the privilege of representing your items in this blockbuster event. If you would like to contact me directly to discuss this further, I can be reached by phone at 925.413.1429 or by email at email@example.com.
Christopher Cavalier
Vice President of Consignments - Goldin Auctions
|Thread Tools
|Display Modes
Linear Mode


text:
Sonatas for violin & piano by Schubert, Brahms, Bloch, Gershwin / Lana Trotovsek, violin; Yoko Misumi, piano
1 CD / Meridian / 2013-08-13Works: Franz Schubert: Sonatina for Violin and Piano in A minor, D 385/Op. 137 no 2; Johannes Brahms: Sonata for Violin and Piano no 3 in D minor, Op. 108; Ernest Bloch: Baal Shem; Igor Frolov: Concert Fant...
Performers: Misumi, Yoko; Trotovsek, Lana
Rising star Lana Trotovek, who debuted with Valery Gergiev and the Mariinsky Theatre Orchestra in September 2012 with Prokofiev's Violin Concerto No.1, is receiving remarkable...continue...
Recording information: St. Edward the Confessor Church SE London (07/10/2012-07/12/2012)....continue...
The Quiristers of Winchester College sing Brahms, Mendelssohn, Mozart & Schubert
1 CD / Meridian / 2009-09-08Works: Felix Mendelssohn: Herbstlied, Op. 53/4; Gruss, Op. 63/3; Duets (6), Op. 63; On Wings of Song; Das Ahrenfeld, Op. 77/2; A Midsummer Night's Dream; Johannes Brahms: Romances and Songs (5), Op. 84; Son...
Performers: Bottone, Robert; Brett, Francis; Evershed, Edward; Gibb, William; Nouban, Arron; Seligman, Tom; Smith, Julian
Meridian Records is proud to announce a new issue of the Winchester Quiristers singing part-songs, duets, and solos by four great composers of the classical...continue...
Brahms: Hungarian Dances, etc / Alvanis
1 CD / Meridian / 2004-06-08Works: Johannes Brahms: Hungarian Dances (21) for Piano 4 hands, WoO 1; Sarabande for Piano in A minor, WoO posth. 5/1; Sarabande for Piano in B minor; Gavotte for Piano in A major; Gigue for Piano in A min...
Performers: Alvanis, Louis Demetrius
Since his highly acclaimed Royal Festival Hall concerto debut before a capacity audience, London-born pianist Louis Demetrius Alvanis has established an international career and a...continue...
Brahms, Dvorak: Piano Quintets / Concertante
1 CD / Meridian / 2002-11-05Works: Johannes Brahms: Quintet for Piano and Strings in F minor, Op. 34; Antonín Dvorák: Quintet for Piano and Strings no 2 in A major, Op. 81/B 155
Performers: Denk, Jeremy; Frautschi, Jennifer; Gerlach, Alexis Pia; Jacobsen, Colin; Johnson, Kirsten; Plesser, Zvi; Shapiro, Rachel; Wang, Xiao-Dong
Ensemble: Concertante Chamber Players
"Concertante's performances are distinguished by their tenderness; they seem to linger lovingly over every phrase, though they aren't really slower than anyone else, and their...continue...
Dvorák: Mass in D; Bruckner, et al /Bristol Cathedral Choir
1 CD / Meridian / 2001-08-07Works: Antonín Dvorák: Mass in D major, Op. 86/B 153; Johannes Brahms: Geistliches Lied, Op. 30; Motets (3) for chorus, Op. 110; Anton Bruckner: Christus factus est; Tota pulchra es, WAB 46; L...
Performers: Cave, Philip; Coupe, Anthony; Foulkes, Stephen; Pinel, Anthony; Taylor, Stephen [Treble]
Conductors: Archer, Malcolm
Ensemble: Bristol Cathedral Choir
Brahms: Sonatas for Viola and Piano Op 120, etc
1 CD / Meridian / 2000-06-26Works: Johannes Brahms: Songs (2) for Alto, Viola and Piano, Op. 91; Sonata for Clarinet (or Viola) & Piano no 1 in F minor, Op. 120/1; Sonata for Clarinet (or Viola) & Piano no 2 in E flat major, Op. 120/2
Performers: Jacobson, Julian; Silverthorne, Paul; Walker, Sarah
Anthems from Salisbury / Seal, Salisbury Cathedral Choir
1 CD / Meridian / 1991-07-01Works: William Byrd: Gradualia, Volume 1; Henry Purcell: Rejoice in the Lord Alway, Z 49 "Bell Anthem"; Samuel Sebastian Wesley: Blessed be the God and Father; Charles Hubert Parry: I was glad; Johann Sebas...
Performers: Walsh, Colin
Conductors: Seal, Richard
Ensemble: Salisbury Cathedral Choir


text:
Championship leader Fernando Alonso of Ferrari won his third race of the season in the German grand prix in Hockenheim on Sunday.
The Spanish two-time world champion crossed the line ahead of Red Bull's defending world champion Sebastian Vettel of Germany, who snatched second place from third-placed Briton Jenson Button of McLaren.
For pole-sitter Alonso it was his 30th Formula One victory, and third this season after the Malaysian and European grands prix.
Australia's Mark Webber finished in eighth place.


text:
Plastic coins are inexpensive and easy to find at most party stores. Because they are so lightweight they're a snap to work with. I used some white string and a hot glue gun and glued the coins (back-to-back) to create a garland across the mantle. I love how they sparkle in the light!
Another way to use these is to hang them from the ceiling, doorway or chandelier above the dining table...
I found my coins at iparty. A large bag of 144 coins costs only $5.99!
You could also use colored ribbon in place of the string, swag them along a staircase or surround a door frame. Any other ideas? Send me a photo of how you'll decorate with gelt!
Linked to:
The Lettered Cottage
Nesting Place


text:
In transparent brown acetate, Cutler and Gross' D-frame optical glasses will lend a retro accent to your everyday look. Wear them with dressed-down outfits for instant chic.
Brown transparent acetateScrew detailing at sidesCan be fitted with prescription lensesCome in a designer-stamped black hard case
Product code: 188798 - Need help? Contact us


text:
Go on a Halloween treasure hunt with Jake, Izzy and Cubby!
A Spell for Mr. Cedric
Create your own pirate pumpkin for Halloween.
Decorate your own Spooky Ooky house for Halloween.
Create your own family portrait of roarsome monsters.
Amber makes a wish with Cedric when she wants to win the costume contest on All Hallows' Eve.
Doc helps her friend, Sebastian, when he is scared by frightening Halloween decorations.
Ariel teaches Sofia about the love we share!
Sofia discovers a whole new world when she is small!
Help Jake, Izzy, and Cubby make their way through the maze to collect Treasure Tooth's figurehead!
Spot and count the hidden musical notes in the scene!
Help Doc, Lambie, and Stuffy connect the dots!


text:
Red, Red Everywhere
I wanted to add these two photos of the ballparks all dressed up. Actually the Cards call their's a stadium because the old one was called Bush Stadium… i want to call it a ballpark. It is a beautiful place- you should all visit it. It is so nice to be back here, oh wait, i wasn't even born in 2004. It is still nice to be here- midwesterners and Cardinal fans are so friendly. Maybe they could be friendly with some errors or throwing the ball over the plate for Big Pappi tonight. Also, i like those give away towels- but maybe people could just twirl them later, or in the privacy of their own homes- they distract from my fan experience.
I hope things go well tonight for the Red Sox…I can't take a game like last night. We dogs need our sleep.
keep the faith,
Fenway the dog
Make Way for Beards
Hello everyone:
I am not even going to make excuses about my extended absence, i know you all have lives and also low expectations about my writing regularity.
With that said, i will let you know that I GRADUATED (!!!!!!) and am now teamed with an awesome young man and his family. Sorry Salty…i can't come live with you, and you need to focus on baseball and helping umpires to update some rules. If i had been at last night's game i would have run on the field and showed them some real interference! My new family is wonderful and they love the Red Sox. They have respect and support for my continuing to write. No, they are not in the Witness Protection Program…I just need to keep my two working lives separate so you all won't come over and trick or treat just to meet my new family. Candy is expensive.
Because i am an obvious fan of the furriness …i also fully endorse the beard. (what do you think of mine?) I think they belong on the players, fans, ducklings, cupcakes, and anywhere the magic can be enhanced. Mine gets in the way a little when i am eating and drinking- but i am taking one for the Team.
keep the faith,
Fenway the Dog
Floating Down Pennsylvania Avenue
Hello patient followers:
It has been a busy winter and I can't wait to tell you about: Christmas at Fenway, a new addition to Bentley University …and about being Santa at Greenfield Community College's holiday party and wish you a happy new year. I can do that really fast- Happy New Year. The rest will have to wait until after….
this Sunday,January 21st
Because I will be in the Inaugural Parade with 56 CCI assistance dogs and dogs-in-training! Dream come true for Canine Companions- could be better than winning the World Series (if it happened more often). I know that Governor and Mrs. Patrick have a fine lab- perhaps we can all have a sit down while we are all in town to discuss some issues small and large like: covering service dogs for military vets with PTSD, health care, gun violence, and that silly trillion-dollar coin (they are all serious as a cliff- "the" cliff, but the coin has to be a joke from a Saturday Night Live skit that the news got confused with a real story).
Here is some information about the parade before I float too off track:
2013 Presidential Inaugural Parade on January 21st in Washington DC.
CCI is one of 43 organizations from across the nation selected for this honor from over 2,800 applicants. 134 CCI assistance dog teams, puppy raising families, volunteers and supporters will march in the parade, along with 57 assistance dogs and dog-in-training, which will be viewed by millions across the globe.
"The President has placed a big emphasis on the idea of service – including a National Day of Service as part of the inaugural tradition – and many of the groups chosen to march in the parade reflect the idea of serving one another and giving back to the community", according to the Presidential Inaugural Committee.
Take a look at the News 9 coverage and story (WUSA9.com in case the link doesn't work):
More later…hope you will be watching the parade.
thanks for following,
Fenway the Dog
Winter Pause For More Fall
Maybe winter could hold back for a week or so. Fall is so great…and Sandy blew the good part away (I found one last leaf).
I am so happy that my fellow CCI* pups and family members are safe after having lived through 8 days without power in our training facility on Long Island. Hope you all will look on the Canine Companions for Independence website…you will be able to see graduation photos. Also, there is a link to a Eukanuba live puppy cam. Nothing is cuter than puppies…babies are a distant second, and then, I guess…well…those are the only cute living things that i like. Kittens maybe.
thanks for following me,
Fenway the Dog
*Canine Companions for Independence
Not a Trick…here come the treats
Hello Everyone!
Even Hurricane Sandy cant keep me from coming to town this week to see my friends. I will be handing out some treats at Halloween at Fenway (please come), and blowing around town giving some Fenway the Dog Treats to dog-friendly businesses. We landed some at Angell Memorial last week for their Hall of Fame Dinner and for their Pit Bull Spay/Neuter clinic. (if you go there, I can't promise it will still be hanging on the letter d…but please go visit them and their adoption center while you are there…tell them I sent you).
Not to be a tattle tail but, some dog friendly places I know of for starters are: Fast Frame in Washington Square in Brookline Village. Hsui-Lan, the owner, always has her greyhound in the store, and recently coordinated a dog-friendly community Wag-A-Thon, Serenella on Newbury Leslee the owner raises lots of money for animal support organizations, of course Fairmont Copley Plaza where my pal Catie Copley lives (she almost always in the lobby meeting and greeting)…I am giving them all some treats for being so nice. There are tons more- please feel free to write me and be a dog-friendly dog catcher. Nothing makes me more happy than to see a nice water bowl outside of a place of business. Why is it that people are so worried about touching public bathroom door handles while we are sharing slobber and drinking out of toilets? I am not saying that God likes us more….but don't you think it is remarkable that we can eat some gross dead thing we find on a walk, while humans get sick from a slightly old bologna sandwich?
In case you are a high school senior and looking for a dog friendly place- Bentley University might soon be dog friendly…and have some Canine Companions puppies on campus being raised (just as i am doing at Greenfield Community College)! It is nice of them to also have Canine Companions blue and yellow colors like we do. Stay tuned for more on that.
See you around Boston this week!
Fenway the Dog
Ode to Joy
This is Joy, who started out as a Canine Companion puppy like me about 15 years ago. Part lab, part golden and really smart . Although she didn't make it to advanced training, she went on to bring love and companionship to a wonderful man named Brian. I recently read a story (tail tale) of Joy's life with Brian, and hope that he will write to share it with all of you. I would retell it here, but he is a brilliant writer and I might dog it down too much. Brian is tall, bold, boisterous, gentle and powerful….and has a heart so big that it barely fits in California. And Joy, well, take a look above…this photo is a thousand-word essay on both of them.
I hope you all are having a great summer, I have missed writing and have so much to share and catch up on.
Thanks for reading,
Fenway the Dog
Head over Heels
Well, I will say that many things happened on the field this Friday including a baseball game, but for some reason this moment keeps drowning out all of the other moments that day. I will never wash my head again, Paula kissed me.
I am in Love,
Fenway the Dog
P.s. I was downloading some of Paula's music today… all of the lyrics are also now stuck in my head. They speak to me…Promise of a New day, Will You Marry Me, Under my Spell….yes, Opposites Attract.


text:
Barriga was driving her vehicle south on 144th Avenue at about 6 p.m. Saturday. She stopped at the stop sign at the intersection of Port Sheldon Road, then proceeded into the path of a vehicle driven by Todd Rhonda, 35, of Hamilton, Garvelink said. Rhonda was pulling a trailer carrying a 25-foot boat.
"(Barriga) mistakenly thought it was a four-way stop," Garvelink said.
Barriga and her passenger, Barrios, were taken by ambulance to the hospital. Rhonda and two passengers in his vehicle were not injured, police said.
All of the people in the two vehicles were wearing seat belts.
Port Sheldon Road was closed for an hour and a half while the crash was investigated and cleaned up, Garvelink said.


text:
This nourishing sheen spray provides a glorious shine that lasts all day without a heavy greasy build up.
Great for a body spray as well ! I use it on photo shoots to highlight my skin. Works great ! I love products with dual uses. Doesn't leave your hair greasy or overly shiny.
This product is perfect for a final hairstyle..I recommend you never use this at night because it tends to get grease all over pillows..use this product if you are going somewhere and like you hair looking healthy and shiny,i get soo many compliments about the smell and look.!
Bought this product in the hopes that it does what it says. I was disappointed because it didnt. Apart from this the product smells horrible, it left my hair brittle and dry and overly shiny.
Saludos a tod@s, Gracias al olive oil ya no sufro por mi pelo áspero y duro, de muy difícil peinado sin agua o algún producto idratante. He probado a lo largo de 8 años muchos producctos para poder peinar mi pelo duro y revelde, y no me ha ido bien del todo, pues los productos oleosos son muy caros y viene poca cantidad, sinembargo el olive oil en espray, me ha facilitado totalmente el peinado, además es muy duradero, me lo compré hace 5 meses y lo uso diariamente por la mañana y por la tarde, con efectos alucinantes para mi cabello. me desenreda este pelo estropajo que tengo, lo utilizo con el pelo húmedo y luego me aplico unos 6 segundos el espray por todo el pelo y...sencillamente fantástico, y de precio igual de bien, pues sale muy muy económico. pues los botecitos de aceite para el pelo son normalmente pequeños y no duran mucho, a mi no me duran más de un mes. y además son más caros que el olive oil. Os lo recomiendo si lo que buscais es calidad-precio, va genial para pelos muy castigados y reveldes. mi calificación es de muy buen producto. gracias por ofrecerlo en el mercado, un saludo. javier
I always have a bottle of this under my sink. I don't really use it that much when my hair is out, this is my to to oil sheen when my hair is braided.
I used this forever when my hair was relaxed. Its a very great moisturizing oil, but it dries up too quickly for me. If it came in a bottle, as an actual oil, that would be great.
This product has been used on my hair since I was 12 years old. The spray smells amazing. It leaves the perfect amount of shine without it being heavy or greasy looking. I also use it on my scalp the night before i wash it because i suffer from dry scalp in the winter due to the cold weather. Best of all its totally affordable!
This sheen spay is amazing. Most sheen spray leave a greasy feel to the hair. This one goes on as greasy but eventually it gets absorbed by the hair and it nourishes it. It makes the hair feel silky and smelling great. The smell is no where near to olive oil. It smells clean. But the big thing is that it nourishes your hair and makes it look healthy, and shiny!
This spray is amazing, Its not only sheen spray but a wonderful hair spray.It makes the hair super sheen,clean,and shiny. You should totally try it out. Its also great for straightening hair. Its truly amazing.
Great shine! I use it after i get my natural styled for added shine. I also use it when i have extensions, it brings the hair "back to life" (well not really lol) The only down side is that i find that when i use it, it seems to make my skin even more oily than what it is already!


text:
Recently over at Green Building Advisor, a great resource for green building knowledge, there's been a hot discussion around the concept of building a "Pretty Good House."
Now at first glance, that sounds like a bad deal. Don't we want to live in a house that's more than just "pretty good?" Yet the idea behind a "Pretty Good House" is to provide a new type of roadmap for building a green home, one that focuses on cost-effective and common sense energy and durability performance, rather than trying to build to the exact requirements of a green building certification.
Don't get me wrong, I think that green building certification programs like LEED or Passive House are wonderful, well-thought out ways to create a building with reduced environmental footprint and lasting value for the homeowner, but they aren't for everyone. Certification means that a widely-recognized green label gets placed on your home—but it also means extra cost in certification fees, and building to a checklist of requirements that may not have the flexibility to match everyone's budget or design constraints. By contrast, a "Pretty Good Home" is a home that doesn't certify but that incorporates those green building and energy efficient features that made sense to the project and were cost-effective, enabling homeowners who don't have the flexibility or funds to go all the way to a Passive House the opportunity to live in a house that functions well and has a reduced impact on the environment.
Since it isn't a certification, but rather an idea, green building professionals across the country have been given the opportunity to weigh in on what green strategies define a "Pretty Good Home" in their particular climate. Recently, some of my suggestions for a "Pretty Good Home" in a North Carolina climate–what building scientists often refer to as a "mixed-humid" climate–were featured in a follow-up post at Green Building Advisor. Whether you're building a home that aims to go all the way to Passive House standards or one that merely aims to have some Pretty Darn Green features, these are the most important green strategies that I recommend to customers building in a climate that is cold in winter, warm in summer, and humid for a good portion of the year.
1. Passive Solar design
2.Insulation values exceeding minimum code requirements
3. A "right-sized" home that incorporates outdoor living space
4. Solid heating and cooling system design
5. Smart water management
In follow-up posts on this blog, I'll go into each of these design principles in more detail.


text: Photo Courtesy: Oneida County Sheriffs Office [ Ellen Bischof Located This Morning By Kristine Bellino September 30, 2013 Updated: 09/30/2013 5:30am Ellen Bishof was located this morning. Sheriffs say that she appears to be unharmed and is receiving a medical evaluation. Read More|Comment Category: Utica-Rome News Tags: ellen bischof, floyd, missing person, Oneida County Sheriffs Send to a friend! Share on Facebook Share on Twitter Pin it! Reddit This! Share on Tumblr!


text:
(HBO on Comcast) With his wife in a coma, a Hawaii lawyer (George Clooney) has to cope with all the parts of his life he didn't know. A somewhat minor work from director Alexander Payne that's also a movingly rich pleasure about compromise and connection. With Shailene Woodley and Amara Miller as the hero's daughters. (R; runs through April 8)
(Comcast Movie Collections: Just In) This overcoming-adversity documentary from director Ramona S. Diaz follows the story of Arnel Pineda, who stepped into the very large shoes of Steve Perry as lead singer of Journey. It's an inspiring, if slightly by-the-numbers, rags-to-riches story. Who wouldn't root for Pineda (other than maybe Perry)? (Unrated; runs through May 8)
(HBO on Comcast) Matthew Broderick, as an Air Force lab assistant, talks to animals, in particular a chimp named Virgil. This pro-animal-rights film, which centers around Broderick's efforts to keep the chimp from being zapped by a dangerous experiment, is appealingly gentle, but ultimately too tame. (PG; runs through April 29)