Re: [whatwg]

[Ian Hickson]

On Mon, 24 Oct 2005, Stefan Leitich wrote:
> 
> The association I had while reading your problem description and 
> solution idea is Xlink. It would provide all your required functionality 
> and is more generic than your approach and basically lets associate more 
> than a single origin and a single destination for a link.
> 
> Did I get it wrong? Wouldn't it be a possibility?What do you think?

Could you show us an example of how that would work?

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Re: [whatwg]

[Jasper Bryant-Greene]

On Mon, 2005-10-24 at 21:35 +0200, Stefan Leitich wrote:
> Hi!
> 
> I stumbled about this thread and started reading ... I must admit I 
> haven't read all postings so please excuse me if my comment was in some 
> kind already mentioned.
> 
> The association I had while reading your problem description and 
> solution idea is Xlink. It would provide all your required functionality 
> and is more generic than your approach and basically lets associate more 
> than a single origin and a single destination for a link.
> 
> Did I get it wrong? Wouldn't it be a possibility?What do you think?

It could be a possibility, but it would only be possible in XML
documents, would it not?

-- 
Jasper Bryant-Greene
General Manager
Album Limited

e: [EMAIL PROTECTED]
w: http://www.album.co.nz/
p: 0800 4 ALBUM (0800 425 286) or +64 21 232 3303
a: PO Box 579, Christchurch 8015, New Zealand

Re: [whatwg]

[Stefan Leitich]

Hi!

I stumbled about this thread and started reading ... I must admit I 
haven't read all postings so please excuse me if my comment was in some 
kind already mentioned.


The association I had while reading your problem description and 
solution idea is Xlink. It would provide all your required functionality 
and is more generic than your approach and basically lets associate more 
than a single origin and a single destination for a link.


Did I get it wrong? Wouldn't it be a possibility?What do you think?

cheers
sl

Ian Hickson wrote:


One of the patterns I've seen a lot while looking at big sites is this:

   Foo 

...where "redirect" is a CGI script that records that the user followed 
the link, and that then redirects the user to the real page (potentially 
setting a cookie in the process).


This is used for four main reasons:

1. Improving sites, by getting data regarding how users use the site.

2. Keeping track of which adverts were clicked on, for book-keeping.

3. Improving services, e.g. by offering a number of options, checking 
   which the user picked, and making that one be the first on the list 
   the next time the user uses the service.


4. Uniquely identifying and tracking a user for evil purposes.

Sometimes more than one of the above is done, e.g. clicking on adverts 
sometimes informs the publisher and the advertiser before moving the user 
to the real destination.


The problem at the moment is that the redirect mechanism obscures the 
eventual target URI. It would be good to have the target URI separate 
from the tracking URIs, so that the UA can show each of them separately in 
the UI, indicating the user who is getting told what.


Doing this would also allow the UA to easily turn off the pinging thing 
for users who are worried about point 4 above.


Bearing the above in mind, I've added a section to the  element that 
describes a ping="" attribute. The URIs given in this attribute would be 
followed when the user clicks the link, thus getting around the problems 
listed above.


Now, because of number 4 above, I'm guessing this is going to be 
controversial, which is why I'm calling this out explicitly (as opposed to 
waiting til I've filled in all the TBW sections and then just asking for a 
general review, since people might miss it if I did that).


Thoughts? Is it evil?

  http://whatwg.org/specs/web-apps/current-work/#ping

 

[whatwg] http://whatwg.org/demos/repeat-02/results.xml

[Anne van Kesteren]

Could you please change the namespace to "http://n.whatwg.org/formdata";. Perhaps
you also want to note at http://n.whatwg.org/formdata that it can be used for
seeding the form with initial values as well.

Cheers,

Anne


-- 
Anne van Kesteren

[whatwg] http://whatwg.org/demos/repeat-01/

[Anne van Kesteren]

Can this demo be fixed? The button named "add" needs to have a template
attribute with the literal value of "player".

Furthermore, the DOCTYPE should be changed to "".

Cheers,

Anne


-- 
Anne van Kesteren

Re: [whatwg]

[ROBO Design]

On Mon, 24 Oct 2005 06:45:19 +0300, Ian Hickson <[EMAIL PROTECTED]> wrote:


On Mon, 24 Oct 2005, Lachlan Hunt wrote:

<...>


Oops.


<...>


Heh. So I had actually written that, then deleted the word "improve" to
find a better word (improve from what?), then forgot that I hadn't
finished the sentence. I suck.

  It is possible to track users without this feature, but authors are
  urged to use the |ping| attribute so that the user agent can optimise
  the user experience.

...is what I have now. If someone can find a better way of phrasing that
please let me know. It's what I mean, but it sounds kooky.



My version:

   It is possible to track users without this feature, but authors are
   encouraged to use the |ping| attribute so that the user agent can  
improve

   the user experience.

Urged is ... a bit too "pushy". Also, "optimise" is not the appropriate  
word. I consider Lachlan's suggestion better: "improve", because that's  
what actually happends (improvement, not optimisation).


--
http://www.robodesign.ro
ROBO Design - We bring you the future

Re: [whatwg] [wf2] 2.3. Changes to existing controls

[Anne van Kesteren]

Quoting Ian Hickson <[EMAIL PROTECTED]>:

# so that if the value content attribute is not specified then
# the value DOM attribute (and the value used for submission
# when the controls are checked) is "on".

Could you perhaps add that setting the value content attribute to the
empty string must not be considered differently from setting the value
content attribute?

Note that in order to do that you would also have to change section 2.4
which states that setting value to the empty string means "no value
selected". That would result in the value used for submission being "on"
which is not what user agents currently do, or are supposed to do.
value="" should not result in the value DOM attribute being "on", but
"".


Your two requests here seem to contradict each other. Could you clarify?


They do? How? You have to add that note because that is what UAs do and after
that you have to change section 2.4 so that the note does not make your
specification contradicting.



# Whitespace must also not be trimmed from any other attributes
# (e.g. the value attribute).

Could you add a note that there is some form of normalization applied to
these attributes in XML documents as described here:
. This could be helpful and
would prevent confusion.


That XML rule only applies to validating parsers and to parsers exposed to
internal subsets, IIRC.


Let me quote:

# Before the value of an attribute is passed to the application
# or checked for validity, the XML processor MUST normalize the
# attribute value by applying the algorithm below

(Also, internal subsets are required to be supported by XML parsers.)


--
Anne van Kesteren