[Application-profiles-ig] Value Type and Value Space

Tue May 26 11:14:53 BST 2020

On 26/05/2020 08:00, Thomas Baker wrote: >Re:https://docs.google.com/spreadsheets/d/1wqHWwRE2wUvOKRThZu6HQ4WAIfBimsXCVCPo7CrSiLQ/edit>>Hi Phil,>>Some comments and ideas re: the recipe example...>>1. For column A: "Local ID" (instead of just "ID") could>helpfully reinforce the idea that the IDs are internal to>the application profile.Agreed >>2. For column D: "Value Type" is more expressive than>"Type" on its own (which invites the question "type of>what?").Agreed >>3. I have trouble seeing 'xsd:string' and 'xsd:date' as>actual values (in a Value Space) instead of as>_datatypes for_ values (ie, literal values). To put>it another way, the instance data would never have>the following triple:>>:x :datePublished xsd:date>>Rather, the datatype URIs seem to fit more naturally>under Value Type, and the Value Space can be left blank.Possibly. TBH I'm not sure which columns we really need >>4. I find Line 23, and most other lines that list multiple>values under Value Space (9, 38, 63), confusing>因为它们混合不同的值类型(why>Value Type is - unhelpfully, I would argue - left>blank): two real values (the entity references) and>one literal value datatype (which is not the same as>the literal value itself).>>The one multiple-value entry for Value Space that does>make sense to me is Line 43, ":Person :Organization".>However, this is not a value space of type "URI" but>rather something like "URI Picklist" (just like one>might have a "Literal Picklist" that listed>"animal", "vegetable", and "mineral").>>For Line 23, could one not perhaps simply repeat:>>:recipeInstructions Entity @HowToStep n n>:recipeInstructions Entity @HowToSection n n>:recipeInstructions xsd:string n n>>The CSV guidelines could say that when a property is>repeated within a shape, this means that the property>can be used with "this value", "that value", or the>"other value". This would sacrifice the notion that>:recipeInstructions _must_ appear in the data>(mandatory = "y"),This is a vital piece of information that I am not willing to lose >but any other option I see would>hit up against the limits of a CSV format that we hope>will be both simple and intuitive (for example, adding>a column that attaches "mandatory" not just to a>statement, but additionally to a property).Yes, having multiple entries in the Value Space column is the simplest most intuitive solution I can see >>5. In general, if there is a value (or value list) in the>Value Space column, should it not always have a Value>Type?Probably. The gaps are where I wasn't sure what the value type should be. I think in some cases it should be ENTITY and in others ANY might be the only option. Phil >>Tom>-- Phil Barker <http://people.pjjk.net/phil>.http://people.pjjk.net/philCETIS LLP <https://www.cetis.org.uk>: a cooperative consultancy for innovation in education technology. PJJK Limited <https://www.pjjk.co.uk>: technology to enhance learning; information systems for education. CETIS is a co-operative limited liability partnership, registered in England number OC399090 PJJK Limited is registered in Scotland as a private limited company, number SC569282. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.www.voudr.com/pipermail/application-profiles-ig/attachments/20200526/48f729ae/attachment.htm>