BRO TCon - Wednesday, Jan. 12 at 11:00am PT
Trish Whetzel
Below is an agenda for this Wednesday, January 12 (feel free to add items) and call-in details.
Agenda:
- remove the Biositemaps IM from the BRO?
- what do we do with the related_areas_of_research and the related_activities, do they belong in the BRO?
- create "numeric URIs" for the BRO Resource classes?
Call-in Details:
-------------------------------------------------------
Meeting information
-------------------------------------------------------
Topic: BRO TCon
Date: The 2nd Wednesday of every 1 months, from Wednesday, January 12, 2011 to no end date
Time: 11:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 921 360 659
Meeting Password: bro
-------------------------------------------------------
To start or join the online meeting
-------------------------------------------------------
Go to https://stanford.webex.com/stanford/j.php?ED=154713612&UID=481527042&PW=NOGQzNmMyMzA3&RT=MiM0
-------------------------------------------------------
Audio conference information
-------------------------------------------------------
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 number (US/Canada): 1-650-429-3300
Global call-in numbers: https://stanford.webex.com/stanford/globalcallin.php?serviceType=MC&ED=154713612&tollFree=0
Access code:921 360 659
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://stanford.webex.com/stanford/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft Outlook), click this link:
https://stanford.webex.com/stanford/j.php?ED=154713612&UID=481527042&ICS=MIU&LD=1&RD=2&ST=1&SHA2=QACZuLJbC/HF1Owa9ST317qaz6QIj0KDbxzoiTDF6LA=
To check whether you have the appropriate players installed for UCF (Universal Communications Format) rich media files, go to https://stanford.webex.com/stanford/systemdiagnosis.php
http://www.webex.com
CCM:+16504293300x921360659#
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. You should inform all meeting attendees prior to recording if you intend to record the meeting. Please note that any such recordings may be subject to discovery in the event of litigation.
Trish Whetzel
Trish
Trish Whetzel
BRO TCon Minutes
Date: January 12, 2011
Attendees: Trish Whetzel, Jessie Tenenbaum, Csongor Nyulas
Agenda:
- remove the Biositemaps IM from the BRO?
- what do we do with the related_areas_of_research and the related_activities,
do they belong in the BRO?
- create "numeric URIs" for the BRO Resource classes?
=-=-=-=-=-=-=-=
Discussion Items
- Remove the Biositemaps IM from the BRO?
o Trish - We will be able to remove the IM from BRO
o Jessie – yeah
- What do we do with the related_areas_of_research and the related_activities, do they belong in the BRO?
o Csongor – do we want to have 4 ontologies, e.g. Activity, Areas of Research, BRO, and IM?
o Jessie – BRO keeps Resources only, IM is removed from BRO.. future representation format does not matter, Area of Research and Activity – should be removed
o Csongor – referring to Area of Research and Activity
o Jessie – these came into existence because of use cases similar to.. I’m doing research in this area, what else might be useful. Maintaining Resources is hard enough, let’s use existing ontology sources for these areas
o Csongor – do we have these other terminologies?
o Jessie – not yet, I will take this on as an Action Item to review terms for Area of Research and Activity
§ Trish – send link to Sample client to run the Search in Batch-mode as an Action Item
§ All – the replacement methodology will be to suggest replacement terms from existing ontologies, extract these ontology terms/branches, submit these terms to BioPortal as a view and have IM point to the ontology view parent class to import the terms. This replacement will be seamless to users.
- Create "numeric URIs" for the BRO Resource classes?
o Trish – suggest not to change URIs at this point in time based on the widespread usage of BRO terms thus far. We could add another property that has a numeric identifier. Suggest that developers become more familiar with the BRO API to traverse BRO to find ‘replacement terms’ when a term is deprecated.
o Jessie – main reason is to not deprecate as often, the extra property does not help this
o Csongor – there is a replaced by property to indicate what should be used if a term is deprecated.
o Jessie – this is fine
o Csongor – what about misspellings?
§ Jessie – change these by deprecating and adding a new term with correct spelling, but do deprecate term only to change plural to singular..only update the value in the SKOS preferred name property
§ Trish – part of the release process is to run a spellcheck so this help identify/prevent typos moving forward
o Trish – review of BRO Curation workflow slide
§ Csongor – also need to know when BRO is released and how this is tested in Editor and Query tool(s)
§ Trish – Action Item – add another slide for release workflow
o Trish
– Action Item – add mappings from BRO to OBI for Instrument terms.
§ Question: Should these terms also be imported?
§ Action Item – Csongor – what are the pros and cons of deprecating BRO Instrument terms and importing branch from OBI vs only mapping BRO Instrument terms to OBI Instrument terms
§ NOTE: Following the call, adding the mappings was decided against until impact of import of OBI Instrument terms is reviewed since adding the mappings and then importing the terms is duplicate work