From glenn.jones at madgex.com Tue Oct 12 04:56:14 2010 From: glenn.jones at madgex.com (Glenn Jones) Date: Tue Oct 12 04:56:27 2010 Subject: [uf-discuss] UfXtract - HTML and Zipped HTML file support Message-ID: <36A319113CF910438942741C4727ADFF04F1BF52@MOBY.Clarence.local> Hi All I have just added HTML and Zipped HTML file support to http://ufxtract.com. It can be used to help build file import/export for HTML files containing microformats. UfXtract has had this feature for a few months, I have made it public in light of Facebook's new date export which also uses Zipped HTML files but with no microformat/RDF markup. As this API needs you to POST binary data, you cannot use the usual cross domain JSON calls. I am working on allowing the new cross domain XHR/AJAX calls, but for the time being I would suggest using server-side proxies to get around any "same origin policy" issues. The HTML file in any zipped file should be named index.html. The extension of zipped files is not important, the API discovers the file type by examining its contents. Glenn From junaid.nazir at superstoresearch.com Sun Oct 17 10:19:24 2010 From: junaid.nazir at superstoresearch.com (Junaid Nazir) Date: Sun Oct 17 10:26:21 2010 Subject: [uf-discuss] hCard and Internet Retailers (Shopping Contact Information) In-Reply-To: References: Message-ID: We recently sent a message to the W3 mailing list for 'public contacts', asking about what standards or guidelines were available to unify and standardize the contact information for internet retailers, as we noticed that there were significant variations in how websites would list their contact telephone numbers and email addresses - some opting to display them prominently on every page while other companies had them buried in some obscure back-pages that were not intuitively or easily accessible. In reply, Michael Hanson from Mozilla Labs helpfully pointed out the hCard microformat as the type of standard we described. However, there were some areas that we would like to clarify, as our experience in the industry indicates that we could add to the microformat standards to increase the quality and richness of the data. For example, the hCard format allows for a contact telephone number, email address and similar contact points such as instant messenger handles. However, high street stores and internet retailers will often have multiple contact points, depending on the nature of the enquiry - such as a dedicated line for sales, another for customer service and maybe even more, for technical support - and it follows a similar pattern for email addresses. There are other variations in the type of information being searched for - in our research we found that web users were commonly searching for phrases such as 'Contact ABC-Company' and 'XYZ-Company Head Office'. The head quarters telephone number for a company is usually always different from the sales and customer support lines - we are not aware of any descriptive classes in the hCard format to signify this distinction. Users are also commonly searching for 'store opening times' and the nearest store for those chain companies that have physical premises nationwide. We are actively working with the product catalogues of some 500 internet retailers through our shopping search engine database at http://www.superstoresearch.com and we have access to thousands of more contacts in the shopping and retail industry - if we have some agreed and suitable standards for the various types of contact information, we could reach out to the internet retailers and put forward the suggestion that they adopt such standards and implement them on their e-commerce sites. The benefit of such an exercise would be that the availability of standardized contact information would lead to the emergence of useful services and applications that made it easier for consumers to connect with companies and brands, while making the companies much more easy to discover via the automated spider bots of such services. There is a hCard creator script: http://microformats.org/code/hcard/creator We could contribute to the project by dedicating some of our developer resources on scripting an adapted version of the hCard creator that was optimized for internet retail businesses - to help the implementation of these standards. However, before going forward with such an idea, we would need to know if there are any suitable classes to differentiate between different telephone numbers and email addresses (sales, customer service, technical, head office, switchboard/operator) and further how to list multiple addresses for a company (head office address, local chain store differentiated by zip/post code) and if there is scope to include 'store opening times' and for e-commerce sites: if they have a 'reserve & collect' service (where you can order online, but collect in store without having to wait for a delivery). We may ask internet stores to provide such store opening times and 'reserve & collect' availability, so it would be ideal if we could agree some standards before compiling such information. Best regards, Junaid Nazir SuperStoreSearch Team -------------------------- Merchant Support http://www.superstoresearch.com | Online Shopping Guide Email: junaid.nazir@superstoresearch.com Phone: 0798 555 333 0 + + + + + SuperStoreSearch on Facebook & Twitter: http://www.facebook.com/SuperStoreSearch http://twitter.com/Guidester Buzz Shopping Blog: Interesting technology news, how to guides, tips and popular product comparisons & reviews. http://www.superstoresearch.com/buzz/ + + + + + From lists at ben-ward.co.uk Mon Oct 18 01:13:53 2010 From: lists at ben-ward.co.uk (Ben Ward) Date: Mon Oct 18 01:14:01 2010 Subject: [uf-discuss] hCard and Internet Retailers (Shopping Contact Information) In-Reply-To: References: Message-ID: <6771F8AE-3D62-4E09-B27A-7B6B620FB1CC@ben-ward.co.uk> Hi Junaid, On 17 Oct 2010, at 10:19, Junaid Nazir wrote: > However, before going forward with such an idea, we would need to know > if there are any suitable classes to differentiate between different > telephone numbers and email addresses (sales, customer service, > technical, head office, switchboard/operator) These are ?agents?. You'd have a main vcard for the company () which along with the main contact (head office or switchboard perhaps?) then contains any number of
children, each of which is another hCard, representing a different part of the company (organization-unit, or a person.) Since each agent is an hCard too, they can have phone numbers, addresses of their own. > and further how to list > multiple addresses for a company (head office address, local chain > store differentiated by zip/post code) Chain stores I think you should just represent as standalone, separate hCards. An hCard is a representation of a business card (and can be quite substantive, especially with agents) but it is not a model of an entire _business_. Different hCard for difference branches is fine. > and if there is scope to > include 'store opening times' and for e-commerce sites: if they have a > 'reserve & collect' service (where you can order online, but collect > in store without having to wait for a delivery). Opening times could, with some a bit of improvisation, be represented using hCalendar. Recurring events from vcalendar haven't really been deployed on the web as yet, so the actual presentation would need some exploration, but hCal is the way to go. Any specifics of a Reserve and Collect service is out of scope of hCard, but if it's just a particular URL or a particular phone number, you could again represent it with an hCard as an organization unit of the company. Hope that helps, Ben From mail at tobyinkster.co.uk Mon Oct 18 02:39:23 2010 From: mail at tobyinkster.co.uk (Toby Inkster) Date: Mon Oct 18 02:39:35 2010 Subject: [uf-discuss] hCard and Internet Retailers (Shopping Contact Information) In-Reply-To: References: Message-ID: <1287394763.11377.15.camel@ophelia2.g5n.co.uk> On Sun, 2010-10-17 at 18:19 +0100, Junaid Nazir wrote: > We are actively working with the product catalogues of some 500 > internet retailers through our shopping search engine database at > http://www.superstoresearch.com and we have access to thousands of > more contacts in the shopping and retail industry - if we have some > agreed and suitable standards for the various types of contact > information, we could reach out to the internet retailers and put > forward the suggestion that they adopt such standards and implement > them on their e-commerce sites. Have you looked at GoodRelations? It's an RDF-based method of marking up businesses (including stores/branches/offices), opening hours, products, services and offers. Via RDFa it can be embedded in HTML. GoodRelations is apparently being consumed by Yahoo and Google; and is being published by O'Reilly (the book publishers) and BestBuy (an electronics retailer) amongst others. http://www.heppnetz.de/projects/goodrelations/ -- Toby A Inkster From jmyers at visi.com Mon Oct 18 15:51:57 2010 From: jmyers at visi.com (Jay Myers) Date: Mon Oct 18 15:52:14 2010 Subject: [uf-discuss] hCard and Internet Retailers (Shopping Contact Information) In-Reply-To: <1287394763.11377.15.camel@ophelia2.g5n.co.uk> References: <1287394763.11377.15.camel@ophelia2.g5n.co.uk> Message-ID: <5DEDDCB0-81F6-4CCE-895C-6EAA1F921741@visi.com> Indeed, GoodRelations in RDFa or Microdata would be a good place to look. Follow this link for a sitemap index of all our stores in RDFa as an example: Http://stores.bestbuy.com/webservices/sitemap-rdfa.xml Jay Myers On Oct 18, 2010, at 4:39 AM, Toby Inkster wrote: > On Sun, 2010-10-17 at 18:19 +0100, Junaid Nazir wrote: >> We are actively working with the product catalogues of some 500 >> internet retailers through our shopping search engine database at >> http://www.superstoresearch.com and we have access to thousands of >> more contacts in the shopping and retail industry - if we have some >> agreed and suitable standards for the various types of contact >> information, we could reach out to the internet retailers and put >> forward the suggestion that they adopt such standards and implement >> them on their e-commerce sites. > > Have you looked at GoodRelations? It's an RDF-based method of > marking up > businesses (including stores/branches/offices), opening hours, > products, > services and offers. Via RDFa it can be embedded in HTML. > > GoodRelations is apparently being consumed by Yahoo and Google; and is > being published by O'Reilly (the book publishers) and BestBuy (an > electronics retailer) amongst others. > > http://www.heppnetz.de/projects/goodrelations/ > > -- > Toby A Inkster > > > > _______________________________________________ > microformats-discuss mailing list > microformats-discuss@microformats.org > http://microformats.org/mailman/listinfo/microformats-discuss > From mnot at mnot.net Fri Oct 29 12:01:29 2010 From: mnot at mnot.net (Mark Nottingham) Date: Mon Nov 29 14:21:40 2010 Subject: [uf-discuss] Fwd: RFC 5988 on Web Linking References: <20101029053328.1BE96E070C@rfc-editor.org> Message-ID: FYI. We (the DEs) are also experimenting with tracking requests for registrations: http://paramsr.us/tracker/ ...and helping people who are new to the process: http://paramsr.us/link-relation-types/ As is probably evident from looking at those pages, this site is still early-days; feedback / help welcome (as always). Cheers, Begin forwarded message: > From: rfc-editor@rfc-editor.org > Date: 29 October 2010 4:33:28 PM AEDT > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: rfc-editor@rfc-editor.org > Subject: RFC 5988 on Web Linking > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5988 > > Title: Web Linking > Author: M. Nottingham > Status: Standards Track > Stream: IETF > Date: October 2010 > Mailbox: mnot@mnot.net > Pages: 23 > Characters: 46834 > Updates: RFC4287 > > I-D Tag: draft-nottingham-http-link-header-10.txt > > URL: http://www.rfc-editor.org/rfc/rfc5988.txt > > This document specifies relation types for Web links, and defines a > registry for them. It also defines the use of such links in HTTP > headers with the Link header field. [STANDARDS-TRACK] > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce -- Mark Nottingham http://www.mnot.net/ From tantek at cs.stanford.edu Sun Oct 31 19:57:16 2010 From: tantek at cs.stanford.edu (=?UTF-8?Q?Tantek_=C3=87elik?=) Date: Mon Nov 29 15:06:38 2010 Subject: [uf-discuss] Re: country-name expected values In-Reply-To: References: <5e90f82f-be7e-4b5c-9750-6fe67b4dd0df@x42g2000yqx.googlegroups.com> Message-ID: On Sun, Oct 24, 2010 at 22:00, David Recordon wrote: > This is a good question. Was hoping the answer was an easy "vCard spec'd X" > but it seems that neither vCard or hCard actually define country-name. > Tantek, thoughts? country-name in vCard, and in hCard reflects what people visibly publish on the web. In this case, the actual full names of countries, or abbreviations thereof, e.g. USA United States United States of America Canada England UK United Kingdom etc. for further questions regarding hCard, please feel free to follow-up on the microformats discuss list (cc'd). http://microformats.org/mailman/listinfo/microformats-discuss/ Thanks, Tantek -- http://tantek.com/ - I made an HTML5 tutorial! http://tantek.com/html5