From brian.suda at gmail.com Fri Sep 15 07:02:37 2006
From: brian.suda at gmail.com (Brian Suda)
Date: Fri Sep 15 07:02:40 2006
Subject: [uf-dev] Re: [uf-discuss] Two include-pattern questions
In-Reply-To: <21e523c20609150654r6ab17153o10effff07d2a05e3@mail.gmail.com>
References: <21e523c20609150654r6ab17153o10effff07d2a05e3@mail.gmail.com>
Message-ID: <21e770780609150702u2216f07emade0dab3704fa152@mail.gmail.com>
there are also a few other outstanding issues on how/what is exactly included.
Senario I
brian suda
my hcard
This senario takes id="var1" and takes that branch of the tree and
inserts it as a CHILD of the 'a' element. Therefore you would extract
the vcard with an fn.
Senario II
brian suda
The second senario id="var2" REPLACES the 'a' element, therefore, you
need to have your class values as children of id="var2"
Obviously, there are issues with both. along with things like this:
Senario III
brian suda
what happens here? it depends on if the included text is a child, or
replaces, and/or if we want to allow something like this?
I suggest that if this is going to get more technical, we take it to
the dev-list.
-brian
On 9/15/06, David Janes wrote:
> I'm working on an implementation in Python and I have a couple of
> questions that affect the complexity of the implementation.
>
> (1)
> Should all microformat parsers be looking for class="include" in any
> (non-rel) microformat, or is it a universal option that will always be
> there?
>
> (2)
> Are multiple levels of including allowed, or rather since it's not
> forbidden, _should_ it be allowed?
>
> Regards, etc...
> David
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss@microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>
--
brian suda
http://suda.co.uk
From davidjanes at blogmatrix.com Fri Sep 15 07:14:14 2006
From: davidjanes at blogmatrix.com (David Janes)
Date: Fri Sep 15 07:14:16 2006
Subject: [uf-dev] Re: [uf-discuss] Two include-pattern questions
In-Reply-To: <21e770780609150702u2216f07emade0dab3704fa152@mail.gmail.com>
References: <21e523c20609150654r6ab17153o10effff07d2a05e3@mail.gmail.com>
<21e770780609150702u2216f07emade0dab3704fa152@mail.gmail.com>
Message-ID: <21e523c20609150714q5955ed47t701766ab78036b4f@mail.gmail.com>
Dev list it is!
I'm going to plug at the implementation for awhile with the simplest
assumptions and see where that takes me.
My superficially observations -- ... I just typed a bunch of stuff,
didn't like it, and deleted it ... is that this is a very difficult
problem ;-)
Regards, etc...
David
On 9/15/06, Brian Suda wrote:
> there are also a few other outstanding issues on how/what is exactly included.
>
> Senario I
>
> brian suda
>
>
> my hcard
>
>
> This senario takes id="var1" and takes that branch of the tree and
> inserts it as a CHILD of the 'a' element. Therefore you would extract
> the vcard with an fn.
>
> Senario II
>
>
> brian suda
>
>
>
>
>
>
> The second senario id="var2" REPLACES the 'a' element, therefore, you
> need to have your class values as children of id="var2"
>
> Obviously, there are issues with both. along with things like this:
>
> Senario III
>
> brian suda
>
>
>
>
>
> what happens here? it depends on if the included text is a child, or
> replaces, and/or if we want to allow something like this?
>
> I suggest that if this is going to get more technical, we take it to
> the dev-list.
From brian.suda at gmail.com Fri Sep 15 07:27:12 2006
From: brian.suda at gmail.com (brian suda)
Date: Fri Sep 15 07:28:11 2006
Subject: [uf-dev] Re: [uf-discuss] Two include-pattern questions
In-Reply-To: <21e523c20609150714q5955ed47t701766ab78036b4f@mail.gmail.com>
References: <21e523c20609150654r6ab17153o10effff07d2a05e3@mail.gmail.com> <21e770780609150702u2216f07emade0dab3704fa152@mail.gmail.com>
<21e523c20609150714q5955ed47t701766ab78036b4f@mail.gmail.com>
Message-ID: <450AB840.4010402@gmail.com>
I don't think this is a difficult problem. X2V's implementation differs
slightly from the wiki page (which isn't all that clear - only from the
examples - which are open to being amended).
The tricky thing is that if you do NOT force the included data to be a
child then you could end-up with valid, yet invalid hCards.
now that is invalid because fn has to be a child of vcard, but because
there is an include that REPLACES the 'a' with the id-ref, this is now
valid (expanded it might look like this)
What X2V currently does is "match" the id to the href and include the
children, so you get some thing like:
which is invalid HTML due to nested 'a', but then it misses any class
values that were encoded on the node with the id. (in this example the
class="fn" didn't come along)
This is just a matter of clarifying the wiki page, and it hasn't been a
high-priority. X2V implements it the second way, (i think) Tails does it
the first - not sure about hKit or the others?
I hope all that makes sense?
-brian
David Janes wrote:
> Dev list it is!
>
> I'm going to plug at the implementation for awhile with the simplest
> assumptions and see where that takes me.
>
> My superficially observations -- ... I just typed a bunch of stuff,
> didn't like it, and deleted it ... is that this is a very difficult
> problem ;-)
>
> Regards, etc...
> David
>
> On 9/15/06, Brian Suda wrote:
>> there are also a few other outstanding issues on how/what is exactly
>> included.
>>
>> Senario I
>>
>> brian suda
>>
>>
>> my hcard
>>
>>
>> This senario takes id="var1" and takes that branch of the tree and
>> inserts it as a CHILD of the 'a' element. Therefore you would extract
>> the vcard with an fn.
>>
>> Senario II
>>
>>
>> brian suda
>>
>>
>>
>>
>>
>>
>> The second senario id="var2" REPLACES the 'a' element, therefore, you
>> need to have your class values as children of id="var2"
>>
>> Obviously, there are issues with both. along with things like this:
>>
>> Senario III
>>
>> brian suda
>>
>>
>>
>>
>>
>> what happens here? it depends on if the included text is a child, or
>> replaces, and/or if we want to allow something like this?
>>
>> I suggest that if this is going to get more technical, we take it to
>> the dev-list.
> _______________________________________________
> microformats-dev mailing list
> microformats-dev@microformats.org
> http://microformats.org/mailman/listinfo/microformats-dev
>
From davidjanes at blogmatrix.com Sat Sep 16 00:49:04 2006
From: davidjanes at blogmatrix.com (David Janes)
Date: Sat Sep 16 00:49:07 2006
Subject: [uf-dev] hResume question
Message-ID: <21e523c20609160049x63ece51ci1644bbd26ced58d9@mail.gmail.com>
hResume says that you express a job title by embedding a hCard [1].
But there is no special class attribute to distinguish between the
hCard and any other within that experience unit (for example, if I
talked about the people I was working for using hCards also).
Issue?
Regards, etc...
David
[1] http://microformats.org/wiki/hresume#Job_Titles
From ryan at technorati.com Mon Sep 18 13:58:17 2006
From: ryan at technorati.com (Ryan King)
Date: Mon Sep 18 13:58:20 2006
Subject: [uf-dev] hAtom xslt merged
Message-ID:
I've merged Robert Bachmann, et al's work on hAtom2Atom.xsl into our
X2V and tests repositories.
Here's the basic method I used.
1. Use tailor to export and convert the SVN repo to a mercurial repo
[1].
2. go to x2v repo and pull (with -f) from the tailor-generated repo.
The -f is needed because the repos are unrelated (ie, they share 0
changesets).
3. branch merge
4. remove the stuff we don't need. I removed the tests from x2v and
the xslt's from 'tests'.
5. repeat 2-4 for the tests repo, but this time deleting the other
files.
Hopefully this will help some collaboration.
Robert Bachmann now has push access to x2v and tests.
-ryan
[1] Tailor config file I used, YMMV:
[DEFAULT]
verbose = True
[project]
target = hg:target
start-revision = INITIAL
root-directory = /Users/ryan/microformats
state-file = tailor.state
source = svn:source
subdir = h2v/
[hg:target]
[svn:source]
module = /trunk/
repository = http://rbach.priv.at/repos/hatom/hatom2atom.xsl/
From ryan at technorati.com Mon Sep 18 14:04:23 2006
From: ryan at technorati.com (Ryan King)
Date: Mon Sep 18 14:04:25 2006
Subject: [uf-dev] hResume question
In-Reply-To: <21e523c20609160049x63ece51ci1644bbd26ced58d9@mail.gmail.com>
References: <21e523c20609160049x63ece51ci1644bbd26ced58d9@mail.gmail.com>
Message-ID: <4CA18C90-6DD2-4138-BA77-61696C2A7BF0@technorati.com>
On Sep 16, 2006, at 12:49 AM, David Janes wrote:
> hResume says that you express a job title by embedding a hCard [1].
> But there is no special class attribute to distinguish between the
> hCard and any other within that experience unit (for example, if I
> talked about the people I was working for using hCards also).
>
> Issue?
Perhaps. Do you have an example of where you or someone else has or
would like to use this?
-ryan
From davidjanes at blogmatrix.com Mon Sep 18 17:20:53 2006
From: davidjanes at blogmatrix.com (David Janes)
Date: Mon Sep 18 17:20:57 2006
Subject: [uf-dev] hResume question
In-Reply-To: <4CA18C90-6DD2-4138-BA77-61696C2A7BF0@technorati.com>
References: <21e523c20609160049x63ece51ci1644bbd26ced58d9@mail.gmail.com>
<4CA18C90-6DD2-4138-BA77-61696C2A7BF0@technorati.com>
Message-ID: <21e523c20609181720v718dc23ek36880a2894a75b38@mail.gmail.com>
Sure -- just randomly googling for "resume worked for professor" I
found this [1]. She talks quite a bit about which professors she
worked for, each potentially to be marked up with a hCard.
Observations:
- text of the the experience should be wrapped in "summary" element
(from hCalendar)
- one could (also) make summaries opaque to finding the title hCard
for the experience, in which case I can't think of a place where there
would be an issue
Regards, etc...
David
[1] http://sitemaker.umich.edu/krisrich/resume
On 9/18/06, Ryan King wrote:
> On Sep 16, 2006, at 12:49 AM, David Janes wrote:
>
> > hResume says that you express a job title by embedding a hCard [1].
> > But there is no special class attribute to distinguish between the
> > hCard and any other within that experience unit (for example, if I
> > talked about the people I was working for using hCards also).
> >
> > Issue?
>
> Perhaps. Do you have an example of where you or someone else has or
> would like to use this?
>
> -ryan
> _______________________________________________
> microformats-dev mailing list
> microformats-dev@microformats.org
> http://microformats.org/mailman/listinfo/microformats-dev
>