W3C home > Mailing lists > Public > public-hydra@w3.org > June 2014

OLDM using the Hydra vocabulary for expressing property constraints

From: Benjamin Cogrel <benjamin.cogrel@bcgl.fr>
Date: Wed, 11 Jun 2014 12:51:01 +0200
Message-ID: <53983495.4060101@bcgl.fr>
To: public-hydra@w3.org
Dear all,

I have just joined the Hydra Community Group, this is my first message
to the list.
I really appreciate this initiative and the good work you have already made.

During the last months, I have been working on an Object Linked Data
Mapper (OLDM, another name for Object RDF Mapper) in Python:
https://github.com/oldm/OldMan .

This project, influenced by Hydra and JSON-LD, enables developers to
express the domain logic in RDF instead of encoding it into some Python
code, for the benefit of Web clients. It uses some Hydra vocabulary and
will support additional ones in the next future.

Currently, the "hydra:supportedProperty" is used for mapping properties
to resource objects.
It also supports the "hydra:readonly", "hydra:writeonly" and
"hydra:required" properties. 

I have seen that some of these terms are willing to change but this
should not be a problem because this
project is still very young.

For this first milestone, I have focused on a server-centric perspective
and I start to think that this OLDM could be of interest for building
Web clients. Currently, it relies on a SPARQL endpoint but I think it
would be better to make optional to allow alternatives like LDP or LD
fragments. Designing Web clients is rather a new topic to me so if you
have any suggestion about this, I would be very happy to hear it.

Also, in the future, I would like to support the "@reverse" JSON-LD
keyword so I would be interested about having some "reversed supported
properties".


Best regards,

Benjamin
Received on Thursday, 12 June 2014 09:30:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:42 UTC