Re: [Simple] Partial publication & version attribute

ext simple-bounces@ietf.org wrote:
> Hello,
>
> draft-ietf-simple-partial-publish-05, section 3.2, says:
>
> "Versioning of these partial publications is necessary to guarantee that
> the changes are applied in the correct order.  The PUBLISH method
> [RFC3903] already accomplishes this using entity-tags and conditional
> requests, which guarantee correct ordering of publication updates. Note
> that the partial PIDF format [I-D.ietf-simple-partial-pidf- format]
> contains the 'version' attribute that could be used for versioning as
> well.  However, we chose not to introduce an additional versioning
> mechanism to partial publish, since that would only add ambiguity and a
> potential undefined error case if the two versioning mechanisms were to
> somehow contradict."
>
> However, XML schema of partial pidf presented in
> draft-ietf-simple-partial-pidf-format-07 defines the 'version' attribute
> to be mandatory:
>
> <xsd:attribute name="version" type="xsd:unsignedInt"/>
>
> So how should partial publications be processed on presence server? Am I
> right if supposing the presence server to require the 'version'
> attribute but to ignore its value? Or is it simply a bug in
> specification?
>
> Thanks for any comments.
>
> Best regards
>
> Michal Burda
>
>
>   
actually attributes are optional by default with the w3c schema (agreed, 
not very intuitive). So clients should not publish 'version' info, but 
if they do, servers just ignore them.
br, Jari

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple