- From: Hugh McGuire <hugh@rebus.foundation>
- Date: Mon, 31 Jul 2017 11:10:40 -0400
- To: Ivan Herman <ivan@w3.org>
- Cc: Matt Garrish <matt.garrish@gmail.com>, Leonard Rosenthol <lrosenth@adobe.com>, MURATA Makoto <eb2m-mrt@asahi-net.or.jp>, W3C Publishing Working Group <public-publ-wg@w3.org>
- Message-ID: <CACeuPAi+1cGjNCm3Q2ksD=h69RCwX-p8f0B7Y34hCpLeJjeSYg@mail.gmail.com>
I love this potential feature. This is the kind of thing that is exciting about WPs — the new possibilities they allow. However, I will continue to argue that we should be keeping our *WP definition/spec work very light & very focused* … what is the minimum viable definition/spec? … with the expectation that publishers & users of WPs will find all sorts of weird things to do with them we cannot imagine, and shouldn’t try to constrain. On Mon, Jul 31, 2017 at 5:31 AM, Ivan Herman <ivan@w3.org> wrote: > This is more a pragmatic reaction from my side: I have difficulties to > foresee how this would happen and what it would require. I have the (vague) > impression that we are getting into some sort of a research issue, that > could easily lead to a very complex, albeit fascinating development. But… I > think this will probably go beyond what this working group could tackle > right now. > > Maybe we will need to introduce a label on our global github issue list as > 'future work', and record this, and other possible but similar issue, as > indeed future work. > > (Just trying to keep us focussed, that is also part of my job:-) > > Ivan > > > > On 30 Jul 2017, at 19:38, Matt Garrish <matt.garrish@gmail.com> wrote: > > I don't think anyone is suggesting we should allow users to change any > content they please. There's always author permission involved – either to > provide the alternative content or identify what can be changed. > > It's more a question of whether content can be tailored to different > readers, and whether it's in our scope to define how. I'd suggest this kind > of question belongs in the business group first to investigate and > prioritize as we have plenty to do already. > > Matt > > *From:* Leonard Rosenthol [mailto:lrosenth@adobe.com <lrosenth@adobe.com>] > > *Sent:* July 30, 2017 12:28 PM > *To:* Matt Garrish <matt.garrish@gmail.com>; 'MURATA Makoto' < > eb2m-mrt@asahi-net.or.jp>; 'W3C Publishing Working Group' < > public-publ-wg@w3.org> > *Subject:* Re: [personalization] Changing the name of hero > > I agree that for publications where this makes sense, it seems reasonable > to coordinate with these other groups… > > But let’s remember that there are many(!!) other types of publications > that we hope to see as (P)WPs in the future where there is either (a) no > such things as a hero/heroine or (b) where changing it would be > inappropriate/incorrect. > > Leonard > > *From: *Matt Garrish <matt.garrish@gmail.com> > *Date: *Saturday, July 29, 2017 at 8:49 AM > *To: *'MURATA Makoto' <eb2m-mrt@asahi-net.or.jp>, 'W3C Publishing Working > Group' <public-publ-wg@w3.org> > *Subject: *RE: [personalization] Changing the name of hero > *Resent-From: *<public-publ-wg@w3.org> > *Resent-Date: *Saturday, July 29, 2017 at 8:49 AM > > > Can WPs take advantage of Personalization Semantics? > > We're not placing any restrictions on the content of a WP (it seems right > now, anyway). Whenever they're sufficiently stable and supported they could > be used. > > Matt > > *From:* eb2mmrt@gmail.com [mailto:eb2mmrt@gmail.com <eb2mmrt@gmail.com>] *On > Behalf Of *MURATA Makoto > *Sent:* July 29, 2017 8:30 AM > *To:* W3C Publishing Working Group <public-publ-wg@w3.org> > *Subject:* Re: [personalization] Changing the name of hero > > > > 2017-07-29 21:18 GMT+09:00 Matt Garrish <matt.garrish@gmail.com>: > > It's also in the personalization specification: https://www.w3. > org/TR/personalization-semantics-1.0/#coga-alternative > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fpersonalization-semantics-1.0%2F%23coga-alternative&data=02%7C01%7C%7Cb4558dc6f2f94823de4208d4d6803c9d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636369293645457986&sdata=dUHqb1hg6mSHbyVsym4qAsBHkToPYLD7KCT9hK6DE%2BE%3D&reserved=0> > > I don't think it's for this group to solve. > > > > Interesting! Can WPs take advantage of Personalization Semantics? > > Regards, > Makoto > > > Matt > > *From:* Daniel Weck [mailto:daniel.weck@gmail.com] > *Sent:* July 29, 2017 6:22 AM > *To:* MURATA Makoto <eb2m-mrt@asahi-net.or.jp>; Charles LaPierre < > charlesl@benetech.org> > *Cc:* W3C Publishing Working Group <public-publ-wg@w3.org> > *Subject:* Re: [personalization] Changing the name of hero > > FYI: in the DIAGRAM project this is codified as "simplified language", and > it is one of the possible alternatives for accessible extended descriptions. > http://diagramcenter.org/standards-and-practices/content-model.html > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdiagramcenter.org%2Fstandards-and-practices%2Fcontent-model.html&data=02%7C01%7C%7Cb4558dc6f2f94823de4208d4d6803c9d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636369293645457986&sdata=FGH2QHpPUgUH1rnRaqEev51ddWKM%2F%2FewuC4stk2T%2Bx0%3D&reserved=0> > Regards, Daniel > > On 29 Jul 2017 9:09 am, "MURATA Makoto" <eb2m-mrt@asahi-net.or.jp> wrote: > > One of my friends suggested that, as do computer games, > future web publications should allow readers to change > the names of heroes and heroines. We might want to go further. > Some authors hesitate to use difficult expressions but they would > like to use them if they know when the current reader is well > educated. Future publications should allow automatic rewriting > based on user preferences. > > Is this in the scope of this tack force? > > Regards, > Makoto > > > > > -- > > Praying for the victims of the Japan Tohoku earthquake > > Makoto > > > > ---- > Ivan Herman, W3C > Publishing@W3C Technical Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 <+31%206%2041044153> > ORCID ID: http://orcid.org/0000-0003-0782-2704 > > -- -- Hugh McGuire https://rebus.community +1.514.464.2047
Received on Monday, 31 July 2017 15:11:35 UTC