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

RE: [foaf-protocols] WebID test suite

From: Peter Williams <home_pw@msn.com>
Date: Wed, 29 Jun 2011 13:29:45 -0700
Message-ID: <SNT143-w4602FE5F647047A86E4EB992590@phx.gbl>
To: <mo.mcroberts@bbc.co.uk>, <henry.story@bblfish.net>
CC: "public-xg-webid@w3.org" <public-xg-webid@w3.org>

no namespacing? "manager: cn=Barbara Doe,dc=example,dc=com" the attribute value is an href (in web speak). If you want, you can invent a novel syntax, and rewrite that as http://example.com/Barbara%20Doe if you want, or ldap:///@cn=Barbara Doe,dc=example,dc=com.  Tim Howes designed that syntax, as a minor variant of the output of the computer science project a school colleague of mine did as his undergrad assigment. It started life as a simple file format, for ADTs (as classes were known as the time). Just shy of being 25 years old, since first deployed. > From: mo.mcroberts@bbc.co.uk
> Date: Wed, 29 Jun 2011 20:32:29 +0100
> CC: public-xg-webid@w3.org
> To: henry.story@bblfish.net
> Subject: Re: [foaf-protocols] WebID test suite
> Hey Henry,
> Just to chip in here:—
> > Here is an ldap entry taken from wikipedia 
> > dn: cn=John Doe,dc=example,dc=com
> >  cn: John Doe
> >  givenName: John
> >  sn: Doe
> >  telephoneNumber: +1 888 555 6789
> >  telephoneNumber: +1 888 555 1232
> >  mail: 
> > john@example.com
> > 
> >  manager: cn=Barbara Doe,dc=example,dc=com
> >  objectClass: inetOrgPerson
> >  objectClass: organizationalPerson
> >  objectClass: person
> >  objectClass: top
> > 
> > 
> > It is an attribute value pair system, without namespacing, and so is designed for client server interaction, not for linked data interaction. You need to tie those into a global namespacing. Not impossible, but you have a lot of work on your hands to get all the others to 1. understand why it is important (because they are living in closed worlds, and don't see what they are missing) and 2. Get an agreement world wide on how to do this.
> It does have namespacing: what you're seeing above is a textual representation of an entry in LDIF format. The attribute names there are generated based on the schema held in the LDAP server, while the raw data uses OIDs for the classes and attributes instead. A given OID arc is a pretty reasonable parallel to a URI namespace. For example, all of the attributes from Sun's NIS+ LDAP schema live under one particular arc (except for references to other schemata), and so on and so forth.
> A fun project for somebody one day would be to run a web service on a well-known URI which spat out RDFS/OWL/whatever for the objectClasses and attributes at a particular OID. Would be a nice extension to Harald Alvestrand’s OID browser… [e.g., http://www.alvestrand.no/objectid/2.5.html]
> M.
> -- 
> Mo McRoberts - Data Analyst - Digital Public Space,
> Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA,
> Room 7066, BBC Television Centre, London W12 7RJ,
> 0141 422 6036 (Internal: 01-26036) - PGP key 0x663E2B4A
Received on Wednesday, 29 June 2011 20:30:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:24 UTC