Content types #2
Conversation
To account for non-sensual descriptions and support future enhancements that wouldn't fit the senses model
mud.ttl
Outdated
| mud:content a rdfs:Class ; | ||
| rdfs:label "Textual Content"@en ; | ||
| rdfs:comment "Content describing another model"@en ; | ||
|
|
||
| mud:sight a rdfs:Property | ||
| rdfs:label "Sight"@en ; | ||
| rdfs:comment "The visual sense"@en ; | ||
| rdfs:domain mud:content |
There was a problem hiding this comment.
Could we move the new things into a new ontology please ? I'm thinking mudcontent ?
Just for modularity - if someone was writing their own front-end they might want to replace our definitions for the user's perception
There was a problem hiding this comment.
Done in 1a6f286 😄
I then updated the Java app here Multi-User-Domain/mud-jena@59a821a
| @@ -0,0 +1,25 @@ | |||
| @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . | |||
| @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . | |||
There was a problem hiding this comment.
I added some extra imports. Note that whenever you use the syntax mud:something it's actually shorthand for the full URI https://raw.githubusercontent.com/Multi-User-Domain/vocab/main/mud.ttl#something
The prefix statements define what the shorthand is for
| mudcontent:sight a rdfs:Property | ||
| rdfs:label "Sight"@en ; | ||
| rdfs:comment "The visual sense"@en ; | ||
| rdfs:domain mud:content . |
There was a problem hiding this comment.
added a missing '.' character here. Every turtle statement ends in a full stop, the semi-colon is a break to say "done with this property, but the next one is about the same subject (mudcontent:sight)
What?
Add content type to MUD Vocab
Why?
To support changes in Multi-User-Domain/mud-jena#7