Support for Wildcard Certificates

[Timothy Holborn]

Hi All,

I've been working on a field of research with a bunch of smart people, who are collectively working on means to separate data from applications. 

The work started with TimBL theory [1][2], which then overtime developed [3][4][5] and these smart people continue to develop concepts / solutions, which need more work - but are developing slowly. 

One of the platform examples [6] show how applications [7] can be authored in a way that separates the data, from the application. This has been further described in the Video [8], and the source for many of the projects is available on github [9][10].

Another good video about the field of work is here [11], and related work can be found here [12].

Purpose of the question is about wildcard domains.

as described in the video [11] the question of how to encourage users to store their own data comes about.  Traditionally, the cost for a user to set-up their own hosting service, domain, and wildcard certificate has been prohibitively expensive.  Let's Encrypt might change all of that; yet,

The current systems use subdomains to separate accounts.  These different subdomains might refer to devices, or persona.  regardless, the server needs a wildcard certificate at present. 

Any chance you might provide support for it and if so, what's the proposed timeline?

Cheers,

Tim.H.

 

[1] http://www.w3.org/DesignIssues/ReadWriteLinkedData.html

[2] http://www.w3.org/DesignIssues/CloudStorage.html

[3] http://crosscloud.org/

[4] http://www.w3.org/2005/Incubator/webid/spec/tls/

[5] http://myprofile-project.org/thesis/manuscript_en.pdf

[6] http://rww.io/

[7] http://cimba.co/

[8] https://www.youtube.com/watch?v=z0_XaJ97rF0

[9] https://github.com/linkeddata

[10] https://github.com/rww-apps

[11] https://www.youtube.com/watch?v=AzMmVr2VUFU

[12] http://w3c.github.io/ldp-testsuite/