[uf-new] hAudio 'acquire' re-naming (Microformats should use
nouns for properties)
brad.hafichuk at gmail.com
Tue May 8 14:30:31 PDT 2007
This kind of relates to something I was mulling over. If you link to a third
party site, how do you guarantee that you don't get a 404 response? I can't
think of any other solution short of periodically "pinging" that url and
checking the response. In theory just checking the content-type and
content-length from the request should give you enough information to at
least highlight this as a problem.
The argument could be made that if you're going to be relying on a
third-party, then some form of formal arrangement should be made between the
On 5/8/07, Andy Mabbett <andy at pigsonthewing.org.uk> wrote:
> In message <A8233CF8-74E5-4886-B816-C221C18776D9 at makedatamakesense.com>,
> Scott Reynen <scott at makedatamakesense.com> writes
> >On May 8, 2007, at 10:22 AM, Chris Griego wrote:
> >> rel-enclosure was ruled out because it's not always a download, but
> >> sometimes a way to purchase, right? What if hAudio suggested the use
> >> of rel-enclosure for downloads and rel-payment for ways to purchase?
> >I think this is an excellent idea. In addition to re-using existing
> >microformats, knowing whether a link is a direct download or a
> >purchase form would allow tools to provide more useful options to
> I can foresee problems.
> Suppose a publisher links to a third-party site, offering an audio track
> as a free sample (or vice versa). Later, that latter site decides to
> start charging for the track - how would the publisher know that their
> site is no longer correct?
> Andy Mabbett
> * Say "NO!" to compulsory ID Cards: <http://www.no2id.net/>
> * Free Our Data: <http://www.freeourdata.org.uk>
> * Are you using Microformats, yet: <http://microformats.org/>
> microformats-new mailing list
> microformats-new at microformats.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the microformats-new