rdf* ?

31 views
Skip to first unread message

Bohms, H.M. (Michel)

unread,
Jan 22, 2020, 3:29:46 AM1/22/20
to topbrai...@googlegroups.com

I understood earlier tbc now had experimental support for RDF*.

If so, how can this be tested (ie I see no “New RDF*”)?

 

Think RDF* will greatly enhance/simplify metadata modelling on the actual property instantiation (no more objectification needed).

 

I was wondering how it could have the same benefits for meta modelling but then on property definition level.

Could we add ie this meta data on a triple like:

 

“height rdf:type owl:DatatypeProperty”?

 

Thx Michel

 

 

 

 

 

Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist

T +31888663107
M +31630381220
E michel...@tno.nl

Location

 

cid:image001.gif@01D5D106.5007E000

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.

 

 

 

 

dprice

unread,
Jan 22, 2020, 4:17:27 AM1/22/20
to topbrai...@googlegroups.com
The 6.3 release notes say:

EDG 6.3 RELEASE

TopBraid EDG version 6.3 delivers a new user experience for editing and viewing asset collections. We are excited about delivering a significantly enhanced user experience and believe you will find the UI looking sleeker and the experience more enjoyable!

Users will now be able to customize and personalize page layouts and get easier access to different features all within a flexible single page. In particular, this change simplifies and streamlines creation of ontology models. We are attaching to the release notes several presentations that will help you familiarize yourself with these changes.

EDG version 6.3 also continues to deliver new functionality. A notable addition in 6.3 is the ability to annotate facts with additional statements. This can, for example, support capturing a provenance of a business term definition or an effective date for any value. Annotations can be made for any property value – relationship or attribute. Further, 6.3 improves support for repeated import and profiling of data sources. It also makes it easier to version a group of collections in one step. Improved APIs now provide GraphQL access to ontology models and to the change history (teamworks) data. These and other new features are described in more detail below.

Key Improvements of 6.3

Support for Reification

Users can now annotate facts with additional statements. This can, for example, support capturing a provenance of a business term definition or an effective date for any value. Annotations can be made for any property value – relationship or attribute. Properties that can be reified and the kind of annotations that can be made are identified in ontology models.

Technically, EDG now supports RDF* data model. Annotations can be queried in SPARQL. To ensure standards compliance and interoperability when data is exported in RDF from EDG, reified statements are exported as RDF statements.

Cheers,
David

On 22 Jan 2020, at 08:29, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

I understood earlier tbc now had experimental support for RDF*.
If so, how can this be tested (ie I see no “New RDF*”)?
 
Think RDF* will greatly enhance/simplify metadata modelling on the actual property instantiation (no more objectification needed).
 
I was wondering how it could have the same benefits for meta modelling but then on property definition level.
Could we add ie this meta data on a triple like:
 
“height rdf:type owl:DatatypeProperty”?
 
Thx Michel
 
 
 
 
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
 
 
 
 

-- 
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5b9bbb6f1e6a4118b03c320a9fb3b7f1%40tno.nl.


Bohms, H.M. (Michel)

unread,
Jan 22, 2020, 4:45:47 AM1/22/20
to topbrai...@googlegroups.com

Right, that is exactly what I saw:

“Technically, EDG now supports RDF* data model. Annotations can be queried in SPARQL. To ensure standards compliance and interoperability when data is exported in RDF from EDG, reified statements are exported as RDF statements.”

 

 

And then I thought...how can I now model according to RDF* in TBC, how can I say put a property to a triple (indirectly to a property) in TBC...or how can I serialise acc. to Turtle*...or query acc. to Sparql* etc.

 

or is this an EDG-only thing for now?

 

Thx Michel

 

 

 

 

Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist

T +31888663107
M +31630381220
E michel...@tno.nl

Location

 

dprice

unread,
Jan 22, 2020, 5:46:27 AM1/22/20
to topbrai...@googlegroups.com
The way this is implemented in EDG 6.3 is using dash:reifiableBy which references a class that defines the annotations properties a reifiable property can have attached. See


Where you’ll see that URI-based reification:

can serve as an implementation technique for RDF* that doesn't require changes to RDF itself or the implementations of APIs and tools

We have customers who have requested support for reification so they can annotation properties with metadata and this is the first support of that in the EDG product itself

Note that this is not full support for RDF* (which is not a standard) and would that require extensions to Turtle, SPARQL, etc.

Note that the EDG reification can be exported as standard RDF Statement reification using the Sorted Turtle RDF exporter to provide interoperability with other apps.

I don’t think Composer supports a nice way to create the URI-based reification, so yet it’s an “EDG-only” feature in 6.3.

More to come, of course, as customers provide feedback on their use of reification/annotation of properties.

Cheers,
David

On 22 Jan 2020, at 09:45, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Right, that is exactly what I saw:
“Technically, EDG now supports RDF* data model. Annotations can be queried in SPARQL. To ensure standards compliance and interoperability when data is exported in RDF from EDG, reified statements are exported as RDF statements.”
 
 
And then I thought...how can I now model according to RDF* in TBC, how can I say put a property to a triple (indirectly to a property) in TBC...or how can I serialise acc. to Turtle*...or query acc. to Sparql* etc.
 
or is this an EDG-only thing for now?
 
Thx Michel
 
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist

Irene Polikoff

unread,
Jan 22, 2020, 9:59:47 AM1/22/20
to topbrai...@googlegroups.com
Correction, it references a node shape that defines what facts you want to add to specific triples.

First, create a Node Shape e.g., Effectivity with properties effective start and end.

Then, go to the property shape for the type of triples you want to annotate with effective dates (eg., works for property for a Person) and connect it to the node shape using reifiable by.

I believe this is covered in the EDG users guide for ontologies, but I am not in front of my computer, so can’t provide a link.

It is also covered in the slide attachment to this recent webinar https://www.topquadrant.com/what-is-new-in-topbraid-edg-6-3/

Sent from my iPhone

Holger Knublauch

unread,
Jan 22, 2020, 1:57:55 PM1/22/20
to topbrai...@googlegroups.com


On 21/01/2020 23:45, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:

Right, that is exactly what I saw:

“Technically, EDG now supports RDF* data model. Annotations can be queried in SPARQL. To ensure standards compliance and interoperability when data is exported in RDF from EDG, reified statements are exported as RDF statements.”

 

 

And then I thought...how can I now model according to RDF* in TBC, how can I say put a property to a triple (indirectly to a property) in TBC...or how can I serialise acc. to Turtle*...or query acc. to Sparql* etc.

 

or is this an EDG-only thing for now?


The TBC user interface does not support these reified triples at the moment, but EDG forms in the new 6.3 editor do. We do not support the Turtle* or SPARQL* syntax but plan to support some variation of that for 6.4.

Holger


Reply all
Reply to author
Forward
0 new messages