On Jan 10, 2017, at 18:06, Grahame Grieve <[email protected]>
wrote:
>>
>> statements to describe the graph itself, e.g. here's a graph which
>> identifies a particular person as the foaf:primaryTopic of the graph:
>>
>> {
>> "@context": {
>> "Person": "http://xmlns.com/foaf/0.1/Person";,
>> "name": "http://xmlns.com/foaf/0.1/name";,
>> "primaryTopic": "http://xmlns.com/foaf/0.1/primaryTopic";
>> },
>>
>>
>
> thanks. Is it expected that every domain application will come up with
> their own (different) way to do this?
Wrong list for this suggestion, but what is missing from the w3c semantic web
stack is a general graph transformation language, analogous to XSLT, that would
allow one to write domain-specific transformations from graph to hierarchy.
Perhaps it was imagined that RDF/XML plus XSLT would fill this role, but that
is painful. I've written srx-to-*ml transforms, but that is awkward also. Of
course you can always roll your own rules in JavaScript, but that hides
business logic in imperative code.
Regards,
--Paul
>
> Grahame
