Closed elf-pavlik closed 8 years ago
You could draw them as arrows between vf:Group and vf:Person.
vf:Groups can be members of vf:Groups. I'm thinking maybe we should take the member stuff off the picture, what do you all think?
Also wondering if I should make vf:Agent into foaf:Agent? Etc.
Actually, I'm wondering if we want to keep the UML diagrams more at a logical level, so we can eventually support non-LOD interoperability schemes? I don't right now know what those implementations might look like. Hmmm.
vf:Groups can be members of vf:Groups. I'm thinking maybe we should take the member stuff off the picture, what do you all think?
In that case you can draw it as arrow between Agent and Group
Also wondering if I should make vf:Agent into foaf:Agent? Etc.
:+1: also http://xmlns.com/foaf/spec/#term_member
I can make PR to JSON-LD context that will make aliases:
{
"@context": {
"foaf": "http://xmlns.com/foaf/0.1/",
"Agent": "foaf:Agent",
"Person": "foaf:Person",
"Group": "foaf:Group",
"hasMember": { "@id": "foaf:member", "@type": "@id" },
"memberOf": { "@reverse": "foaf:member" }
}
}
This way for those who want to rely on that JSON-LD context, difference between vf:
and foaf:
namespaces stays hidden away.
I can make PR to JSON-LD context
Sounds good. Except I'm wondering about foaf:member, I will need to look at it to see how they define it. We also talked at one point about other types we want to define, so people can create subproperties of them and know something about their behavior. (Will be later today I think.)
So what do you think is most useful on the UML diagram then? foaf:Agent? Agent?
I looked up foaf:member. Sounds fine to me.
Let's always use prefixes, at least until we get close to 1.0 release :wink:
fixed in #67
Current diagram seems to show vf:memberOf and vf:hasMember as subclasses of rdf:Property. We define them as instances of rdf:Property. You could draw them as arrows between vf:Group and vf:Person.
Also vf:Relationship as a class doesn't use owl:inveseOf it only makes sense on rdf:Property in this diagram.