[00:00:00.00]Participant: It is a question about the Domain model. What's being represented there. We know that we've got a class that's represented by the resource cloud. What I think I want to clarify what is it that's being represented by the other purple squares. So, does Audience represent a class, or entity. And I guess why I am asking this because I'm not sure why you have audience as being related to a group of things, like language, type, level, age - rather than those being properties of Audience, or displayed as being properties of the Audience in the same way as the property hasLanguage, coverage is displayed as a property of the resource.
So I think what I am asking one of the things we need to clarify with this is _what_ is being represented where i terms of what is a class of entities and what is a property of the entity in that class.
[00:01:36.27] Modeller: Thank you very much, Phil. Exactly the sort of things that I wanted because, well, partly to do with me learning to use Microsoft Visio as I go, and... I'm so useless at graphic modelling, and honestly, I was so proud of myself that I got this far. But I knew very well that some of the things with purple boxes, they're not the same kind of things than other purple boxes. So, yes, you're quite right, we need to clarify what are classes of things, and what are properties of things that are in that class. And we need to do it visually so things are very clear in different visual appearance, and have a key somewhere so it is clear. I really want to be on to do that, so I feel a bit embarrassed actually showing it publicly, special to people like Andy Powell, and yourself, Phil and John, and everybody. Yeah... we got 8 minutes left, so it is definitely a thing I want to do next, and I would certainly appreciate some help with that.
[00:02:58.04] Participant: I think switching to a more standard modelling representation, rather than clouds and purple boxes, would be a good idea to switch to the perhaps standard UML way of representing what's what is a class, and that way when we get it wrong there will be people around we show it to who will immediately recognise that's it is wrong. And I should make it clear to everyone that one of my contributions to this diagram was to start off with the purple boxes and the clouds, partly because I wanted to be vague about what was going to be a class. But I think the time for vagueness now is passed.
[00:03:50.28] Co-moderator: I think those were really good points, and know that, I have heard some of the same kinds of concerns about the diagram. And I have to say that I am much worse than Sarah can profess to be about doing these kinds of diagrams and doing it properly. You know, I'm still a learner in those areas, and far behind where Sarah has gone. But, I do think though, that it is good to remember that the a lot of the stuff that is already identified by Dublin Core, you know, they already have a life as properties, not inserted in classes, so even though we may have, if we have indeed shifted our feeling about things like, you know, based on the way the Singapore framework allows us to kind of modularise things in more incree ? classes where we once have properties, we have to be pretty clear about that. Because I think that is one of the areas that we're struggling with in our own heads.