I would go for RDF/XML so we do not have to explain to much the
inbound/outbound xml.
Same as the one we use for indexing?
It remains only the question of how many people understands RDF...
Alin
On Mon, May 5, 2008 at 5:04 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote:
> Niclas Hedhman wrote:
> > The Restlet server is opening port 8182 and expects the URL path to be;
> > /entity/{type}/{identity}
> > For instance;
> http://localhost:8182/entity/org.qi4j.rest.RestTest$TestEntity/1234
> >
> > I have committed the beginning of the RESTful interface. The following
> > things are supported;
> >
> > * Entity PUT, GET, DELETE
> > * Only String Properties
> > * XML variant
> >
> > We need SOMEONE (one or more) to step up and work on the other bits, such
> as;
> >
> > * /entity should return a list of all EntityTypes in the system.
> > * /entity/{type} should return the identities of a particular type.
> > * Types; Numericals, Date, BLOB
> > * Associations
> > * ManyAssociations
>
> IMO we should use RDF/XML as the output format, since that defines a lot
> of the above, and makes references between entities easy (just use
> rdf:about attribute). Parsing can then be done with a standard RDF/XML
> parser, like Sesame. Would that be ok, or is there any reason to use a
> custom XML format?
>
> /Rickard
>
>
>
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
>
--
Alin Dreghiciu
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.
http://malaysia.jayway.net - New Energy for Projects - Great People
working on Great Projects at Great Places
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
