[Application-profiles-ig] ShExStatements first version

Sun Mar 29 10:51:01 BST 2020

你好,凯伦,现在ShExStatements inpu也可以t tabular formats for Application Profiles for generating ShEx. Inspired from your example, here is the Application Profile for language [1]. The columns may have all these terms: 'Entity_name, Property, Property_label, Mand, Repeat, Value, Value_type, Annotation' as proposed here [2]. To generate ShEx from Application Profile, the user has to pass the option -ap to clarify that the input CSV file follows the Application Profile format. Taking into account that the columns for Application Profile is still under discussion, this may mean further changes to ShExStatements in future. 1.https://github.com/johnsamuelwrites/ShExStatements/blob/master/examples/languageap.csv. 2.https://github.com/dcmi/dcap/blob/master/prototypes/wikidatapainting/E130b.csv3.https://github.com/johnsamuelwrites/ShExStatements/blob/master/README.mdBest Regards, John Samuel On Tue, Mar 24, 2020 at 10:00 PM John Samuel <johnsamuelwrites at gmail.com> wrote: >Hi Karen,>>First of all, thank for your feedback. Here are my responses to the two>questions:>>1. Yes, ShExStatements is currently using a single position for both value>and value types, as the goal is to simplify writing ShEx (by reducing the>column count). However, if you are separating them for the application>profiles, such a possibility need to be further explored.>2. A more verbose template is doable. However, I need to explore it a bit>more, on how to integrate such a concept to ShExStatements in a more>generic manner (like mapping templates for different use cases).>>Best Regards,>John Samuel>>On Tue, Mar 24, 2020 at 4:21 PM Karen Coyle <kcoyle at kcoyle.net> wrote:>>>Hi, John, thanks for this! I'm trying to make the mapping from our>>template to yours. It appears that your template reads:>>>>entity | property | value | cardinality | comments>>>>Whereas ours reads (leaving out the unused elements):>>>>entity_id | property | value_type | value | mandatory | repeatable |>>annotation>>>>Two things immediately jump out as ones we have recently discussed:>>>>1. We are separating the value type and the value. Am I correct that you>>are using a single position for those? I see things like:>>>>@painting,P31,Q3305213>>@painting,P572,xsd:dateTime>>@painting,P170, at creator>>@creator,P2561,LITERAL,#name>>>>in which Q3305213, xsd:dateTime, @creator, LITERAL all occupy the>>"value" column.>>>>2. We are separating the cardinality functions of mandatory and>>repeatable because we figure that many people don't understand the more>>compact notation, either the UML-type notation of "1..n" nor the ShEx>>values borrowed from regular expressions.>>>>Would it be possible to create a transform that makes use of our more>>verbose template? (We would have to decide what to use for the values of>>mandatory/repeatable - "y/n" or "1/0" or "T/F" ... )>>>>Thanks,>>kc>>>>>>On 3/23/20 5:34 AM, John Samuel via Application-profiles-ig wrote:>>> Hi,>>>>>> The first version of ShExStatements is now released:>>>https://github.com/johnsamuelwrites/ShExStatements>>>>>> The main goal is to help newcomers easily write shape expressions. The>>> users write a CSV file and ShExStatements will translate it to a shex>>file.>>>>>> Take for example, a CSV file concerning a language (with prefixes):>>>>>https://github.com/johnsamuelwrites/ShExStatements/blob/master/examples/language.csv>>> is translated to a shape expression>>> (https://github.com/johnsamuelwrites/ShExStatements#quick-start). As>>you>>> can see, there are five columns. Columns 3,4 and 5 are empty for>>> prefixes. Columns 1, 2, 3 are mandatory for others. Column 3 can be .>>> (to say any value). Column 4 is for cardinality (+,*) and column 5 for>>> comments.>>>>>> More examples can be found here:>>>https://github.com/johnsamuelwrites/ShExStatements/tree/master/examples>>>>>> In my opinion, it's possible to consider such CSV files for describing>>> application profiles.>>>>>> Please let me know if you have any questions/remarks.>>>>>> Best Regards,>>> John Samuel>>>https://johnsamuel.info/>>>>-->>Karen Coyle>>kcoyle at kcoyle.nethttp://kcoyle.net>>skype: kcoylenet>>>>>-->Best Regards,>John Samuel>https://johnsamuel.info/>-- Best Regards, John Samuelhttps://johnsamuel.info/-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.www.voudr.com/pipermail/application-profiles-ig/attachments/20200329/6e16ab32/attachment.htm>