I'm not sure I'm fully following this discussion, so apologies if this has 
already been covered.

It sounds like we might need to step back a little bit and consider the process 
from the user's perspective, thinking about how we want it to be designed, 
rather than how it currently works technically.

I imagine a workflow that goes something like this:

* A user has a video that they want to include in their WordPress blog/site
* They use our plugin to either:
   a) upload the file directly (like, say, if they made the movie themselves in 
iMovie)
   b) point us to a video that's already on YouTube
* If it's a YouTube video, our plugin checks Amara to see if there are already 
captions for it
* If there aren't, or if the video is being uploaded by the user, it prompts 
them to caption it using Amara
* There might be, if necessary, some "advanced options" where a user can choose 
to upload or link to a pre-authored caption file; but I suspect this isn't a 
typical use case

Does this seem about right?

Colin

---
Colin Clark
http://fluidproject.org

On 2013-01-24, at 12:15 PM, "Cheetham, Anastasia" <[email protected]> wrote:

> 
>> I have listed the major pieces of functionality on this wiki page:  
>> http://wiki.fluidproject.org/display/fluid/%28Floe%29+Video+Player+Wordpress+Plugin+Exploration
> 
> I've updated the wiki page with a bit more specificity about the 
> functionality.
> 
> 
> Regarding your questions:
> 
>> 1. Is any other metadata information required? i.e. author, description / 
>> summary, primary language, etc?
> 
> At this time, no other information is supported.
> 
> 
>> 2. Are any of the fields mandatory? I assume the Video URL and format are 
>> the only required fields?
> 
> At least one videoUrl/format combination is mandatory. Any additional ones 
> are optional.
> 
> Captions and transcripts are not mandatory, however, if they are added, all 
> information for the file is mandatory: url-or-name, format and language
> 
> 
>> 3. How common is the Amara use case for either Transcript or Captions?
> 
> I think that remains to be seen :-)
> 
> 
>> 4. Can JSONcc or VTT resources be loaded from an URL?
> 
> Not at this time, due to cross-site scripting restrictions.
> 
> 
>> 5. Can the type of caption / transcript be detected given an URL?
> 
> I suspect not, given that we can't count on what people will name their files.
> 
> 
>> 6. Can an Amara transcript or Amara caption be uploaded locally or must it 
>> always be specified with an URL?
> 
> AFAIK, it must be an URL.
> 
> Amara is a service that hosts captions for videos. In this case, the URL is 
> actually the URL of a video that has Amara captions on the Amara site. Even 
> if it happened to be uploaded to the local WordPress instance, the Amara 
> captions would have to be referenced using the full URL of the 
> WordPress-hosted video; that's just how Amara works.
> 
> The URL will not necessarily be the same as one of the video urls: it will 
> include a language code (since it refers to a specific language of caption). 
> For example (taken from our demo), if the original video is a youtube video
>       http://www.youtube.com/v/_VxQEPw1x9E
> Amara might host two captions, referenced using these urls:
>       http://www.youtube.com/watch?v=_VxQEPw1x9E&language=en
>       http://www.youtube.com/watch?v=_VxQEPw1x9E&language=fr

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

Reply via email to