Page MenuHomePhabricator

ericP (Eric Prud'hommeaux)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Friday

  • Clear sailing ahead.

User Details

User Since
Jun 2 2018, 5:59 AM (219 w, 4 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
EricP [ Global Accounts ]

Recent Activity

Nov 24 2020

ericP added a comment to T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS.

For reasons that I believe have to do with additional data not changing already inferred facts (AKA monotonicity), certain OWL constructs MUST be expressed as a blank node. I think it's a great idea to remove blank notes wherever possible in wikidata but if you want the data to be conformant with OWL (and thus work in e.g. Protégé, OWLAPI, and some other tools), I believe you are stick using blank nodes for some OWL expressions.

Nov 24 2020, 9:07 PM · Community-consensus-needed, Wikidata-Query-Service, Wikidata
ericP added a comment to T267782: Incorrect use of blank node to represent unknown and no value in Wikidata.

I'll weigh in on 341 after we reach consensus here on whether our (Andra, Labra, DanBri, myself, ...) interpretation is correct that, at least for http://www.wikidata.org/entity/Q313093.ttl , a blank node represents the unknown value in https://www.wikidata.org/wiki/Q313093#Q313093$761f04ee-4d7f-d725-522a-85a3077bb47b . (Perhaps Andra can speak to "no value" cases.)

Nov 24 2020, 6:12 PM · Wikidata
ericP added a comment to T267782: Incorrect use of blank node to represent unknown and no value in Wikidata.

Oops, sorry, I failed to notice that.

Nov 24 2020, 8:50 AM · Wikidata

Nov 21 2020

ericP added a comment to T267782: Incorrect use of blank node to represent unknown and no value in Wikidata.

I don't believe it's the same. T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS is about the use of blank nodes in the representation of some OWL expressions. The OWL spec is very clear about saying that they have to be blank nodes so the decision was made by the OWL Working Group 15 years ago.

Nov 21 2020, 12:47 AM · Wikidata

Jan 24 2020

ericP updated subscribers of T243595: Run ShEx validation over Blaze API.

I believe Blaze supports the RDF4J API. @Jelabra , is that your understanding?
At any rate, every graph store has a fast and efficient getTriplesMatching(s, null, null) function, which is all we need.

Jan 24 2020, 6:51 PM · Wikidata, Shape Expressions
ericP created T243595: Run ShEx validation over Blaze API.
Jan 24 2020, 12:46 PM · Wikidata, Shape Expressions

Jul 30 2019

ericP added a comment to T214884: linking Schemas in statements.

ShEx schemas have an RDF representation. which round-trips everything except comments and whitespaces. For example, compare 3circRefPlus1.shex to 3circRefPlus1.ttl or 1dotIMPORT1dot.shex to 1dotIMPORT1dot.ttl in https://github.com/shexSpec/shexTest/tree/master/schemas.

Jul 30 2019, 8:36 PM · Wikidata-Campsite, Patch-For-Review, MW-1.34-notes (1.34.0-wmf.17; 2019-08-06), User-Ladsgroup, Wikidata, Shape Expressions

Jun 21 2019

ericP added a comment to T225996: JSON results serializer in Wikidata Query Service generates an extra "datatype" field.

The RDF model asserts that a literal with a langtag is considered to have a datatype of rdf:langString. The various formats state exactly how literals with langtags are written. The former specifies how APIs behave, such as a SPARQL FILTER DATATYPE("ab"@es) = rdf:langTag; the latter specifies that it's written {"type":"literal", "value":"ab", "xml:lang":"es"}. The rules for the XML and JSON results formats are that the implicit datatype of langtagged literals is omitted.

Jun 21 2019, 6:07 AM · Patch-For-Review, Discovery-Wikidata-Query-Service-Sprint, Wikidata-Query-Service, Wikidata

Jun 20 2019

ericP added a comment to T224962: Syntax highlighting for editing ShExC code (EntitySchema pages).

That's way cooler than mine. @Jelabra, can that be plugged in today?

Jun 20 2019, 7:16 AM · Wikidata, Shape Expressions

Jun 11 2019

ericP added a comment to T225492: extends SchemaExtension with fields capturing positive and negative examples.

The schema for human advertises both the entities which should pass and ones that should fail. This sort of QC can help keep the schemas themselves testable and more reliable over time and many editors.

Jun 11 2019, 10:19 AM · Wikidata, Shape Expressions
ericP updated subscribers of T224962: Syntax highlighting for editing ShExC code (EntitySchema pages).

I mocked up using the ace ShExC mode in an EntitySchema.

EntitySchema2-ace-edit.png (925×961 px, 179 KB)

The [x]s at the left come form an WebWorker which runs a shex.js ShEx parser asynchronously. If you uncomment the PREFIX decl at the top of the schema, you'll see the [x]s go away in ~.2 seconds.

Jun 11 2019, 9:32 AM · Wikidata, Shape Expressions

Jun 3 2019

ericP added a comment to T214884: linking Schemas in statements.

You might not want to add it to the data itself as people persuing different use cases will want to assert that the item is linked to different schemas. When I go to test whether a schema matches <SomeSpecialWidget>, I won't be interested in whether it matches everything else it's ever been used for, so at the very least, properties linking data to schemas are advisory and not required for the validation infrastructure.

Jun 3 2019, 7:03 AM · Wikidata-Campsite, Patch-For-Review, MW-1.34-notes (1.34.0-wmf.17; 2019-08-06), User-Ladsgroup, Wikidata, Shape Expressions

May 24 2019

ericP added a comment to T221604: remove control menu in shex simple tool.

I believe that removing the results section makes it basically impossible to diagnose errors.
I added a switch ?ui=full to enable the results section and the control menu. You can see it in use in a video. Does the behavior without that switch close this issue?

May 24 2019, 8:07 AM · Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)), Shape Expressions, Wikidata

May 23 2019

ericP added a comment to T223997: Add reserved IDs to EntitySchema.

propose adding E12345 to the list 'cause it's not uncommon to have to model three interconnected schemas and E123{,4{,5}} is a nice mnemonic for a scratch space for that.
other than that, +1 to calling this done.

May 23 2019, 10:34 AM · User-Michael, Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)), Wikidata, Shape Expressions