 |
 |
> I guess I don't see the advantage of this. Why would we want > to create our own interface, query syntax, etc. when everyone > else seems to be implementing Web services? OK, I just want to be sure we aren't raising the bar for users. > The provenance information for the translation relies heavily > on rdf:ID. If we do not offer the provenance info as a > service then we avoid this problem, but are still faced with > the encoding problem (see below). OK, yes, I thought the reified stuff might be complicated. > I need to play around with this a bit, but I believe this > will look, to the client, like one big structure. I'm not > sure that is particularly useful. Well, I guess that one big structure is useful when it's passed to an RDF-aware client ;-) > I think it would be more > useful to deliver an XML document that conforms to a > published schema. Anyone else have any thought on this? Pete