Playready Envelope Format - specifications

I'm trying to encrypt arbitrary content using the PlayReady envelope format, in order to send it to a 3rd party app which supports that format.
I was not able to find the format specification online.
Does anybody know where I can find the spec, or is it supported only by opaque services provided by Microsoft?

You will find the PlayReady Envelope format specified in the Microsoft PlayReady Documentation Pack (available to Microsoft PlayReady technology licensees). The relevant section is Specifications -> Microsoft PlayReady Format Specification -> 3. Envelope File Format.

Related

Are there differences between ics files for Apple and MIcrosoft?

I am creating an html form that accepts calendar event inputs, and returns an ics file. Are there any parameters of an ics file that are different between Apple and Microsoft devices?
Welcome to Stack.
No, no platform specific parameters are required to be provided to be read by an external platform. Of course if you mean parameters to URL, you can offer what you want - they become part of the URL for that ics calendar feed.
If you producing an ics file then you should familiarise yourself with https://www.rfc-editor.org/rfc/rfc5545 or https://icalendar.org/RFC-Specifications/iCalendar-RFC-5545/. The RFC 5545 ics specification is platform agnostic. It allows for private non-standard properties which can be (usually are) platform specific See
https://www.rfc-editor.org/rfc/rfc5545#section-3.8.8.2
https://en.wikipedia.org/wiki/ICalendar#Calendar_extensions
Apple of course has the unofficial uri webcal. See https://en.wikipedia.org/wiki/Webcal. It is not necessary to offer that. Apple does handle the standard http/s protocol with Mime type text/calendar and suffix .ics.

Koha RESTful api

I've been looking around the internet for information on Koha ILS restful api but I haven't found anything concrete. There is this link which talks about its HTTP API: http://wiki.koha-community.org/wiki/Koha_/svc/_HTTP_API but there are no examples and I'm quite confused with the MARCXML format required.
What I want to do is use this API to create biblio records into a remote Koha ILS system. If I understand correctly, using these services I can create records (probably using a JSON-to-MARC convert tool) but will I be able to also upload pdf files of each record in BASE64 format? It doesn't look like this is possible using this API although I'm not really sure.
The HTTP API available in Koha is a well-established protocol, called SRU, for searching library catalogs. This is protocol is meant only for searching, not for updating records.
Secondly, even though SRU 2.0 provides option for transmission of records in JSON format, most implementations do not support it yet.
Coming back to your use case, Koha cannot store PDF documents. It is a process automation tool in a library for physical collections, which deals only with metadata records. For storing digital documents you should look for document management solutions, such as DSpace, or smaller and easier Omeka. DSpace provides its own REST API for searching as well as supports SWORD protocol for uploading documents.

Document exchanged format in differen CMS

Is there any document exchange format for metadata among CMS?
For example, between Sharepoint and Alfresco, or Alfresco and Documentum?
I've been building a CMS and couldn't find a commonly accepted standard for content metadata. I decided to use the approach NestaCMS did by simply placing it at the top of the document: http://nestacms.com/docs/creating-content/metadata-reference
And then filtering it out when published.

PlayReady ClientID Individualization on Samsung SmartTVs

There is a fairly common practice to individualize the client of an app using the PlayReady IBX (Individualization Black Box). You can find more about this here http://blogs.msdn.com/b/playready4/archive/2011/10/10/ways-to-unqiuely-identify-a-silverlight-client.aspx but it is essentially a 'fake' license request to the license server that responds with the ClientID, then you can use this id to do whatever you may want.
It happens that I can't find any equivalent API for Samsung Smart TV system. I've read the PlayReady tutorial many times and the better candidate I've found was the SAMSUNG-INFOLINK-SEF object through the 'ProcessInitiatorsFromXml' call but I don't think it is going to work since I can't create the XML that contains the proper IBX ClientID.
Any ideas?
Thanks!

Which event data format should use?

I have an application that (among other features) has an event calendar. Some users need to export and import event data to their own calendars. I've found the iCalendar format, but I don't know if that's the most suitable format for me.
The format should be an extended format (as much as possible to reach the maximum number of users), particularly it must be a format that allows import/export of iPhone and Android calendars (the built in calendars).
The event data itself is very basic (name, description, start and length).
Is there any format that fits these requirements? Is there any way to make an iPhone/Android phone to import/export events in the iCalendar format?
Yes iCalendar is the standard that you are looking for (for more information you can go to http://calconnect.org/ )
regarding exports:
iCalendar is a standard that is based on apple calendar sor iPhone is compatible with icalendar and since this is the de-facto standard for calendaring so is Android compatible.