Last updated: 
3 May 2019

This is the transcript for the video: Transactional Digital Services Program: Second reference community webinar

Josh Burns, IP Australia

Hi guys, thanks for coming to our second webinar for TDS reference group. My name's Josh Burns, I'm the engagement manager for the TDS program. Our other presenter today, most of you guys may know him. It's Kieran MacGillicuddy who's Senior Project Manager for the TDS program. So I'm just going to run through a bit of a brief introduction. I'll cover a few housekeeping bits of information about today's webinar, how long we'll go for, et cetera. And I'll also cover our first event.

So our first activation event in the TDS reference group for those who weren't able to attend or watch the recorded webinar. Basically, in terms of housekeeping, we're using GoToWebinar for today's session, so it's probably best to leave any questions you have during the presentation or the webinar until the end. We've got a question point at the conclusion of the presentation. There's a couple of ways that you can ask questions, so we'll go through that at that point. You can either type a question or it's called Raise Your Hand and use that functionality. But we'll get to that at the end point. We can also take questions offline following the webinar.

It's probably important to know that today we're probably going to go for about thirty or so minutes, but it depends on how the demos run that Kieran will take us through, and any questions that we have at the end, but we're weary that it's lunchtime, you guys are busy. We don't want to keep you too long. Please let us know if you can, if you can't hear us, if you can't see our shared screens, and we'll try to get that sorted on the fly. The only other little bit of housekeeping information that I'd like to share is that we're recording today's webinar, so it will be available after the session today for any of your colleagues that want to watch the webinar and go through the slide pack. So we'll send an email at the conclusion of this event to everyone who's registered with the details but we'll also probably publish it to our website as well. And we'll include the first sessions just in case people need to catch up.

All right, so today's session, as most of you will be aware, we had our activation event in Sydney and Melbourne in February. These kick off events were well attended by the professional sector and also well attended by the software development community. The event covered a high level introduction to the TDS program and the drivers of the business case that we've got. We also summarised our program delivery roadmap with key delivery time frames, the program objectives at a high level, our commitment to establishing strong and regular communicational collaboration throughout the program, and some, I guess a few demonstrations of the technology platform that we're using, and we're keen to do that again today. In terms of where we're at currently for TDS, we've deployed patents, trademarks, and designs renewal APIs to production currently.

So we've got them available in our test environments, we've got mocking surfaces via the anypoint platform that Kieran will sort of demonstrate a little bit today. But if you guys are interested in testing or having a look at the specifications, please reach out. We're happy to register you if you're not already registered. But there's plenty of information on our website, and we'll share a URL later in this slide pack with that detail. Today's session Kieran will demonstrate our trademark and design renewal APIs that have been recently deployed to production. He's also going to demonstrate our soon-to-be-released smart trademark search API.

This is an API that's sort of come about as a result of a fair bit of feedback from our stakeholders about the fact that extracting data from RP Australia is a high value point to our customers. We're keen to get some value out via APIs. It's not all about transactional facing APIs. We're looking at providing data where we can as well. That's something that's imminent for delivery, but Kieran will show you a bit of a demo of that functionality.

Kieran MacGillicuddy, IP Australia

Thanks, Josh. Just before we jump into the roadmap, sorry, into the demonstration, we'll actually jump forward and just do the roadmap. Talk about where up to so far, what's coming next, and hopefully that'll serve and give people a bit of context. We've got up on the screen now our delivery roadmap, so the people that were at Sydney and Melbourne would have seen a version of this. So what you see there is for this current financial year, we're obviously into Q4 now, so you see in the top line there the patents line that we've got amendments and assignments showing there. As of next week we're starting work in examination requests, so effectively requests there around amendment status, and we also must tackle the first round of national phase entry. So that's what we're working on there, so we will be talking to customers about what the priorities are, what the issues are, all of those pieces.

And we're also currently working in trademark new applications. So as Josh said just before we've completed the renewal for patents, which is the Q2 line, renewal for trademarks and designs, which is the Q3 column there, so we'll be starting a new application, so we'll be very keen for people's feedback about the current new application process for trademarks, areas for improvement, areas you like, and even within that process, even the different kinds of trademarks and new applications, which are most important. Whether we need to look at images, word marks, the different variations there, what's the best one for us to focus on. And then, as you say, moving into the next financial year, we'll continue in the patent space. We'll continue on other versions of some amendments and assignments, and we'll also start picking up new applications. Within the trademark space, we'll then start looking at all of the amendment and assignment activities that relate to trademarks. Both of those lines will continue through for the rest of next financial year. Hopefully to complete by the end of fin year.

So you see that obviously there are more transaction types than what we've got on the slide there. So we will, based on your feedback, based on the data that we see coming through our systems, will choose the additional transaction types that we will be working on, and the order in which we work. So that's definitely an area that we're interested in your feedback and your input. So certainly, at the end of this meeting take some time to shout out what are the things that are most important to you or least important, and now you'll see that designs and plant breeder rights sit into the following financial year with the exception of design renewals. So as some of you may know, our original plan left design renewals into financial year 2020, 2021, and based on the feedback that we had per our engagement, people told us that design renewals was important to do as part of a whole package of renewal, so we brought that forward. So, similarly, if there are other transactions sit out into the right in the designs or plant breeder rights, that are very important to you, let us know, and we can look at where we prioritize those. I might just pause there for a second and ask if anyone has any questions on the road map. Maybe Sarah if you want to step through the process for that.

Yeah, so Paul, I see you've just raised your hand. I should be able to unmute you in just a moment so you can ask your question for the group.

Sorry Paul, we're just working on the buttons here. There you go Paul, you should be able to speak now.

Paul and Barney, Xenith IP

Hi guys, it's actually Paul and Barney here from Xenith, and Barney has a question.

Hi guys. Just on this road map, Josh, you mentioned at the start you're talking about data services that you'll be able to show us as well. On this road map, where do we see the ability to potentially get, say, the next action or the next renewal date on a property? Is that on this calendar somehow?

Kieran MacGillicuddy, IP Australia

I might just jump in there, Barney. You've picked up probably the biggest question, or the biggest thing that's not on there which is generally informational sort of APIs. So one of the things that's certainly came out really strongly in particularly the Melbourne workshop was the interest of people in accessing informational services. The one that we talked about quite a lot in Melbourne was around trademarks, and we've actually started work on that, so pending some sign off internally around basically the privacy act, we are hoping to be out into a testing phase with yourselves sometime in the next couple of weeks for trademark search. So that's the ability to search for a trademark and view the trademark details with the full range of details identically as though you were going through the Australian trademark search website, but through an API. That was one of the key bits of the event that we took out of Melbourne.

Barney, Xenith IP

That's excellent. What about for patents?

Kieran MacGillicuddy, IP Australia

We haven't got anything scheduled yet for patents and we haven't finished looking at that space. Our focus there was to improve the concept, the trademarks and then move on from that. The most likely one that we would pick up after trademarks is actually designs. Some of you might be aware, I think last week, one of the teams in Australia demonstrated the newest trade in design search, there's the YIPTA conference, so the technology that's built on is the same technology as the Australian trademark search so it would be quite quick and quite easy for us to add an API onto that. The underlying technology behind the AusPat search is quite a bit different. It will need a bit more analysis before we can make any firm commitments around when we do that.

Josh Burns, IP Australia

It's definitely something that's in scope though, Barney. We've heard the feedback and it's something that we want to provide across the properties so we'll provide some more information around AusPat and that API in the future but for now, doing some testing to trademark, we're calling it smart trademark API, search API, and then looking at designs in the near future after that. It's a start for us. Like I said, we've heard the feedback and we came to commit to achieving some of those things that weren't initially in our scope of work but we can see the value for customers in verifications process.

Kieran MacGillicuddy, IP Australia

Thanks, Josh. One place there and at, there's a bit of a tech mix-up on our side. We were hoping to demonstrate the trademark search option today but because we haven't actually pushed that into a public UIT that you can see, we actually can't get it from the laptop that we're running the presentation from. We do apologize for that. If you use the powers of your imagination, there's two API functions, one which is a search and one which is a retrieval of the details. You enter the search term through one of them and it returns a list of IDs that match that search term and then through the second API, you provide an ID and it returns the complete set of details from Australian trademark search and that does also include some minor details that I have published through the website so I know one of the key issues that people have raised since the Australian trademark search went live was around the status field and the information there.

We will actually be exposing in more detail the status as part of the API that's drawn directly from our backend systems. Sorry, I'm just looking at one of the questions that's just been launched by Paul. The question was, does the smart trademark API allow searching using a device-A file? Not in the first release. The first release will really be be around a quick search equivalent to what's on the website. It'll be a later release where we pick up advance search functionality. I see Paul's just brought in another question which is, the two key things required by a search are one, next action/date and two, status. So, per the retrieval of an API route, you will be able to see all of the dates that you would see through Australian trademark search so the different dates, grant dates, examination, et cetera. We aren't exposing the little UI element that sits on the left-hand side of that timeline. We are exposing all of the dates so that you can build your own or you can action those. The status field is a sense definitely exposed.

Josh Burns, IP Australia

It's probably also worth capturing, guys, that in terms of next action, even in our renewal API set for patents, trademarks and designs, we've got to get API service that you can essentially extract the next renewal date from that get all the posts that we send a response to. Once you've done that renewal transaction, we'll actually give you a response with the enforced day or the pay-to day, that actual which should help you at your end kick off that next event if that makes sense.

Kieran MacGillicuddy, IP Australia

We've got a couple other questions that've come through. One from Michael, will the owner details be available? The answer to that is yes. The details that are through Australian trademark search, so the name of the owner and the physical address of the owner will be available. Likewise, the agent or the address for the service. I think there's another question from Paul. And ideal search text fields? Yep, agree. Again, we'll keep building that search functionality app. There's a question from Ben. What protections are implemented over applicant privacy? There are known issues with data mining for scams, analysis of services, is it proposed to restrict access to address information? Really good question, and that's the key privacy consideration that we've been looking at internally.

The answer there is that it will be fully accessible through the API. However, the access to that API will be controlled and limited to organizations who agree to the terms of service for the API. It will be at the discretion of IP-Australia whether we suspend or revoke that access for abuse. So, we are very conscious that we are exposing peoples' potentially home addresses and that that is sensitive information. But we do also want to ensure that we meet our other requirements under the trademark act around inspection of the register. There's another question in from Paul. Paul's question, could we use the renewal get action for applications not initially renewed by the API? The answer to that, Paul, is yes. The renewal API allows you to renew any patent, design or trademark held with the office.

That's in a status that allows for renewal. Regardless of how that was originally filed, or how that's been renewed in the past.

Josh Burns, IP Australia

All right, so we might push forward. Are you ready for that demo, Kieran?

Kieran MacGillicuddy, IP Australia

Yep, give me one second. Sorry about that, guys. Sorry, I'm not sure about that. We might actually just through the next slide while I finish getting this set up. We can always read out Paul's comment there which was awesome, thanks guys.

Josh Burns, IP Australia

So we might jump to the next slide which is with me so, what we wanted to do, guys, in committing to collaborating with you and engaging with you regularly is obviously, this reference group forum is important in terms of doing that but we want to measure how we're going, how we're tracking with our engagement with you. What we wanted to do is I guess, do a quick poll on the screen. This is an interactive poll with some very brief questions about how we're engaging with you currently, how often you'd like these reference groups to be held, whether you prefer it to occur remotely like today's session and hopefully, we'll refine our ability in these webinars. It's our first go, so, or it's our second go, sorry, so we're a little bit rusty with some of the internal connections here.

Whether or not you guys see benefit in splitting the reference group in terms of two forums, so having a technical forum and a business-focused forum. We'll just display the first poll on screen and if you can just answer those questions, I'll give you a minute just to have a bit of a think and then we'll hit the next poll. Thank you very much. We'll just go ahead to the next one. These polls, guys, we'll take offline and we'll consider and we'll talk to you about what the feedback is like and it'll certainly help us refine our engagement process and help us review our strategy generally for the program. The frequency question here is fairly important to us.

We're trying to align our frequency of reference group sessions with our development sprints. At the moment, we're running three weekly sprints which is a bit of first here for in terms of agile methodology so that's something that we're continuing to refine but if you guys would like more, more frequent reference group sessions, we're happy to change that up. Thank you for that one. The second-to-last one we've got up here is around high you'd like to hear from us primarily, so, emails, for example, that's the subscription list, that you guys subscribe to currently and got the invite from. Today's webinar technology we can continue to use. Obviously face-to-face is very important and we've certainly got budget to make side visits where applicable and obviously we've also got the corporate website which we do share information on our APIs and our digital transformation journey at a high level. Last poll. This was about whether you guys feel the need to split this forum into a technically-focused group and a business-focused group. Just give you another 20 seconds there and we'll move onto our demonstrations. You ready for the demo?

Kieran MacGillicuddy, IP Australia

Give us a second and we'll switch over into the demonstration. Sorry, guys, technical difficulties again. We're just trying to work out if we can on the screen here. Sorry, guys. We're just stepping through here. We're working on two different laptops. It seems that we give myself remote control of the keyboard but not actually switch over to my screen. Bear with us for a couple of seconds more. We're just going to pop you on mute. Thanks. Okay, you should now be seeing my screen and hearing my voice. If there are any issues, please use the raise your hand functionality and we'll go through, I think we've got a couple comments there that we're, that are coming from Simon. We'll tackle those after the demo but anyone else has questions, please, flip them through as they occur to you and then we'll work through them afterwards. On my screen, you should be seeing the API portal. If we have everybody's screen up, you should see IP Australia and the IP right management B2B API. For those of you that were in Sydney or Melbourne, this'll be quite familiar to you. As you go into that API you can then, it'll load up and have a range of endpoints down the side and I'll just step into one that I've prepared earlier. As we look across on the left here, you'll see the endpoints and then as we go down through patents, we can open that up to the renewal option for patents and we've demoed that a few times, so we'll actually step through and you'll see that there's now a trademarks option where our mouse is over now and below that, designs. Jumping into the trademark option here, you'll see us here. We have the mocking service and the IP right identifier.

I've already prefilled the auth details. For those of you who are testing these or who want access to them, just get into contact with Josh over email. He'll set you up with credentials. As we then send through a transaction, you'll see in this case that you're receiving very similar information for a trademark as you would for a patent so we provide back the identifier, trademark application number, the renew-to date and the fee payable including both the breakdown of that fee so that will again line up with the information that'll come through on your bank statement effectively. Similar to the others, if you were sending in a malformed bit of content, then you'd get the error message but I will jump down into the designs piece. Again, in a similar way it's prefilled our details there. I can enter whatever number I like because we’re using the mocking service. You see above that it's updating. That number is the URL. We’ve got our headers in there, so content type, now body message. I'll submit that and receive back the response. Again, the identifier, the fee paid, a slightly different sequence for this one and then we have the application and the renew-to date. Across the parade, the intent is that they operate in a very similar way. To reduce the effort for any regards in integrating across more than one transaction type and we'll keep using that same kind of process across all of the other transactions as we move through them.

I do apologise that we can't demonstrate the search API. It is a fair bit more interesting that these ones which, if you've seen us demonstrate renewing one patent, you've seen us demonstrate renewing a trademark or any other patent. So, we will look to just take some screenshots of that and circulate that along with the recording of the webinar afterwards but apologies again from us. Just before we move on to the end, are there any questions before I hand back to the slide deck?

Josh Burns, IP Australia

We had a question from Ben. Sorry, Ben, we missed this question. You asked whether intends to replace access to both data products with the information provided over the garter APIs.

Kieran MacGillicuddy, IP Australia

Yeah, so the answer to that one Ben is that the bulk data products for now remain unchanged. This is about an additional way to access that data. We see it as part of the organization's strategy of moving towards APIs. We're not decommissioning bulk data or even talking about that at this stage. We're acting on the feedback from organisations like yourselves. It would be great to have that data by API down the track depending on uptake and customer feedback and our overall strategy.

We might look at the bulk data but there's no part of that at the moment and I might just, we'll jump down. I think Ben has just replied. Cool. Ben's reply was just thanking us for that answer and talk about the data. Absolutely agree. So definitely do reach out to Josh, Chris and the rest of the team. And now, we've got a string of questions, I think, that came through so we'll just skip through some of these, make sure that we haven't missed any, so just a couple of comments from Simon and, excellent. A comment from Simon that says no need to read all of Simon's. Way ahead of you. Give us five seconds and we'll just switch back across to the slide deck.

Josh Burns, IP Australia

So back with Josh, guys. We've just got this slide deck before we hit some more additional questions if you guys were eager to ask anything further. In terms of next actions and wrap up for our reference group, as Kieran said at delivery roadmap overview, our technical team, our product team are working on a number of different transactional APIs, most notably I guess, national phase entry in the patent space. Also examination request in the patent space and building towards new trademark applications and going forward. These are fairly significant transaction types that we're looking to develop. What I'd like to reiterate is that if you guys are keen to be involved, we can set up workshops individually with your firms about the journeys and about the particular that you've got within those transactions now and where you see some value in the future that we could potentially deliver in a TDS program for you going forward.

If you are keen to be involved, please reach out. Onscreen now we've just got, there's an email address there, MDB-TDS@ipaustralia.gov.au. That's our main inbox for any inquiries. If you're keen to be involved, please reach out. We can tell you up with some credentials to access the platform that we're using for APIs and you can start doing some testing. Start looking at the mocking services and getting a look and feel for what it is we're actually delivering. We've also got detailed information, as I said before, on our website. There's a couple of URLs there about our API documentation and a higher level introduction to why the TDS program has commenced, which most of you guys will be well and truly across. What we might do is just kick ahead to any additional questions that you guys might have. Again, feel free to type them through or raise your hand and we can go through a few questions.

Kieran MacGillicuddy, IP Australia

We've got a couple of questions. We've got one from John, what does API stand for? Great question. We probably didn't really cover that at the beginning so apologies for anybody else who's in that same boat. API stands for application programming interface. Now, what that means is a way for two computer systems to interact with each other. That's about us allowing the case management software of your firms to interact with the case management software of IP Australia. For those of you that are currently using, for example, Inprotech and B2B, it's effectively a more modern way to do that. For those of you who haven't had the opportunity to take up B2B, part of the reason we're moving towards APIs rather than the B2B system is because they're a lot easier to work with and that translates into it being faster for you to integrate and cheaper for you to integrate because it's less complex and the specialist skills that you might need are more generally available.

Moving on to a question from Paul. It'd be great to have a community/wiki-area somewhere to ask questions and open discussion. That was something that we did talk about in Melbourne, this workshop there. We have been investigating some options about that. Certainly, we'd be very interested in feedback from the whole group, really, about how useful that would be for them just so we can work out our prioritizing that over some of the other stuff that we're working on. I've got a couple of questions from Michael. The first was, can you provide example coding for PHP? The answer there is, I'm pretty sure yes, giving you five seconds just to check. Sorry, that's not included in the standard set of code examples. Through the portal, you will actually see code examples for curl, HTTP, JavaScript, Python-C and Java. That's the stuff that's provided by our platform.

Josh Burns, IP Australia

We could probably talk to our tech team following this webinar, Michael, and raise it with some of our developers and see whether or not that's something that we support and give you an example if possible or we can take that off and I'll make some contact with you, Michael.

Kieran MacGillicuddy, IP Australia

I think just wrapping that up as well, Michael or anybody else on the line, if there are additional languages that you are interested in, please let us know and that can again help shape our thinking about the tools and technologies that we use and the support that we provide to you. Now, there's another question from Michael, can you make prior art documents and that's something that we need to go away and think about so that's something that we'll definitely Josh and the team, probably make contact, talk with you a bit more about that understand it and then come back with a more fulsome answer.

Josh Burns, IP Australia

And Michael, we’ll capture that as a story and I'll make some contact with you about some of the detail that we need to look at but that would probably enter the patents, like the AusPat realm, in terms of accessing prior art for patents and it's something that yes, definitely would be considered but we need to just unpack it a little bit.

Kieran MacGillicuddy, IP Australia

So now, we've had a range of questions from a couple of people on the line. There certainly, if there are any more questions, now's the time, seeing how the floor is yours, or type out, rather, raise your hand, and if we don't have any more in the next minute or so we'll probably look to wrap it up there.

Josh Burns, IP Australia

Just while we're letting questions go, what I didn't mention before is next webinar, we're probably going to look at a webinar in June so it's a good chance then to have a look at where we're at in terms of, I think the particular folks at that point will be trademarking our vocations, so like I said, reach out about getting involved and providing some influence on that particular transactional journey and we can have some workshops individually, capture some users' stories and requirements that you guys may have that we can document for our technical team during that build. It looks like there's no more questions coming in, guys. We might wrap it up at that point.

As we keep saying, if you've got any questions following the session, please reach out. Send it to a TDS inbox or to me, if you've got my email. I can raise them with my team. As I said at the start of the webinar, an email will go out to everyone who registered today with a link to the recorded webinar, so if you want to share it with your colleagues or your partners, anything like that, that is able to be done. We'll also publish it on the website along with our first recorded webinar for people that need to catch up a little bit. Otherwise, it's been a good session today, guys. Apologies for the technical hurdles we faced at our end. We'll make sure they're refined for next time, but we appreciate your input and appreciate the time that you've taken out of lunch and we will talk to you very soon.