Re: [pwg] Remixing content - in scope for WP

With the "not thought about it enough" caveat...

I generally view making a publication as "putting stuff together in one
place", so I'd think:

-- Manifest & all docs in reading order must live on same-origin (don't get
be started on "linear=no" type content)
-- "External resource" (similar to current EPUB allowances) may be from
different origin

I'm sure others (looking at you Hadrien) will likely strongly disagree...
but this is at least a proposal at one end of the spectrum.

Best,
   Garth

On Wed, Jul 12, 2017 at 9:29 AM, Leonard Rosenthol <lrosenth@adobe.com>
wrote:

> And as discussed in the issue – there is also the question of what
> “remixing” means in this context.
>
>
>
> Are we simply looking at allowing “linking” (vs. inclusion/embedding)?  Do
> it apply only to resources or also to “spine items”?  What about sub-items?
>
>
>
> Leonard
>
>
>
> *From: *"Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>
> *Date: *Wednesday, July 12, 2017 at 12:12 PM
> *To: *"public-publ-wg@w3.org" <public-publ-wg@w3.org>
> *Subject: *[pwg] Remixing content - in scope for WP
> *Resent-From: *<public-publ-wg@w3.org>
> *Resent-Date: *Wednesday, July 12, 2017 at 12:12 PM
>
>
>
> This was raised on GitHub [1], but I think it’s an issue about what’s in
> scope for WP.
>
>
>
> Should WP, PWP, EPUB 4 allow remixing content? When we discussed this in
> the DPUB IG, we pushed out to a later date because of security concerns,
> cross-origins and many other issues.
>
>
>
> [1] https://github.com/w3c/wpub/issues/8
>
>
>
> *Tzviya Siegman*
>
> Information Standards Lead
>
> Wiley
>
> 201-748-6884 <(201)%20748-6884>
>
> tsiegman@wiley.com
>
>
>