Hi,

Just curious if anyone has done this or has opinions either way; e.g.

<link href="http://example.com/path/to/{deviceType}/movie/resource";
type="video/quicktime" />

Where the client applications know to substitute the parameter
appropriately.

Versus using Media RSS or similar:

<media:group>
  <media:content url="http://example.com/movie1.mov";
  fileSize="15555"
  type="video/quicktime"
  medium="video"
  isDefault="true"
  expression="full"
  bitrate="128"
  framerate="25"
  samplingrate="44.1"
  channels="2"
  duration="185"
  height="200"
  width="300"
  lang="en"/>
  <media:content url="http://example.com/movie2.mov";
  fileSize="12345"
  type="video/quicktime"
  medium="video"
  isDefault="true"
  expression="full"
  bitrate="128"
  framerate="25"
  samplingrate="44.1"
  channels="2"
  duration="185"
  height="200"
  width="300"
  lang="en" />
</media:group>

For my domain (mobile applications) the smaller payload is quite attractive,
and I control all of the clients of the feed, since I'm writing them. One
niggle is that I don't think the URI template is a valid IRI, so validation
tools might grouse.

Cheers,

James

Reply via email to