Rest in peace, Erik Naggum.
]]>XSPARQL is a fusion of SPARQL and XQuery, a query/transformation language able to process RDF and XML data sources and return RDF or XML. It's great for transforming data from XML to RDF or vice versa, and more. Finally the worlds of XML and RDF might be getting closer, yay!
Now go check out the online demo. 8-)
]]>Happy birthday, Web. Thanks, Sir Tim.
]]>When Adam does something good, such as buying flowers or cleaning the bathroom, Eve can thank him, smile, and it's done, off everybody's mind, a small pleasant memory.
When Adam does something bad, such as forgetting to clean the bathroom or burping loudly, but it's not so bad that Eve would feel like raising it as a criticism (fearing that would be creating a bad feeling), Adam may not notice that it was perceived as bad, and Eve will be left with this unfinished matter on her mind, waiting in the back ready to pop up, souring her mood. When enough of these small unfinished matters accumulate, the last straw (just as insignificant as the others) leads to an outburst of criticism, which focuses on all those small bad things left not-dealt-with, and ignores all the small good things that were closed with a thanks and a smile.
I believe this is a natural course of life — we can't really bring up every small bad thing that someone does.
If the partners keep this natural course of things in mind, it could lessen the violence of the outbursts without keeping any pent-up issues waiting to explode later and with more strength.
This should apply in situations other than couple relationships as well (e.g. in a workplace), but it seemed easiest to describe in terms of two people.
It's not likely to be a new insight, but it's new to me. 8-)
]]>Saw it over at Jim Webber's blog, couldn't easily find it with google, so maybe this will help others.
Update: See the comment - it was a typo at Jim's blog (should be HATEOAS), but it's not unique there anyway. 8-)
]]>The following seem to be key principles for leveraging RDF-enabled services in an SOA.
- Define interface contracts as though message content is RDF
- Permit custom XML/other serializations as needed
- Provide machine-processable mappings to RDF
- Treat the RDF version as authoritative
- Each data producer supplies a validator for data it creates
- Each data consumer supplies a validator for data it expects
- Choose RDF granularity that makes sense
Apart from suggesting that RDF can be a good internal view on the data exchanged by Web services, with benefits especially in versioning, David suggests that validation has two faces - the producer should say how to validate that the data makes sense, and the consumer should say how to validate that the data is fit for the use by this particular consumer.
Further, David wonders about the mapping between XML and RDF - XSLT seems good enough for lifting from XML to RDF, and SPARQL seems to be a good start for transforming from RDF to XML. I can heartily suggest XSPARQL, a fusion of XQuery and SPARQL, for both mapping directions, but especially for lowering. (I'm a minor coauthor of XSPARQL.)
]]>Repeat after me: Resources should be sessionless!
]]>