Comments on: Extending RSS and MicroFormats http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/ The journal of Paul M. Watson Fri, 21 Nov 2008 21:50:56 +0000 http://wordpress.org/?v=2.7-beta1 hourly 1 By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-8003 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-8003 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-7967 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-7967 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-9838 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-9838 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-9975 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-9975 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-10848 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-10848 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-11342 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-11342 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Paul Watson http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-14821 Paul Watson Fri, 23 Nov 2007 20:59:37 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-14821 I'm not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn't a consumer production play. I've used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.<br><br>And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn't change to XML tools just to get extra elements in an RSS feed and they wouldn't do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.<br><br>The benefit of the MicroFormat is to the end-user who doesn't need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data. I’m not sure powerful XML tools is a strong argument for XML grammars, especially in this case which isn’t a consumer production play. I’ve used a few XML tools and they are not for the layman. The market still seems to center around purpose built applications which can then emit structured data.

And for the kinds of companies wanting to use product meta-data in RSS the source would be a database and server-side application. Amazon and co. wouldn’t change to XML tools just to get extra elements in an RSS feed and they wouldn’t do it to get MicroFormats either. But the RSS producer should be easily configurable to insert the MicroFormat (and even extra RSS elements) from the product database.

The benefit of the MicroFormat is to the end-user who doesn’t need updated tools to gain the benefit of the extra data. In Google Reader it would just be HTML and to a machine it would be easily parsable data.

]]> By: Randy Charles Morin http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-8002 Randy Charles Morin Fri, 23 Nov 2007 18:32:30 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-8002 I think hResume v HR-XML Resume XML best shows why new XML grammars are better than microformats. In order to build a hResume fragment, you have to understand how microformats work. With HR-XML, you just import the XSD into an XML editor and you can build it without ever seeing an angled bracket. Further, look at the depth of detail in HR-XML vs hResume. Many resume constructs can't even be expressed in hResume. I think hResume v HR-XML Resume XML best shows why new XML grammars are better than microformats. In order to build a hResume fragment, you have to understand how microformats work. With HR-XML, you just import the XSD into an XML editor and you can build it without ever seeing an angled bracket. Further, look at the depth of detail in HR-XML vs hResume. Many resume constructs can’t even be expressed in hResume.

]]> By: Randy Charles Morin http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-7966 Randy Charles Morin Fri, 23 Nov 2007 18:32:30 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-7966 I think hResume v HR-XML Resume XML best shows why new XML grammars are better than microformats. In order to build a hResume fragment, you have to understand how microformats work. With HR-XML, you just import the XSD into an XML editor and you can build it without ever seeing an angled bracket. Further, look at the depth of detail in HR-XML vs hResume. Many resume constructs can't even be expressed in hResume. I think hResume v HR-XML Resume XML best shows why new XML grammars are better than microformats. In order to build a hResume fragment, you have to understand how microformats work. With HR-XML, you just import the XSD into an XML editor and you can build it without ever seeing an angled bracket. Further, look at the depth of detail in HR-XML vs hResume. Many resume constructs can’t even be expressed in hResume.

]]> By: Randy Charles Morin http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/comment-page-1/#comment-9837 Randy Charles Morin Fri, 23 Nov 2007 18:32:30 +0000 http://paulmwatson.com/journal/2007/11/23/extending-rss-and-microformats/#comment-9837 I think hResume v HR-XML Resume XML best shows why new XML grammars are better than microformats. In order to build a hResume fragment, you have to understand how microformats work. With HR-XML, you just import the XSD into an XML editor and you can build it without ever seeing an angled bracket. Further, look at the depth of detail in HR-XML vs hResume. Many resume constructs can't even be expressed in hResume. I think hResume v HR-XML Resume XML best shows why new XML grammars are better than microformats. In order to build a hResume fragment, you have to understand how microformats work. With HR-XML, you just import the XSD into an XML editor and you can build it without ever seeing an angled bracket. Further, look at the depth of detail in HR-XML vs hResume. Many resume constructs can’t even be expressed in hResume.

]]>