W3C home > Mailing lists > Public > public-xg-webid@w3.org > September 2011

Re: Marketing troubles - workable WebID profile generators

From: Andrei Sambra <andrei@fcns.eu>
Date: Wed, 28 Sep 2011 13:25:10 +0200
Message-ID: <4E830416.8020403@fcns.eu>
To: Jürgen Jakobitsch <j.jakobitsch@semantic-web.at>
CC: public-xg-webid@w3.org
Hi Jürgen,

I've tried looking into the charset problem and I can't really put my 
finger on it. To generate the certificates I call openssl though a 
shell_exec function. I've checked the terminal charset (locale) and it's 
set to en_US.UTF-8, which in theory means that there shouldn't be any 
problems with the encoding of accented characters.

AFAIK my local php install is configured with HTTP_ACCEPT_CHARSET 
ISO-8859-1,utf-8, etc. so that isn't the problem either.

If anyone has already encountered difficulties processing accented chars 
through php, please let me know. I'll keep looking into it.

Andrei

P.S. At least I've fixed the regex function that checks the name in the 
WebID generation form, so now it allows accented characters to be used 
(as opposed to 0-9a-Z._-).

On 09/28/2011 12:24 PM, Jürgen Jakobitsch wrote:
> hi andrei,
>
> i was just about to type on fcns's wall...
>
> your services are working great, thanks!
> i am especially thankful for being able to delete my profile, that's not common these days and greatly appreciated!
> i personally am totally fine with editing the profile in a text box, but non-coders might do some wrong of course..
>
>
> for debugging : the "common name" in my new certificate doesn't display umlauts correctly.
>
> wkr turnguard.com/turnguard
>
> ----- Original Message -----
> From: "Andrei Sambra"<andrei@fcns.eu>
> To: public-xg-webid@w3.org
> Sent: Wednesday, September 28, 2011 12:12:29 PM
> Subject: Re: Marketing troubles - workable WebID profile generators
>
> Hi,
>
> I'm the person responsible for webid.fcns.eu, and I would like to thank
> you for bringing forward the issues you had with this endpoint. I will
> try to fix them asap, as well as to improve a little the interface (at
> least to editing profiles less painful).
>
> Best wishes,
> Andrei
>
> On 09/28/2011 11:46 AM, Jürgen Jakobitsch wrote:
>> one more remark for info :
>>
>> there is an encoding issue with (at least) german umlauts @ http://webid.fcns.eu/
>> when i curl my foaf-uri, accepting rdf+xml everything is fine, but in the certificate
>> the umlauts are messed up.
>>
>> wkr turnguard.com/turnguard
>>
>>
>> ----- Original Message -----
>> From: "Jürgen Jakobitsch"<j.jakobitsch@semantic-web.at>
>> To: "Henry Story"<henry.story@bblfish.net>
>> Cc: public-xg-webid@w3.org, "Helmut Nagy"<h.nagy@semantic-web.at>
>> Sent: Wednesday, September 28, 2011 11:43:56 AM
>> Subject: Re: Marketing troubles - workable WebID profile generators
>>
>> hi henry, thanks for your answer and work in generell.
>>
>> we will communicate this page [1] for creating
>> foaf-uris and webids now.
>>
>> i just tested it and it works. only remark :
>>
>> it also creates the cert#hex as a predicate and not as a datatype.
>> i have already implemented a (still to be improved) workaround in webIDRealm for that special case
>> which should now work with foaf.me and fcns.eu generated foaf-profiles
>>
>> wkr turnguard.com/turnguard
>>
>> [1] http://webid.fcns.eu/
>>
>> ----- Original Message -----
>> From: "Henry Story"<henry.story@bblfish.net>
>> To: "Jürgen Jakobitsch"<j.jakobitsch@semantic-web.at>
>> Cc: public-xg-webid@w3.org, "Helmut Nagy"<h.nagy@semantic-web.at>
>> Sent: Wednesday, September 28, 2011 11:28:32 AM
>> Subject: Re: Marketing troubles - workable WebID profile generators
>>
>>
>> On 28 Sep 2011, at 10:51, Jürgen Jakobitsch wrote:
>>
>>> hi all,
>>>
>>> as you know our company set up a demo server of our main product (PoolParty Thesaurus Server)
>>> which is protected by webID.
>>> now we some people very interested in the technology and who would like to test things.
>>> problem is, believe it or not, these guys are from the not-so-tech-savvy front and
>>> do not have access to their own root server, which means they are not simply able to
>>> create or change their foaf-profile and therefor rely on foaf generators like foaf.me [1]
>>> or myxwiki [2].
>>> now unfortunately we are experiencing troubles with these sites, so any help is really appreciated.
>>>
>>> foaf.me
>>>
>>> 1. if you create a foaf-profile there's no way to edit it
>>> 2. especially so, if you create a foaf-profile without webID, there's no way to log in at all
>>> 3. nobody reacts to mails, is it a dead mailing list?
>>
>> Yes, I think that is probably very much in its last stages. It never really evolved beyond what it was 4 years ago as far as I can tell. A major problem is that it allows people to edit the xml, which of course is a no go as far as ease of use goes.
>>
>>> myxwiki
>>>
>>> 1. only creates rdfa, ok i'll write a parser or check if sesame has one to use, but availability of application/rdf+xml would be highly appreciated
>>> 2. the rdfa created doesn't seem right.
>>>     using this parser [3], i get triples that are not really ok,
>>>     have a try with this foaf-URI [4], try with and without #me
>>
>> Yes, you are quite right. That produces WebID profiles that use the deprecated ontology.
>> I put that together 1 and a half years ago quickly. I could try to update it, but I am not sure I will have time
>> in the near future (even if it should not take a lot of time, it's perhaps a few hours for me to remember how that whole system works, and things may have evolved a lot in the xwiki platform) I'd rather work on a better version using my branch of http://clerezza.org/ on http://github.com/bblfish/clerezza.
>>
>> The best work recently put together was the server at http://webid.fcns.eu/ by Andrei Sambra.
>>
>> That has a nice user interface, has a test suite and works.
>>
>> Things can still be improved a lot in my view as far as user interfaces go. We are only at the very beginning here. And because the benefits of WebID pivots around ease of use, I must say that we still don't have demos that do it full justice.
>>
>>>
>>>
>>> both of the above services write the rsa public key resource slightly different that i have it in my profile [5]
>>> but one has to adapt the foaf-profile parser to find the publickey-string.
>>> which one is the right one?
>>>
>>> version one (datatype=cert#hex):
>>>
>>> <rdf:Description>
>>>    <rdf:type rdf:resource="http://www.w3.org/ns/auth/rsa#RSAPublicKey"/>
>>>    <cert:identity rdf:resource="http://www.turnguard.com/turnguard"/>
>>>    <rsa:modulus rdf:datatype="http://www.w3.org/ns/auth/cert#hex">
>>>      bc 6d c4 be c2 a8 9a 3b 72 cf 31 74 e6 a3 d9 89
>>>      7e bd fc e5 bb 43 39 4d 85 cf 1e ad e4 b1 a7 83....
>>
>> This is the new accepted way to do it, and this is how the examples should be written out in the spec.
>>
>>>
>>> version two (cert#hex is a predicate)
>>>
>>> <rsa:RSAPublicKey>
>>>    <rsa:modulus>
>>>     <rdf:Description>
>>>      <cert:hex rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
>>>       b549fda19426d73c7b4b486ce50de7c10cbd89cac7ba39c5bf37a0465df5
>>>       e4e181211d8f7ea1432b0a1afb440c1d1e7f994cddfe05dcadd10e083be9
>>
>> It is worth supporting this way too, for backward compatibility. You can see the code that I use
>> in Scala here:
>>
>> https://github.com/bblfish/clerezza/blob/bblfish/parent/platform.security.foafssl/core/src/main/scala/org/apache/clerezza/foafssl/auth/WebIDClaim.scala
>>
>> or in Java using SPARQL, which I think ends up being easier to read:
>>
>> https://github.com/bblfish/foafssl-java/blob/master/foafssl-verifier-sesame/src/main/java/net/java/dev/sommer/foafssl/sesame/verifier/SesameFoafSslVerifier.java
>>
>>
>>> we seriously would like to spread the word about webID and help growing the community,
>>> also to world of decision makers who are interested. i guess a refactoring of the services around our topic would certainly help.
>>
>> thanks a lot.
>>
>> What would be great is if you could give people who have profiles on your system a WebId too. We just need more WebID generators and more competition and presentation ideas.
>>
>>
>>>
>>> any pointer, help or comment greatly appreciated
>>> wkr http://www.turnguard.com/turnguard
>>>
>>> [1] http://foaf.me
>>> [2] http://webid.myxwiki.org/
>>> [3] http://www.w3.org/2007/08/pyRdfa/
>>> [4] http://webid.myxwiki.org/xwiki/bin/view/XWiki/nagyhel#me
>>> [5] http://www.turnguard.com/turnguard
>>>
>>>
>>> --
>>> | Jürgen Jakobitsch,
>>> | Software Developer
>>> | Semantic Web Company GmbH
>>> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
>>> | A - 1070 Wien, Austria
>>> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>>>
>>> COMPANY INFORMATION
>>> | http://www.semantic-web.at/
>>>
>>> PERSONAL INFORMATION
>>> | web   : http://www.turnguard.com
>>> | foaf  : http://www.turnguard.com/turnguard
>>> | skype : jakobitsch-punkt
>>>
>>
>> Social Web Architect
>> http://bblfish.net/
>>
>>
>>
>> --
>> | Jürgen Jakobitsch,
>> | Software Developer
>> | Semantic Web Company GmbH
>> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
>> | A - 1070 Wien, Austria
>> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>>
>> COMPANY INFORMATION
>> | http://www.semantic-web.at/
>>
>> PERSONAL INFORMATION
>> | web   : http://www.turnguard.com
>> | foaf  : http://www.turnguard.com/turnguard
>> | skype : jakobitsch-punkt
>>
>
>
Received on Wednesday, 28 September 2011 11:27:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 September 2011 11:27:08 GMT