13:54:32 <RRSAgent> RRSAgent has joined #adapt
13:54:36 <RRSAgent> logging to https://www.w3.org/2024/07/30-adapt-irc
13:54:36 <Zakim> RRSAgent, make logs Public
13:54:37 <Zakim> please title this meeting ("meeting: ..."), janina
13:54:49 <janina> Meeting: WAI-Adapt Teleconference
13:54:56 <janina> Date: 30 Jul 2024
13:55:32 <janina> Chair: Lionel_Wolberger
13:56:38 <janina> agenda+ Introduction, logistics. Any Updates?
13:56:38 <janina> agenda+ TPAC Preps
13:56:38 <janina> agenda+ WKD Github actions and PRs
13:56:44 <Lionel_Wolberger> Lionel_Wolberger has joined #Adapt
13:57:09 <janina>  present+
13:57:15 <janina> zakim, who's here?
13:57:15 <Zakim> Present: janina
13:57:17 <Zakim> On IRC I see Lionel_Wolberger, RRSAgent, Zakim, janina, Roy_, gb, dmontalvo
14:01:30 <roy__> roy__ has joined #adapt
14:01:43 <Lionel_Wolberger> agenda?
14:02:32 <Lionel_Wolberger> present+
14:02:51 <Lionel_Wolberger> scribe+
14:02:54 <matatk> matatk has joined #adapt
14:03:05 <Lionel_Wolberger> agenda+ Symbols status
14:03:07 <janina> present+
14:03:08 <matatk> present+
14:03:29 <Abhinav> Abhinav has joined #adapt
14:03:36 <Abhinav> present+
14:07:38 <matatk> agenda?
14:07:51 <matatk> zakim, who's here?
14:07:52 <Zakim> Present: janina, Lionel_Wolberger, matatk, Abhinav
14:07:53 <Zakim> On IRC I see Abhinav, matatk, Roy, Lionel_Wolberger, RRSAgent, Zakim, janina, Roy_, gb, dmontalvo
14:07:59 <Lionel_Wolberger> scribe+
14:07:59 <janina> scribe+
14:08:12 <janina> zakim, take up item 1
14:08:12 <Zakim> agendum 1 -- Introduction, logistics. Any Updates? -- taken up [from janina]
14:08:23 <janina> Lionel_Wolberger: Suggests calendar review ...
14:08:36 <janina> Lionel_Wolberger: Any regrets next week? 6 August?
14:08:42 <janina> Lionel_Wolberger: How about 13 Auguswt
14:08:48 <janina> [crickets]
14:09:13 <janina> matatk: Expects to be away for a week perhaps late August, perhaps early September
14:09:51 <janina> zakim, next item
14:09:51 <Zakim> agendum 2 -- TPAC Preps -- taken up [from janina]
14:10:49 <janina> janina: Recalls mtg with WHAT
14:10:56 <janina> matatk: Yes, both AAC and WKD
14:11:17 <janina> matatk: Hoping we'll have greater clarity on WKD by TPAC
14:11:47 <janina> matatk: Meanwhile, we (APA) need to clarify our meeting schedules on a wiki page as in past years
14:12:12 <janina> matatk: Recalls our conversation re a flyer to promjote WKD
14:12:26 <janina> matatk: More AAC flyers would be helpful
14:14:35 <janina> matatk: Breakout? Suspect WKD not quite ready
14:15:03 <janina> matatk: More useful to focus on WHAT mtg for WKD
14:15:20 <janina> matatk: AAC we have UA solved; not phps yet registry
14:16:04 <janina> janina: Not sure we should. What would we say that we haven't said before?
14:16:21 <janina> matatk: Generally like breakouts, but agree with Janina
14:17:13 <janina> Lionel_Wolberger: Hearing WHAT gets our focus
14:18:06 <janina> Lionel_Wolberger: Double checking ...
14:20:01 <janina> Lionel_Wolberger: Last year we WKD was kicked off in a largish technical WHAT mtg;[no one recalling]
14:22:55 <janina> zakim, next item
14:22:55 <Zakim> agendum 3 -- WKD Github actions and PRs -- taken up [from janina]
14:23:16 <janina> matatk: A few updates ...
14:23:35 <janina> matatk: Reading material from GS1 -- still reading
14:24:37 <janina> matatk: Still following up from AC mtg esp with person with concerns
14:24:53 <janina> matatk: Am following up
14:25:41 <janina> matatk: Recalls concern re explainer using terms "goals" and "non goals"
14:25:48 <janina> matatk: Reason is TAG Explainer
14:27:48 <janina> Lionel_Wolberger: Is this the time to edit Explainer for that?
14:29:10 <janina> Abhinav: Have read gs1
14:29:34 <janina> subtopic: GS1 Materials
14:30:42 <matatk> Abhinav: Gone through the email and linked materials at a high level. I can give you an overview.
14:31:44 <matatk> ... First of all, a key concept: HATEOS - hypermedia as the engine of application state.
14:32:25 <matatk> ... Commonly used in the context of RESTful APIs. You may fetch a resource, but not know what related ops you can do on the resource. Instead of the client knowing what it can do (hardcoded) the response may include links that indicate what can be done.
14:32:31 <Lionel_Wolberger> s/HATEOS/HATEAOS
14:34:07 <matatk> ... E.g. if you ask for a person you may get details like name, age, etc. and links to other things like address, or employer. Links can be to ops or further data.
14:34:14 <matatk> rrsagent, make minutes
14:34:15 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/30-adapt-minutes.html matatk
14:34:47 <Lionel_Wolberger> RFC 9264
14:35:02 <Abhinav> https://www.rfc-editor.org/rfc/rfc9264.html#name-json-document-format-applic
14:35:09 <matatk> Abhinav: Main thing Phil linked to is RFC9264.
14:35:23 <matatk> scribe+
14:35:25 <matatk> rrsagent, make minutes
14:35:27 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/30-adapt-minutes.html matatk
14:36:15 <matatk> Abhinav: The main thing this describes is a way to group links. E.g. if you have appendices, A and B, the RFC gives you the ability to create a link set that contains two line items, relating to the two appendices.
14:37:02 <matatk> ... So you are linking related info together, and expressing the relation between the info.
14:37:06 <matatk> rrsagent, make minutes
14:37:07 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/30-adapt-minutes.html matatk
14:37:39 <matatk> matatk has joined #adapt
14:37:49 <matatk> rrsagent, make minutes
14:37:51 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/30-adapt-minutes.html matatk
14:37:56 <matatk> scribe+
14:37:59 <matatk> present+
14:39:09 <janina> matatk: Q: Seems relevant, but where are linksets defined? Doc level? Each page? Or domain level? Impact on scope?
14:40:09 <janina> Abhinav: pointer to separate doc with definitions
14:40:17 <janina> matatk: Like a site-map?
14:42:10 <janina> matatk: We have keyword semantics; we want to annotate link with semantic meaning but also ...
14:42:35 <janina> . a way to next  or structure them
14:42:59 <janina> . Sounds promissing for that
14:45:23 <janina> matatk: Discovery remains a concern
14:46:43 <janina> matatk: We need nesting and ability for discovery to meet COGA use cases
14:48:02 <janina> . sounds we should try an example here to compare with wk uri
14:49:00 <matatk> scribe+
14:49:18 <matatk> Abhinav: Moving on to the IANA registry of link relations.
14:50:10 <matatk> ... The link relations provide essentially an enum of possible link types (with human-readable definitions, to explain what each keyword means).
14:50:28 <matatk> ... It probably doesn't have all of the things we talked about - we have two options:
14:50:42 <matatk> ... (1) ask IANA for additional relation values
14:51:12 <matatk> ... (2) create our own link type and use that to namespace our destination types (this is what GS1 did)
14:51:13 <Abhinav> https://www.iana.org/assignments/link-relations/link-relations.xhtml
14:53:38 <matatk> Abhinav: There are other links, but one more important one for now...
14:53:52 <matatk> ... They're also proposing well-known URLs.
14:54:42 <matatk> ... This RFC9264 could be used to provide a link and a relationship, but for very obvious ones, like home page, you can use a query parameter to find out more info. They're doing a redirect to that well-known URL.
14:55:19 <matatk> ... e.g. for a food product, you could add a query parameter to go to the allergy info - that will cause the app to redirect to that info, via a well-known URLs.
14:55:49 <matatk> ... So we can use well-known URLs for discovery, and for this part - what they call a 'resolver'
14:56:59 <matatk> Lionel_Wolberger: We have a steep hill to climb conceptually - years ago the rel attr was brought to our attention, and now we're seeing different uses for it, and now link sets. The summary was super helpful. An action to digest this would be good.
14:58:02 <matatk> ... We may need to refine the use case. We made the traditional tech mistake of seeing the technical approach, and thinking 'we can use this' - need to think about it from the perspective of a site visitor, 'as a site visitor, I want to be able to access certain places quickly...'
14:58:28 <matatk> ... Good news, as it sounds like we have many routes to success, and we have to pick the best.
14:59:17 <matatk> ... Let's review, and use the list.
15:00:38 <Lionel_Wolberger> zakim, end meeting
15:00:38 <Zakim> As of this point the attendees have been janina, Lionel_Wolberger, matatk, Abhinav
15:00:40 <Zakim> RRSAgent, please draft minutes
15:00:41 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/30-adapt-minutes.html Zakim
15:00:47 <Zakim> I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent.  Goodbye
15:00:48 <Zakim> Zakim has left #adapt