Re: [uf-discuss] ufXtract - new microformats parser
Awesome work, Glenn. I like the way results are return (specially in XML, for server-side). BUT... I just tested it on my blog and I think there might be an issue with charsets different than utf-8. I'm using iso-8859-1, by the way. http://lab.backnetwork.com/ufXtract/?url=http%3A%2F%2Fandr3.net%2Fblog&format=hcard&output=xml&callback= Cheers, André Luís ps: it might be my problem, but still, thought I'd let you know. Parsers should be as robust as possible, right? hehe On Nov 26, 2007 12:58 AM, Guillaume Lebleu <[EMAIL PROTECTED]> wrote: > Glenn Jones wrote: > > It has been built from the ground up to take configuration > > objects which allow the parsing of different microformats or POSH > > patterns. > Great job Glenn, > I was wondering what the configuration objects look like. Do you use a > grammar for each uf expressed? > Thank you, > Guillaume > > > ___ > microformats-discuss mailing list > microformats-discuss@microformats.org > http://microformats.org/mailman/listinfo/microformats-discuss > ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using namespace
Le 23 nov. 2007 à 23:14, Tatsuya Noyori a écrit : I would like to suggest that microformats use namespace like the following example. I think microformats need namespace to ensure interoperability. You can use RDFa, that will make it possible http://www.w3.org/TR/xhtml-rdfa-primer/ RDFa Bookmarklet http://www.w3.org/2001/sw/BestPractices/HTML/rdfa-bookmarklet/ RDFa Extractor http://torrez.us/rdfa/ RDFa Implementations http://rdfa.info/rdfa-implementations/ -- Karl Dubost - W3C http://www.w3.org/QA/ Be Strict To Be Cool ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] ufXtract - new microformats parser
Glenn Jones wrote: It has been built from the ground up to take configuration objects which allow the parsing of different microformats or POSH patterns. Great job Glenn, I was wondering what the configuration objects look like. Do you use a grammar for each uf expressed? Thank you, Guillaume ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] ufXtract - new microformats parser
On 25 Nov 2007, at 18:09, Glenn Jones wrote: http://lab.backnetwork.com/ufXtract/ Great work, Glenn! drew. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] ufXtract - new microformats parser
Hi All I have being work hard on a new microformats parser (ufXtract) to help explore the real world issues of creating portable social networks. Although I have previously designed a number spiders that can find the most common hCard and XFN structures, this is my first full blown parser. It has been built from the ground up to take configuration objects which allow the parsing of different microformats or POSH patterns. It was important that I could parse more general patterns such as the joint hCard-XFN being promoted for use with friend's lists. http://lab.backnetwork.com/ufXtract/ After some further testing I am going to start to produce a number of portable social network demo's and posts. This should also provide others with experimental API's. By sharing this early work I hope in some way to add to the important technical and architectural discussions that are taking place. I have already added hCard-XFN, rel="me", rel="next" and hAtom to the parser. These are the four cornerstone microformats/patterns required to gather profile and content from other social networks. Although for technical/speed reasons ufXtract is currently only parsing the hEntry sub-element of hAtom. The component also contains extendable output options, so far, I have built a simple text format for debugging, JSON and XML for building services. For the more technically minded ufXtract is a .net component written in c#. It uses a combination of DOM structures and xPaths. It can typically parse a page in 50-200ms. At the moment, I am building a test suite to fine tune the components' compliancy. It still has some small issues with most of the compound microformats, which I am trying to address. If you have any comments or want to point out any issues, please give me as much feedback as possible. Thanks Glenn Jones www.glennjones.net ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
On 25 Nov 2007, at 11:34, Philip Tellis wrote: On 25/11/2007, Tatsuya Noyori <[EMAIL PROTECTED]> wrote: I changed to . Is this correct? AFAIK, tags need some text inside. Well, to be valid an Anchor needs to be explicitly closed, since self- closing cannot be used in HTML. Inner text _can_ be omitted, but until we've got some more feedback on the assistive technology implications I'd consider it ill advisable. And yes, such feedback is in the works following the include-pattern update. Ben ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
Thank you for your help. I understand a little. I will see the details. Also, I reconsider my suggestion. -- Tatsuya Noyori (^o^)/ ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
2007/11/25, Tatsuya Noyori <[EMAIL PROTECTED]>: > I changed to . Is this correct? --- there is another option. In HTML the element allows for a profile attribute. This profile attribute is a list of URLs that further define terms in the page. We have created an XMDP document to describe an hCard. http://www.w3.org/2006/03/hcard As for your examples, in the prose of the specification, we state that the terms are case-specific because CSS is case-specific, so class='tel" is valid, but class="TeL" is not. http://microformats.org/wiki/hcard-issues 2005-07-23 raised by DanConnolly Q. Are class names case sensitive or not? hcard says "If names in the source schema are case-insensitive, then use an all lowercase equivalent." A: ACCEPTED FAQ. Class names are case sensitive per the HTML4 specification. Hence hCard explicitly specifies the case of class name to use for source schema names that are case-insensitive. The values: Home, home, and HOME are all valid: from: http://microformats.org/wiki/hcalendar-faq Is the list of possible types for an ADR and TEL case sensitive? No, enumerated values are case-INsensitive, therefore Home, home, HOME, etc are all equivalent I hope this helps, much of the automated schema parsing is solved in text in the spec not in a format document. -brian -- brian suda http://suda.co.uk ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
On 25/11/2007, Tatsuya Noyori <[EMAIL PROTECTED]> wrote: > I changed to . Is this correct? AFAIK, tags need some text inside. -- hello world ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
Hello David, Thank you for your comments. I revised the following example. http://microformats.org/2007/hcard.rng"/> home +1.415.555.1212 I changed to . Is this correct? -- Tatsuya Noyori (^o^)/ ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
On Nov 25, 2007 12:25 AM, Tatsuya Noyori <[EMAIL PROTECTED]> wrote: > > http://microformats.org/2007/hcard.rng"; /> > home > +1.415.555.1212 > > > The example is added " href="http://microformats.org/2007/hcard.rng"; />" to original hcard to > declare using microschema. LINK is only valid inside of HEAD, not BODY so this is invalid (X)HTML [1]. Regards, etc... [1] http://www.w3.org/TR/REC-html40/struct/links.html#h-12.3 -- David Janes Founder, BlogMatrix http://www.blogmatrix.com http://blogmatrix.blogmatrix.com ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
Hi Tantek, Thank you for your questions and comments. I think the following example is valid. home +1.415.555.1212 But, I am not sure whether the following examples are valid. HOME +1.415.555.1212 --- home +1.415.555.1212 --- home +1.415.555.1212 Are these examples valid? I am not sure. This is the problem that I would like to solve. And, the aim of microschema is not to validate whole XML but to validate a part of XML. The way of the validation is as follows: 1. search 2. retrieve the parent element of this and the child elements of the parent element. 3. retrieve the schema linked to "..". 4. validate the xml retrieved by the schema retrieved. I think, if microformats use microschema, the interoperability of microformats will be improved. Best regards, -- Tatsuya Noyori (^o^)/ ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] using microschema
On 11/24/07 9:25 PM, "Tatsuya Noyori" <[EMAIL PROTECTED]> wrote: > I would like to suggest microschema to improve interoperability of > microformats. Hi Tatsuya, There are two general areas of problems that your suggestion. The first is, what is the real world interoperability problem that you are trying to solve? Do you have test cases that have been demonstrated to fail in specific implementations? Do you have analysis that demonstrates that such problems stem from a lack of an explicit typed schema? Lacking that, it is not logical to conclude that a schema (micro or otherwise) would help improve interoperability. The second problem is that in practice, explicit schemas do not represent all (often not even most) of the semantics of a specific format. For example, the HTML4 DTDs contain a mere fraction of the constraints and semantics expressed by the HTML4 specification. A validator that only checks the rules expressed in the HTML DTD will fail to check numerous assertions and requirements made in the specification itself. This is the schema incompleteness problem. In short, having a set of rules from a framework (such as those expressed by a schema like a DTD) is not only in practice insufficient, but serves to give a false sense of completeness of description. Thus with microformats we eschew trying to solve the general schema problem (others are trying much harder for much longer on that problem - e.g. XML Schema etc., and failing in practice - i.e. usage on the Web) for simple dictionaries instead. There has been some value demonstrated in some scenarios (e.g. reading microformats into an RDF store, either directly or thru a GRDDL transform) to at least disambiguate the use of vocabulary, and back the terms used with URLs. Thus we have XMDP (XHTML Meta Data Profiles) which is sufficient to define terms and provide a URL for each. Thanks, Tantek ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
