On May 25, 2006, at 5:25 PM, Scott Reynen wrote:
On May 25, 2006, at 10:52 AM, Tantek Çelik wrote:
What problem is this solving?
What human readable content is this marking up?
This is sounding off-topic for microformats. Am I missing something?
I don't think it's about publishing microfor
Pardon what may sound like a late hit, but please let me point out
that the most
low-level and hence most useful of these random-access URIs (leading to
an un-ID-ed point in the cited page) is now available in running code
to all of us.
http://lists.w3.org/Archives/Public/wai-xtech/2005Sep/0
On 5/25/06 10:46 AM, "Scott Reynen" <[EMAIL PROTECTED]> wrote:
> On May 25, 2006, at 12:20 PM, Tantek Çelik wrote:
>
>> There is already an easy solution that works for publishers (ID).
>>
>> Inventing a more complex solution will not result in more adoption.
>
> My understanding of "HyperScope
On May 25, 2006, at 12:20 PM, Tantek Çelik wrote:
There is already an easy solution that works for publishers (ID).
Inventing a more complex solution will not result in more adoption.
My understanding of "HyperScope" would accomplish a bit more than ID
attributes could. While a standard me
Ben,
I think you provide an excellent summary.
On 5/25/06 10:00 AM, "Ben Ward" <[EMAIL PROTECTED]> wrote:
> Tantek Çelik wrote:
>> But discussions of extending URL/URI semantics for addressing bits of
>> information? I'm not sure that actually has much bearing on parsing
>> microformats. But l
On May 25, 2006, at 1:00 PM, Ben Ward wrote:
Tantek Çelik wrote:
But discussions of extending URL/URI semantics for addressing bits of
information? I'm not sure that actually has much bearing on parsing
microformats. But like I said, perhaps I am missing something.
I don't know if my inter
On 5/25/06, Ben Ward <[EMAIL PROTECTED]> wrote:
Personally, I
wouldn't think it unreasonable to have 'microformats must have an ID' as
part of each spec.
Note that requiring id's complicates authoring (first, you gotta come up
with one, and unless you pick very wisely, you risk conflicts when
Tantek Çelik wrote:
But discussions of extending URL/URI semantics for addressing bits of
information? I'm not sure that actually has much bearing on parsing
microformats. But like I said, perhaps I am missing something.
I don't know if my interpretation brings this on topic or just clarifie
On 5/25/06 9:25 AM, "Scott Reynen" <[EMAIL PROTECTED]> wrote:
> On May 25, 2006, at 10:52 AM, Tantek Çelik wrote:
>
>> What problem is this solving?
>>
>> What human readable content is this marking up?
>>
>> This is sounding off-topic for microformats. Am I missing something?
>
> I don't thi
On May 25, 2006, at 10:52 AM, Tantek Çelik wrote:
What problem is this solving?
What human readable content is this marking up?
This is sounding off-topic for microformats. Am I missing something?
I don't think it's about publishing microformats, but rather parsing
microformats. That may
What problem is this solving?
What human readable content is this marking up?
This is sounding off-topic for microformats. Am I missing something?
Thanks,
Tantek
On 5/25/06 8:46 AM, "Chris Messina" <[EMAIL PROTECTED]> wrote:
> Ooo.. that would be cool... I might sound dumb by saying this, bu
Ooo.. that would be cool... I might sound dumb by saying this, but
would that be like a RESTian way of accessing data in a microformatted
page?
Chris
On 5/25/06, Dimitri Glazkov <[EMAIL PROTECTED]> wrote:
So, this is like W3 Selectors for URLs?
:DG<
On 5/25/06, Scott Reynen <[EMAIL PROTECTED]
So, this is like W3 Selectors for URLs?
:DG<
On 5/25/06, Scott Reynen <[EMAIL PROTECTED]> wrote:
On May 25, 2006, at 3:04 AM, Chris Messina wrote:
> how do we create URIs for partial bits of data like a word
> or hcard in the middle of a paragraph?
>
> http://www.eekim.com/blog/tech/hyperscope
On May 25, 2006, at 3:04 AM, Chris Messina wrote:
how do we create URIs for partial bits of data like a word
or hcard in the middle of a paragraph?
http://www.eekim.com/blog/tech/hyperscope/hyperscopeuri.html
I'm not sure that's really the question being asked by Eugene. It
sounds like the
On 5/25/06, Ryan King <[EMAIL PROTECTED]> wrote:
They're called "fragment identifiers" and they're common practice
already in (X)HTML:
It's often convenient to be able to point to bits of a document that
haven't been annotated with fragment identifiers.
--
Christopher St. John
http://artofsy
They're called "fragment identifiers" and they're common practice
already in (X)HTML:
http://www.w3.org/TR/REC-html40/intro/intro.html#h-2.1.2
-ryan
On May 25, 2006, at 9:04 AM, Chris Messina wrote:
Eugene has posted an interesting issue that might benefit from some mF
insight... how do we
At 01:04 -0700 25.05.2006, Chris Messina wrote:
Eugene has posted an interesting issue that might benefit from some mF
insight... how do we create URIs for partial bits of data like a word
or hcard in the middle of a paragraph?
Referencing particular document fragments within an XML document
(
Eugene has posted an interesting issue that might benefit from some mF
insight... how do we create URIs for partial bits of data like a word
or hcard in the middle of a paragraph?
http://www.eekim.com/blog/tech/hyperscope/hyperscopeuri.html
Chris
___
m
18 matches
Mail list logo
