[Xerte-dev] Re: Youtube RSS

[Julian Tenney]

Thinking differently, why don't we just embed the youtube search page and forget about the API calls?



-----Original Message-----
From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley (Pgogy)
Sent: 13 July 2015 13:28
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Youtube RSS

Exported is a sort of context neutral reuse, with an OER it is any use you feel like doing under the license.
I may plausibly just want the youtube page and nothing else, and then to get other feeds as well.

If I have something which uses a key I basically take a punt on how much it will be used and how techie the reusers are.

The phoning home makes sense, would make setting up a server easier as well (what would stop someone creating a youtube page is the key wasn't set up?)

On 2015-07-13 08:17, Julian Tenney wrote:
> Not sure what you mean?
> 
> The key is going to bind the content to an owner. I wouldn't let my 
> personal key get passed around, nor would I let any keys associated 
> with UoN. I'm not sure it's risky, but it just doesn't feel right as 
> the use of it is tracked and we would lose control over what it's 
> being used for.
> 
> All I can think is that the content reaches back to its mothership for 
> the key somehow: the youtube rss functionality will need internet 
> connectivity anyway, but it still makes me a bit uneasy.
> 
> -----Original Message-----
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat 
> Lockley (Pgogy)
> Sent: 13 July 2015 13:08
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: Youtube RSS
> 
> On 2015-07-13 05:10, Julian Tenney wrote:
>> OK. It's basically working though, if it wants tweaking a bit to line 
>> up with the existing code that's fine.
>> 
>> Do you think it would be acceptable if you had to add your own key to 
>> make an exported file work? I can't think of another way: we can't 
>> use a generic 'xerte project' key, and as an institution I would be 
>> uneasy with an exported piece taking my key with it: god knows where 
>> it might end up or what it might be used for.
> 
> What if it becomes an OER though?
> 
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> 
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee 
> and may contain confidential information. If you have received this 
> message in error, please send it back to me, and immediately delete it.
> 
> Please do not use, copy or disclose the information contained in this 
> message or in any attachment.  Any views or opinions expressed by the 
> author of this email do not necessarily reflect the views of the 
> University of Nottingham.
> 
> This message has been checked for viruses but the contents of an 
> attachment may still contain software viruses which could damage your 
> computer system, you are advised to perform your own checks. Email 
> communications with the University of Nottingham may be monitored as 
> permitted by UK legislation.

--
Pgogy Webstuff
pgogywebstuff.com

_______________________________________________
Xerte-dev mailing list
Xerte-dev at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev