CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 08:48:24 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:27:13 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 08:48:24 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bc9e65b892c17e
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=gnZzP9S5ceOwOm5ITtU8HoSQuS4E1zyrDDZEh_OOwac-1759999704-1.0.1.1-mfCdwg3hXl3Oxd8JXct9W0jHCOwGugP0XR51npx8w9GW9OKWVExhnS3qyG3FmNki5GoXpic5iS_gDN_Er_Xray8_mGbJho6Y_w9xCwmTTwM; path=/; expires=Thu, 09-Oct-25 09:18:24 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc9e65b892c17e-BLR
alt-svc: h3=":443"; ma=86400
Representing the Differences Between two Models from Arnold deVos on 2001-03-28 (www-rdf-interest@w3.org from March 2001)
Representing the Differences Between two Models
- From: Arnold deVos <adv@langdale.com.au>
- Date: Wed, 28 Mar 2001 19:22:13 +1000
- To: "RDF interest group" <www-rdf-interest@w3.org>
- Message-ID: <001001c0b768$a7b93af0$ea01a8c0@cockatoo>
Here is a proposal [1] for representing the difference between two RDF models as an RDF model. In the electric power industry have a use case for this in exchanging power system models between utilities [2]. I would imagine there are others who have giant models like us and sometimes need to handle only the differences. Something like this requires quoting of RDF statements. I know this is supposed to be covered by rdf:bagID, but I couldn't see how to use that in this case without creating a self-contradictory model. Therefore I am floating an (application-specific?) extension to the syntax, parseType="Statements". This is supposed to be similar to the braces in N3 [3]. Here is an illustration of a difference model using this extension: <rdf:RDF xmlns:rdf="https://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cim="https://iec.ch/TC57/2000/CIM-schema-cimu09a#" xmlns:dm=https://iec.ch/TC57/2001/Differences> <rdf:Description about=""> <!-- Content: (literal-property|resource-property)* --> <dm:preconditions parseType="Statements"> <!-- Content: (definition|description)* --> </dm:preconditions> <dm:forwardDifferences parseType="Statements"> <!-- Content: (definition|description)* --> </dm:forwardDifferences> <dm:reverseDifferences parseType="Statements"> <!-- Content: (definition|description)* --> </dm:reverseDifferences> </rdf:Description> </rdf:RDF> Here is a short definition of the parseType used above: * The content model of a property element with rdf:parseType="Statements" is the same as the content model of the rdf:RDF element. * The content generates the same RDF statements as if it appeared in an rdf:RDF element. Note: these statements may duplicate or contradict others outside the enclosing element. RDF processors are not entitled to eliminate such duplicates. The statements are in a separate "context". * The value of a property element with rdf:parseType="Statements" is a collection of resources of type rdf:Statement, representing the generated statements. - Arnold [1] https://www.langdale.com.au/CIMXML/DifferenceModelsR03.pdf (Sorry only in PDF for the moment.) [2] https://www.langdale.com.au/CIMXML [3] https://www.w3.org/DesignIssues/Notation3.html
Received on Wednesday, 28 March 2001 04:20:25 UTC