- From: Phil Barker <phil.barker@hw.ac.uk>
- Date: Fri, 19 Aug 2016 09:12:57 +0100
- To: Wes Turner <wes.turner@gmail.com>, DCMI <sasutton@dublincore.net>
- Cc: "public-schema-course-extend@w3.org" <public-schema-course-extend@w3.org>
- Message-ID: <7046db0d-d21b-e2a4-6fc9-572809fab974@hw.ac.uk>
On 19/08/2016 02:30, Wes Turner wrote: > It would be great to be able to include accessibility markup this in > an initial guide to implementing Course markup. > Agreed. You should add Liddy Nevile to your people, she has worked on accessibility of learning resources all the way from IMS Access for All through to ISO/IEC 24751, also Madeleine Rothberg who has worked on schema.org -related accessibility. (chaals@yandex seems to be the schema.org expert closely involved). I don't know where are the best forums for engaging with them and others with similar interest, but I see you also posting at https://github.com/schemaorg/schemaorg/issues/254#issuecomment-240900602 which seems one reasonable place. I'll keep and eye on that for developments. Phil > People: > > - Domain experts > - Which organizations have an expert to help out with this? > - Schema.org experts > - @danbri > - @rjw > - Schema.org amateurs > - @westurner > - > - Data publishers > - > - Data consumers > - Data presenters: e.g. search engines, aggregator sites > > User stories: > > - Data publishers can specify available accessibilityPhysicalFeatures > (at least) for Places and Events (**URLs**) > - Data presenters can display (themed) icons for available services > (**URLs**) > - Data consumers can locate Place and Events with specific > AccessibilityPhysicalFeatures (**URLs**) > > Technical approach: > > - Enumeration > AccessibilityPhysicalFeature > - List of Enumeration URLs for known "AccessibilityPhysicalFeatures" > - @accessibilityExperts: catalog known accessibility features > - @schemaorgExperts: should these be Enumerations in schema.org > <http://schema.org> core or listed in a wiki page? > - Property: "accessibilityPhysicalFeature"? d: {Place,Event} > - @schemaorgExperts: Relation to amenityFeature r: > LocationFeatureSpecification > > ... I'll copy this to this issue: > > "Accessibility of places" > https://github.com/schemaorg/schemaorg/issues/254 > > On Thu, Aug 18, 2016 at 7:34 PM, DCMI <sasutton@dublincore.net > <mailto:sasutton@dublincore.net>> wrote: > > I'm happy to leave accessibility to the people who understand it best. > > Stuart > > Sent from my iPhone > > > On Aug 18, 2016, at 10:30 AM, Phil Barker <phil.barker@hw.ac.uk > <mailto:phil.barker@hw.ac.uk>> wrote: > > > > Hello again, I propose that we do not address accessibility > requirements as part of the course extension (we can use > properties inherited from more general accessibility work). > > > > > > We have use cases relating to accessibility at > https://www.w3.org/community/schema-course-extend/wiki/Outline_use_cases > <https://www.w3.org/community/schema-course-extend/wiki/Outline_use_cases> > > > > namely that it should be possible to find course where the > searcher is concerned about physical and cognitive accessibility > features, controls, API, hazards. > > > > This leads to requirements around identifyingaccessibility > features, controls, API, hazards of resources (i.e. CreativeWorks) > used in delivering the course, in any Events that are part of the > course and at any locations where the events are held. > > > > There are other people with specialist knowledge for > accessibility who have dealt with the accessibility of > CreativeWorks (so we can just apply that to Course and to any > materials used in the course), and there is an open issue relating > to accessibility of Places (and hence events at those places), > https://github.com/schemaorg/schemaorg/issues/254 > <https://github.com/schemaorg/schemaorg/issues/254> > > > > So, are we happy to leave accessibility to the accessibility > people and use the outputs of their work for Course and > CourseInstance as they are inherited from CreativeWork, Event etc.? > > > > Phil > > > > > > -- > > Phil Barker @philbarker > > LRMI, Cetis, ICBL http://people.pjjk.net/phil > > Heriot-Watt University > > > > Workflow: http://www.icbl.hw.ac.uk/~philb/workflow/ > <http://www.icbl.hw.ac.uk/%7Ephilb/workflow/> > > > > > > -- Phil Barker @philbarker LRMI, Cetis, ICBL http://people.pjjk.net/phil Heriot-Watt University Workflow: http://www.icbl.hw.ac.uk/~philb/workflow/
Received on Friday, 19 August 2016 08:13:42 UTC