- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Jan 2017 03:05:01 +0000
- To: public-poe-archives@w3.org
@nitmws (and all!) - Some comments on the Constraint changes: 1 - Would the new label for "Absolute Position Asset" read better as "Absolute Asset Position"? 2 - Same question for the two "narrower" absolute positions 3 - Can the URI for /absoluteSpatialPositionAsset be /absolutePositionSpatial to make it consistent with /absolutePosition (and not too long)? 4 - Same question for Temporal 5 - Question 1-4 above repeated for the "Relative Position" terms 6 - Would the new label for "Absolute Size Asset" read better as "Absolute Asset Size"? 7 - "Action Datetime or Period" -> "Datetime Action Period" 8 - Assume that "eventEndPeriod" is no longer supported? 9 - "Action Event" -> "Event Action" 10 - I am not clear why we need "File Format After" - If we had a "translate" Action, with constraint "File Format" = "PDF", then that is the same as "File Format After" ? 11 - The same question for "Language After" ? 12 - In "Media" can use use "Category..." instead of "High level type..." 13 - "Product" -> "Product Context" 14 - "Industry" -> "Industry Context" 15 - Why do we need "Named Geospatial Area" - isn't this just a different datatype for the rightOperand? That is, if you use long/lat in "Spatial" then you should use an appropriate datatype? 16 - "Virtual IT Communication Location" -> "Virtual Domain Location" 17 - Assume all the "leftOpResource1" stuff can be removed as we now have RightOperandReference? -- GitHub Notification of comment by riannella Please view or discuss this issue at https://github.com/w3c/poe/issues/67#issuecomment-273965648 using your GitHub account
Received on Friday, 20 January 2017 03:05:07 UTC