...
- Brown
- Buffalo -
- Colorado
- Cornell
- Duke
- Florida
- Indiana - trying to load some UF SQL dumps to test performance and caching of visualizations. Taking 18+ hours to load to load on Mac system; getting access to a faster machine which should allow them to move forward.
- Johns Hopkins --
- Memorial University --
- NYU –
- Scripps --
- Stony Brook – Erich wrote up a demo of WebID work he's done. Go to ebremer.com to see webID in action. Stony Brook implementation is going forward, had to reboot some things as administrators have come and gone. WebID attractive for VIVO because foaf profiles already in place, with the only real new addition being the public key data. There's a small ontology for public key; Erich will send out an email to the dev group about this. Would be good to be included in VIVO distribution / ISF. Some security/stability issues to consider related to hackers and malicious or simply oversized "foafiles." Do we want to have a shorter "business card" profile would link to larger things so servers don't have to download giant profiles in one fell swoop? For optimization reasons it would be useful to have a short and long version with a seeAlso kind of reference.
- UCSF – Eric - very busy week. Finally launched new version of Profiles that supports the VIVO ontology, several months in the making. Probably, other than Harvard, the only ones to upgrade to the new version. Frees up time to do other things they want to do. The older code had API for extracting data – native XML, but they created a JSON version. Extremely popular; dozens of sites that use this API to consume data in real time. All but one use the JSON API; people love JSON. Now that they're on the new version, they're going to migrate things to linked open data. Promote people using things outside of OpenSocial. Looking at how to get the Linked Data out as JSON. JSON-LD seems more standard than Elda, and there are libraries that support it. Lots of Drupal sites that integrate data right at the HTML layer doing runtime grabs. With JSON that's a feasible solution.
- BL: What should we include in standard/"extended" linked data responses? EM: Very PubMed-centric, people want PubmedID in any deep copy of data. It would be nice to specify shallow/deep linked data request that would be standardized across systems.
- BL: What should we include in standard/"extended" linked data responses? EM: Very PubMed-centric, people want PubmedID in any deep copy of data. It would be nice to specify shallow/deep linked data request that would be standardized across systems.
- Weill Cornell --
- other --
...
- To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
- Call-in toll-free number (US/Canada): 1-855-244-8681
- Call-in toll number (US/Canada): 1-650-479-3207
- Global call-in numbers: https://cornell.webex.com/cornelluniversity/globalcallin.php?serviceType=MC&ED=161711167&tollFree=1
- Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf
Access code:645 873 290
last meeting | next meeting