Proposed SSE spec changes, round 1

I’ve received a bit of feedback now on the v0.93 spec that was published in June here: http://msdn2.microsoft.com/en-us/xml/bb510102.aspx.

 

As part of revising the spec for the next update, I’ll be sending out all of the proposed changes for your review. I’ve collected about 30 changes, mostly small ones, so I’ll break the change list apart into several emails over the next couple of days. I’ve tried to capture the context and reasoning for each change in the description, but feel free to ping me if any of them are unclear.

 

Here’;s the first set:

 

----

 

1:: Fix wording in sx:conflicts description

 

In section 2.5, the second sentence should read:

When the sx:conflicts element is present, it MUST contain one or more item sub-elements, where each item or entry represents a conflicting update.

 

The change was to update the phrase “each item represents̶1; to “each item or entry represents” to reflect the addition of Atom support in this revision.

 

2:: Fix sx:sync/id in examples

 

Spaces are not allowed in the sx:sync/id attribute. The spec will be updated to remove spaces from every instance of sx:sync/id that contains one. They are in the examples in section 1.4.1, 1.4.2, 3.1, 3.2, 3.3, and 3.4.

 

3:: Fix conflict item/entry in examples in 3.3

 

The <sx:sync> elements in conflict items in the RSS and Atom examples are not closed. In each example, just above the </item&gt; and </entry> tags, we will add </sx:sync> to close the <sx:sync> element.

 

4:: Fix time value in example in 3.3

 

We will remove the extra “0&#8221; from the RSS example, in the “when” attribute in the sx:history with sequence 2.

 

5:: Fix reference to window attribute

 

In Section 3.2, the last sentence of item number 2 under the text “Additionally implementations MAY…” should read:

Also note that publishers SHOULD rely on the since, until, and expires attributes (if present) of the sx:sharing element to determine when to stop publishing items.

The current version mentions the “window” attribute, which was removed in an earlier version of the spec.

 

6:: Fix date value following section 5.2.4

 

In the note about “since and until valuesR21; following section 5.2.4, we will fix the sample RFC3339 date so that it reads 220;2006-05-02T09:10:33Z”.

 

7:: Fix reference in section 2.5

 

In section 2.5, the last sentence should read “See conflict preservation behavior (section 3.4) for more information.” (Current version incorrectly references section 3.5, which doesn̵7;t exist.)

 

----

 

This first set is pretty straightforward…;hope they all make sense.

 

Thanks,

Steven Lees

CSA Concept Dev Team

Microsoft