Re: suggestion of new element and attribute `greyarea`

Oh, Sorry, I didn't reply to mail list...

Actually, i think we all met such case when using facebook or app which has
friend feature.
As a technique guy, you may have both technical friends and non-technical
friends. Sometimes we may publish our life that both tech and non-tech can
all understand; And sometimes, just the technical stuff, and when in this
case, i think those non-technical guys will prefer avoid it.

In nowadays, the problem is not the lack of data, the problem is useful
data is covered by huge un-useful data. And when doing so, we can at least
hide something we may don't want to see.


Yarco


On Wed, Oct 21, 2015 at 10:29 AM, Wang Yarco <yarco.wang@gmail.com> wrote:

> >> I have serious reservations about who would set and enforce the
> policies on specific types of content.
> And this is not something strict rules, just like the name `grey area`.
> The readers still have rights to see real content.
> But forcing everyone to read is actually the action of `enforcing the
> policies`.
>
>
> On Wed, Oct 21, 2015 at 10:24 AM, Wang Yarco <yarco.wang@gmail.com> wrote:
>
>> >> I have serious reservations about who would set and enforce the
>> policies on specific types of content.
>> Of cause, the editor who own the resource.
>>
>> >> To that end I believe, currently, that whether to guard or censor
>> those materials should remain within the scope of the many available tools
>> for that purpose.
>> There 's no good resolution on this, except every website add such
>> css/script has such functions.
>> Just an example, if i'm in facebook, i have friends those may be male and
>> female. And i want to publish my naked body to discuss healthy with my male
>> friends. But for female, they may feel ugly.
>> One solution is trying to group them into two groups. But if you have
>> hundreds male friends and female friends, add each to the group is
>> obviously unacceptable.
>> I think such case can happen in anywhere in internet. `The photo of Death
>> of Alan Kurdi` is just a case in real world.
>>
>>
>> On Wed, Oct 21, 2015 at 9:37 AM, John Teague <ts@themesurgeons.com>
>> wrote:
>>
>>> While I appreciate your opinion about issues of guarding content from
>>> those who may find certain material offensive, I don't believe that control
>>> over the display of that content should be considered in the HTML5 space
>>> itself. I have serious reservations about who would set and enforce the
>>> policies on specific types of content. To that end I believe, currently,
>>> that whether to guard or censor those materials should remain within the
>>> scope of the many available tools for that purpose.
>>>
>>> Best to you and yours,
>>>
>>> John
>>>
>>> John Teague
>>> Founder
>>> Theme Surgeons LLC
>>> john@themesurgeons.com
>>> https://themesurgeons.com
>>>
>>> On Twitter <https://twitter.com/themeSurgeon> | Google+
>>> <https://plus.google.com/+ThemesurgeonsWordPress/>
>>>
>>> On Tue, Oct 20, 2015 at 7:58 PM, Wang Yarco <yarco.wang@gmail.com>
>>> wrote:
>>>
>>>> There are different types of resources in internet, from article to
>>>> video. Normally, when we publish a resource, we suppose it is public in
>>>> some area (world wide or your friend circle in Facebook) and useful to
>>>> others.
>>>>
>>>> But whether the resource is harmful or harmless is actually determined
>>>> by the guy who received the resource. For example:
>>>>
>>>> The photo of Death of Alan Kurdi (
>>>> https://en.wikipedia.org/wiki/Death_of_Alan_Kurdi )
>>>>
>>>> Someone may feel they are touched; and others may feel un-comfortable —
>>>> and hard to explain to their children. Those are the informations been
>>>> pushed to the readers without considering you like it or not.
>>>>
>>>> There should be a new element/attribute `greyarea` in html5 (or any
>>>> other representation) for this target. It should work like this:
>>>>
>>>> 1. For pieces of text:
>>>>
>>>> …other text...<greyarea title=“these text you may/may not want to
>>>> read…”>unknown TEXT</greyarea>…other text...
>>>>
>>>> Can be viewed as:
>>>>
>>>> …other text...*these text you may/may not want to read…*…other text...
>>>>
>>>> The italic text here may actually be highlighted in real. If the guy
>>>> exactly wants to read it, he clicks the highlighted text, then the text
>>>> will be extended to full paragraph.
>>>> If omit the title attribute here, the text should default to use mosaic
>>>> (if we have mosaic character in unicode) with some length.
>>>>
>>>>
>>>> 2. For block of text or multi-media:
>>>>
>>>> …other elements…<div … greyarea=“…the title…”>unknown TEXT</div>…other
>>>> elements...
>>>>
>>>> OR
>>>>
>>>> …other elements…<img … greyarea=“…the title…” />…other elements...
>>>>
>>>>
>>>> Block of texts have the same effects as in previous description;
>>>>
>>>> Multi-media element may show a mosaic image with the text set
>>>> in greyarea. If omit the value, it just shows the mosaic image. (The
>>>> algorithm of mosaic can be defined by the application you are using)
>>>>
>>>>
>>>> 3. Hierarchical structure
>>>>
>>>> If a greyarea block includes other greyarea (whether it is another
>>>> greyarea block or attribute in some elements), for simple usage, when click
>>>> the parent greyarea block, sub-greyarea blocks should also be extended..
>>>>
>>>> Original Posted:
>>>> https://www.linkedin.com/pulse/html5-suggestion-new-element-attribute-greyarea-yarco-wang
>>>>
>>>
>>>
>>
>