Re: GSoC Final Project Deadlines

It's reasonable, but pretty shallow, and certainly doesn't follow the best practices of Linked Data. For example, it shows that Wikia is one of companies I work for, but just has a blank node with name "Wikia". Looking at the returned JSON from LinkedIn, though, there's enough information to create an actual IRI for it. Looking at the returned JSON, I see the following for positions:

   "positions": {
      "_total": 15,
      "values": [{
        "company": {
          "id": 157252,
          "industry": "Internet",
          "name": "Wikia",
          "size": "51-200 employees",
          "type": "Privately Held"
        },
        "id": 291520813,
        "isCurrent": true,
        "startDate": {
          "month": 6,
          "year": 2012
        },
        "summary": "Adding structure to wikis.",
        "title": "Linked Data Consultant, Advisory Board member"
    ...

This is enough to link to the company, and provide some context for the work I've done with them. At the least, I would create an @id referencing the Wikia profile. This would just be <http://www.linkedin.com/company/157252>, which you can figure out given that it is a "company" position, and has an id. Same would hold for other references, such as education.

Also, the "owns" information isn't too useful. It like your setting a type of <http://schema/url>, which is a property, not a type. And your using the account URL as the name and throwing the name away. For example, the following:

{
  "@type": "url",
  "name": "http://www.kellogg-assoc.com"
}

Where the information from LinkedIn is:

    "memberUrlResources": {
      "_total": 3,
      "values": [{
        "name": "Personal Website",
        "url": "http://www.kellogg-assoc.com"
      }, {
        "name": "Laudits",
        "url": "http://www.laudits.com/pub/1162/gregg-kellogg/7trdv"
      }, {
        "name": "Twyla",
        "url": "http://www.twylah.com/Gkellogg?utm_source=New+users+week+of+20120319&utm_campaign=4d564b7e48-New_20120321&utm_medium=email"
      }]
    }

From that, I would think that you'd do more the following:

{
  "@id": "http://www.kellogg-assoc.com",
  "name"Personal Website"
}

You might be able to figure out that it has a @type of schema:OwnershipInfo, as that is the range of schema:owns (look at http://schema.org/owns).

Gregg Kellogg
gregg@greggkellogg.net

On Sep 4, 2013, at 11:32 AM, vikash agrawal <vikashagrawal1990@gmail.com> wrote:

> Hello Markus, 
> 
> For the current scenario of testing its live here [1] (make sure its http and not https). Also once its merged, I will remove this domain from LinkedIn Developer Console, so that it becomes inaccessible from the dropbox domain.
> 
> [1] - http://dl.dropboxusercontent.com/u/5278881/gsoc/json-ld.org.old/linkedIn/index.html
> 
> 
> On Wed, Sep 4, 2013 at 9:35 PM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote:
> On Wednesday, September 04, 2013 11:33 AM, vikash agrawal wrote
> > hi All,
> >
> > Task Completed So Far.
> > • LinkedIn Tool
> 
> Is there a link to the latest version of the LinkedIn tool so that I can have a look at it without having to set it up myself?
> 
> 
> Thanks,
> Markus
> 
> 
> --
> Markus Lanthaler
> @markuslanthaler
> 
> 
>