RE: Technologies - RDF

Good catch.  
 
I hadn’t considered RDF as a carrier of change-tracking information and provenance information.  I was thinking of the case where RDF is used to provide semantic markup and how changes can break the semantic connection if the processor that introduces changes is unaware of the semantic dimension (or the user neglects it).
 
In providing a serialization of changes, would you expect to limit the RDF grammar for that or would it be open-ended RDF?
 
-   Dennis
 
From: innovimax@gmail.com [mailto:innovimax@gmail.com] On Behalf Of Innovimax W3C
Sent: Sunday, September 21, 2014 02:21
To: Dennis Hamilton
Cc: public-change@w3.org
Subject: Re: Technologies - RDF
 
Thanks Dennis,
I want also to hear more about RDF in this area
 
Here is the use cases I foresee :
* extending Dublin Core
* providing a serialization in RDF of the list of changes (bear in mind that we will provide many serialization XML-with-PI, XML-with-Element, etc.)
If we see other use cases, I will be happy to consider them
Regards,

Mohamed
 
 
On Sat, Sep 20, 2014 at 10:06 PM, Dennis E. Hamilton <dennis.hamilton@acm.org <mailto:dennis.hamilton@acm.org> > wrote:
[The W3C site seems to be a little pokey about posting the message it was sitting on until I gave my permission.  Here is what may end up being a repost.]
 
RDF was touched on a little in discussions at DChanges 2014.
 
One concern is that RDF directed into an XML document and/or embedded into the XML document is technically possible but the loose-coupling raises difficulties.  If the application of the XML document is only passively aware of the RDF usage, changes to the XML document might preserve the RDF yet it can become semantically inconsistent as a result of the changes.
 
This seems to apply in cases where RDF injection is a kind of appendage to the use of XML for document representation and applications do not provide an integrated treatment.  
 
My thought is that integrated treatment might be very difficult because, in some manner there can be quite a disparity between the levels of abstraction of the XML document versus what the RDF is intended to elicit.
 
Of course, one might inject change-tracking into an <RDF:rdf> element, which is different than the case where there has to be coordinated change in both the RDF and modification of the non-RDF XML document structure and text.
 
This may become aggravated the farther the model of the application is from the level of abstraction of RDF and XML.  In that case, more and more of this becomes invisible to users at the application level and coordinated change with underlying RDF seems not to be handled in any general way at this time.
 
-   Dennis
 
From: Innovimax SARL [mailto:innovimax@gmail.com] 
Sent: Saturday, September 20, 2014 02:25
To: public-change@w3.org <mailto:public-change@w3.org> 
Subject: Technologies
 
Dear all,

I started to collect the technologies that could interact at any level with change tracking
Here are a few so far https://www.w3.org/community/change/wiki/Technologies
* XML 
* Namespaces 
* HTLM5 
* XPath 
* JSON 
* RDF 
* XQuery Update 
* EXI 
* Dublin core 
Please fill free to add (and perhaps links also)
Mohamed


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787 <tel:%2B33%209%2052%20475787> 
Fax : +33 1 4356 1746 <tel:%2B33%201%204356%201746> 
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 € 



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €