Hi Turadg, Thanks for bringing that to our attention; we should definitely encode that output since we're labeling it as appropriate for direct inclusion. I've created a bug to track this: http://code.creativecommons.org/issues/issue447.
Nathan On Mon, Aug 31, 2009 at 3:34 PM, Turadg Aleahmad<[email protected]> wrote: > I recently started using the "creativecommons" Drupal module that Blaise has > been developing this summer. Today I came across a bug that is rooted in > CC's REST service (http://drupal.org/node/564816 ). > The output of the /support/jurisdictions call is HTML, but not fully to spec > because it has a naked "&" character. I guess it depends on what version of > HTML is being returned. HTML4 says & *should* be encoded as &. And if > it's supposed to be XHTML, then it's necessary. > Specifically, I believe the output for "UK: England & Wales" should be "UK: > England & Wales". The 1.5 and dev versions both output the former. > http://api.creativecommons.org/rest/1.5/support/jurisdictions > http://api.creativecommons.org/rest/dev/support/jurisdictions > > Could the output be entity-encoded? Or perhaps there could be an output > like the ".js" for XML? > http://api.creativecommons.org/rest/1.5/support/jurisdictions.xml > -Turadg > > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
