 Pete's going to set the stage for tonight's 5.30 vendor team meeting which will be here in this room and show you some of the plans we have and the tooling we're developing for being able to look at all the vendor products equally. So Pete. Thanks Dennis. Hi everyone. So I'm going to be talking about what we've been doing in something called the FIBO vendors team. That's one of the other teams that we're running within FIBO that is in parallel to the content team which is actually developing FIBO itself. This is about, so the aim of this activity is because FIBO is based on standards, we want to build a community of tools. And so the objective of this FIBO vendors team is to provide FIBO users and also FIBO developers, people working on FIBO, the choice of tooling and also a basis for choosing between them. And then what we want to do for vendors, this is a motivational factor, it provides them a marketplace to tell people, tell the FIBO community about their tools and their capabilities. So it's a marketing option for the vendors as well. And what we're doing is managing it through the FIBO community. So there's the FIBO vendor team which has weekly calls and also that manages everything through the wiki, which you can see on the EDM Council site there. What I'm going to be doing is giving you a flavor of what we've been doing of a wiki so far and encouraging you to be involved with the session later today. So what we're doing as part of a wiki, we have weekly meetings with minutes and everything. We've been building a number of online tables of different criteria. So there's one, there's four different tables allowing people to categorize information about the different tools. So one we've got is support by our construct. So this is for ontology tools, this allows the vendors to list which our constructs do they support. For example, there's several tools which, for example, CCM allows you to do a lot of what FIBO supports in terms of OWL. It doesn't quite do them all. So this gives an opportunity to see which aspects of OWL support are supported by the tool. And also that column there you can see FIBO question mark. So this is where, from a FIBO point of view, we can say does FIBO actually use this OWL construct? So maybe it doesn't matter to people involved in the FIBO community if the tool omits support for one OWL construct which FIBO doesn't actually use. It's largely irrelevant to a FIBO user. It's just academic. So I'm not going to go through all of the criteria. There's a number of different rows in all of these tables. We'll be talking about that more later. But you can see there's a column for each, there will be a column for each tool and then a criteria on each row. And the idea is you expand, each vendor will expand the matrix to include a new column. Question? Yes, sorry about that. I can't immediately hear, I'm afraid. So the point is really, as Dennis said, to be a teaser for this evening rather than provide a detailed analysis of these. So I can quickly, next is support by function for FIBO development. So this is aimed more at people involved in the FIBO community itself in terms of actually changing FIBO. There's facets focused on FIBO developers there. And then separately from the OWL and the FIBO ontology, we've also got the thread within FIBO, FIBO Viva vocabulary, which is based on SCOS. So there's a separate page covering SCOS constructs. So what can I do with this as a user? As a user, either an end user or someone involved in FIBO, you can just, the idea is you've got to browse the available tools. But based on your criteria, choose a tool that meets your needs. And then what can you do as a vendor? So firstly, you should add a new column to the table for your tool to ensure people know about your tool and its capabilities. At the top of each column there's a version and date so people know how up to date your tool entry is. And then you should keep it updated with new releases so people know about new features you've added to your tool. But generally the guideline is the tool should be generally available at least to the FIBO community. So it's pointless putting things in there for a new release or a very limited release that people can't actually get their hands on. There is a link which I've reproduced here for Confluence Editing Instruction. So in the Wiki we're using a tool called Confluence from Atlassian, the same people who produce JIRA. So that's what we're using for the Wiki. And there's quite sophisticated instructions for adding tables you can paste in from Excel. And there's a link there to those editing instructions. And then if you want a change to the number of rows you think there's something missing from a criteria or maybe a new page missing then rather than just adding it in for your own tool and no other tools we'd like you to add a comment to the actual specific page or better still raise a JIRA issue which will go through our FIBO vendor team process to agree adding a row because that affects all tools. And then generally this is a community resource. So we're not trying to sort of restrict it to particular vendors or particular columns. So treat it with respect, don't go in and edit the columns of other vendors and so on. You can come back at 5.30 and ask as many questions as you want. We'll take a lot of time. But Dave and I just made the executive decision to make this particular Wiki site wide open so we won't have to log in just go there. And when Jacob just comes back he can show me how to do that because I don't know how. So just to get us started we want to treat every single vendor the same. We want all vendors to participate in the way that this is broad enough that it certainly should be possible. You could be a visualization person. You could be a FIBO builder. You could be what we saw with Scott yesterday, a university. And could you be something? This is for everybody. So thank you very much Pete.