Bob,
A desired feature that led to the current rdf:List structure is the ability to
"close" a list - so some separate sub-graph can't "silently" add properties not
in the original. Your pattern might allow this through additon of a
"maxSlotIndex" property on "olo:OrderedList" (not suggesting this as a design,
just an example).
#g
--
Bob Ferris wrote:
Hello everybody,
in a longer discussion in the Music Ontology mailing list about how to
model a playlist, Samer Abdallah came up with a very good proposal[1] of
modelling a sequence/ordered list (as recently also discussed at RDFNext
Workshop[2]) as semantic graph (in RDF).
So, here we go:
- specification[3] (please also note the anonymous inverse properties)
- concepts and relations in a graphic[4]
- funky playlist example[5,6]
Again, thanks a lot Samer Abdallah for that cool concept.
Comments, suggestions, critics are very welcome.
Cheers,
Bob
PS: its all OWL based ;) however, we could also downgrade the concept on
the basis of rdfs:class, if needed.
[1]
http://groups.google.com/group/music-ontology-specification-group/msg/305a42362a1e4145
[2] http://www.w3.org/2009/12/rdf-ws/slides/rdflist.pdf
[3]
http://motools.svn.sourceforge.net/viewvc/motools/orderedlistsonto/trunk/rdf/orderedlistontology.n3
[4]
http://motools.svn.sourceforge.net/viewvc/motools/orderedlistsonto/trunk/gfx/olo_-_orderedlist.gif
[5]
http://motools.svn.sourceforge.net/viewvc/motools/orderedlistsonto/trunk/examples/orderedlist_-_example.n3
[6]
http://motools.svn.sourceforge.net/viewvc/motools/orderedlistsonto/trunk/gfx/olo_-_orderedlist_example.gif
