adding some more sugar to rdf

Just a quick post to log an idea that's been spinning round my head for a few days.

1. Create a vocab or profile syntax that lets you give short (non namespaced) names to ontology classes and properties.
name = foaf:name
label = rdfs:label

where = is like owl:equivalent*, don't care about the syntax of this file at all, even RDF using owl:equivalent is just fine.

2. Create a way to reference this from an rdf file, something similar to profiles.

@proxy http://ex.org/my-proxy-ontology .
@prefix : .

:me a Person; name "Nathan"; nick "webr3"; birthday "31-03" .

and just to detract from this, I'd actually really quite like this syntax:

@proxy http://ex.org/my-proxy-ontology .

:me a Person; name Nathan; nick webr3; birthday 31-03;
knows (name Michael Hausenblas), (name Melvin Carvalho) .

literals shouldn't need enclosed in quotes unless they contain syntax grammer (although \ delimiting could cover this), it'd also be nice to be able to talk about the uri you just mentioned in context, and also to leave out obvious stuff like "a foaf:Person" on who you know, cos of course they are a person. Further, literal types could easily just be inferred by the predicate, and further still the ontology of the predicate should/could contain all the rules to validate the value using owl data type restrictions. (note, doesn't this cross over with xsd restrictions?).

just a random snippet of thoughts / brain dump!

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Printed from: http://webr3.org/blog/semantic-web/adding-some-more-sugar-to-rdf/ .
© Your Name Here 2012.

1 Tweet

2 Comments   »

  • Seth Russell says:

    I really like the ability to factor the namespace out of calls for information from the profile. That will allow the channel to evolve into human understandable language. Doing that does not preclude these words mapping into URI ... it just means that somewhere in the channel we have a semantic network evolving ... somewhere in the channel is the network of sameAs relationships which get efficiently fired. This allows the application programmer to think more conceptually ... like we do in the upper cortex of our brains on the other side of the nerve channel leading from the ear drum which is bombarded with sound waves having all manner of the ambiguity. Remember ... inevitably we are evolving a brain ...

RSS feed for comments on this post , TrackBack URI

Leave a Reply

Additional comments powered by BackType

  • webr3 avatar