Defect #112

Encoding

Added by Adrian Georgescu about 5 years ago. Updated over 2 years ago.

Status:New Start date:
Priority:Low Due date:
Assignee:- % Done:

0%

Category:Interoperability
Target version:Nice to have

Description

URIs in att_value. Should differently encoded be considered equal?

Note, that there're 2 encodings: percent-encoding, and xml attribute encoding (i.e. " and friends)

Resource Lists RFC features example document with http URI that has percent-encoding in it. Does that mean that to match against it, percents in the URI should be themselves percent-encoded?

Or XCAP server should use its knowledge about the app and figure out that URIs are equivalent. This may be unreliable if it's unknown whether this URI was percent-encoded or not. Why that URI was percent encoded in the first place, why not paste it in the documents as it is, using XML escaping where necessary.

Make few simple xpath expressions that include that URI as att_value and post it SIMPLE mailing list.

History

Updated by Tijmen de Mes over 2 years ago

  • Assignee deleted (2)

Updated by Tijmen de Mes over 2 years ago

  • 7 set to trunk

Also available in: Atom PDF