[Bug 6774] <mark> element: restrict insertion by other servers


--- Comment #16 from Nick Levinson <Nick_Levinson@yahoo.com>  2009-07-01 08:44:36 ---
I propose 2 alternatives for section 4.6.7:

-- Edit the example that depends on knowing the user's search string (the
"kitten" explanation) to require that the markup be performed only inside the
original page owner's server. Replace "and the server knew" with "and the
original page owner's server knew". The next mention of "the server" should
stay as it is, as it would inherit the constraint on the first mention. Also,
allow per-page opt-in by the page author via a meta tag to permit anyone else
to add mark tags anywhere else. Without an opt-in on a page, other servers thus
could not legally add the markup to that page. Section 4.6.7 does not need more
wording to accommodate this opt-in, because sec. 4.2.5 (meta) and the
MetaExtensions Wiki will be sufficient, and I can review the Wiki for relevant

-- Or delete the example (the line explaining it and the "kitten" text).

Either of these will preserve mark as semantically more specific and thus often
more useful than span, which remains as a general fallback tag. The definition
and other examples for mark thus remain intact.

The main explanatory paragraph for sec. 4.6.7, before the examples, may remain
as it is, because "likely relevance" does not convey what "knew" does.
"[L]ikely relevance" can be guessed before any specific user ever approaches a
computer to access any page, with the guess applied by the original page
author, whereas "[knowledge]" of a user's specific search must follow a search,
which is not the page author's time frame. With the kitten case neutralized or
deleted, the main paragraph won't have the adverse effect.

Thank you.


Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 1 July 2009 08:44:51 UTC