Meeting minutes
recap
mel: last time's minutes: https://
<phila_> My slides
Barcodes on the web
phila_: GS1 known for
barcodes since 1974
… heavily involved in retail, marketplaces,
healthcare, transport and technical industries
… and with a global footprint
phila_: lots of different
barcodes on products, often more than one
… [slide 5]
phila_: Digital link is
single identifier resolvable as URL
… [slide 8]
… concetenating identifiers into a single URL
phila_: [slide 9] ideally we will support multiple redirection
phila_: [slide 13] - how does it work?
phila_: three kinds of resolver
<Ian> Web Linking spec at IETF
phila_: 1) Default
… 2) Ask for specific link type
… 3) Give me everything
<Ian> Linkset: Media Types and a Link Relation Type for Link Sets
phila_: Linksets have ideas in common with DIDs
phila_: [slide 22] - linkType parameter
phila_: So what?
… at least 4 multinational companies committed to
using GS1 Digital Link
… use cases for BG?
… product ID
ian: Are any browser vendors interest in the digital link initiative?
phila_: I don't believe that we have approached them
mel: what's the customer
journey?
… how does it work on line?
trent: what's the governance process?
phila_: we built it as
decentralised system
… we operate a resolver, but we'd expect big retailers
to run their own resolver
… tl;dr - whoever runs the resolver chooses how the
link is resolved
… our starting point is the domain name
dezell: where is linkset being standardised?
phila_: we are working at IETF
dezell: I noticed you put two different identifiers: one in the URL and one in the query string
phila_: things that are separated in the path are increasingly granular, whereas the query string is in the used for descriptive things (like expiry)
<Ian> nicktr: One thing that might be valuable to online retailers: product artwork could be provided with QRs embedded in the product artwork
mel: is it fair to say that this is a hybrid between barcode and URL?
phila_: it's an entry point
… the more important thing is that is lets consumers
see information that *isn't* on the box
mel: but retailers might be worried about journeys outside their site
phila_: we can use modals and iframes
ian: having an identifier
that can provide redirection is great
… having things built into browsers can make things
less cumbersome
… so there's a data view and a UX view
phila_: language negotiation is perfectly possible but lots of sites don't do it well
mel: let's move on
recruiting more members
mel: talking to people in
our networks
… so I've put together a little cold call mail that I
wanted to share to get your feedback
mel: text reads
Hi <persons’s name>,
I’m part of the W3C’s business merchant group which has been created to discuss issues and topics related to ecomm.
Because you work for <organisation name> which operates online B2B/B2C I thought the discussions about improving online transactions,
emerging technology, payment solutions would be of interest to your organisation.
<Organisation name>’s input would definitely enrich the conversation and help to shape the recommendations the group delivers.
Have quick read about the group <link> and we can discuss further,
Thanks,
laura: where do we fit at
MAG?
… it needs to be about payments
… whereas the BG is talking across wider topics
<Ian> (I read this as Laura saying "our priority would be payments"...good to hear and would be interested in hearing priorities from others as well)
linda: these are not
prosperous times - difficult to recruit and retain our own members
… fees make this more difficult
dezell: I have reached out
… and will continue to do so
phila_: difficult to promote
another standards org from my own - but not impossible
… and on use cases, receipts and inventory are very
relevant, rather than payments
<nicktr> next meeting: Monday 15th Feb