Last updated: 
24 June 2019

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

 

Josh Burns, IP Australia

Hi all. It's Josh Burns here, just starting off our June TDS webinar. I might just give it one minute. We've only got 14 attendees at the moment. So we've had about 50 people register in terms of participation. So, I'll just lead in fairly slightly with some housekeeping stuff, and we'll get started. I'm trying not to waste too much of your time, but today's webinar event I guess has got a little bit of a demonstration from one of our developers on our smart trademark search API, which we weren't able to demonstrate last time. We've sorted those technical issues out and we've got that available today. So in terms of housekeeping, just a couple of different things that I covered last time. But for new participants, we're using GoToWebinar for the session today. In terms of questions, we've got a, a hand up, process in GoTo that a lot of you guys used last time. But people can also draft questions via text and send them into us that we can read out and answer as we go.

 

If possible, it might be best to leave the questions to the end of today's webinar, just so we can unpack them properly and not sort of get lost. The webinar should run for about 30 to 40 minutes roughly. Again, I don't wanna waste people's time. We'll get out what we can in terms of valuable information and let you guys go and have your lunch. Please let us know via text or hand up if you can't see the desktop that we're sharing or hear us and we can try to sort something out fairly quickly. The webinar, today's webinar like others that we've had, will be recorded so it's available after the event today. We'll flick an email at the end of the event to everyone who registered. But it will be on our website for people to access and catch up on.

 

So we might get started 'cause we are a minute or two over. So today's session guys, we're gonna cover quite a bit in terms of upcoming releases. We've got, as I said, a demonstration of, smart trademark search API that Aidan is gonna run us through. There's been significant interest in that API instance and it's out to public test at the moment. So Aidan's gonna run us through the functionality, stage one functionality and we'll talk about, you know, possible enhancements to that API as we go.

 

In terms of a general update for TDS the program. As I mentioned in our last webinar, we've got patent, trademark and designs from new APIs out in production. If you guys or your colleagues are interested in testing or registering to our platform to do some testing or mocking, please get in touch with us via our TDS inbox, that will be available in I think our last slide. All right.

 

So today's session, the other things we'll be covering is, in a little bit more detail is the upcoming API releases so, just quickly trade mark search. Obviously we're doing the demo. Our MVP versions of national phase entry applications, MVP of patent examination requests API, MVP of trademark new apps, and the trademark good and services API, which will be available soon-ish in the next few weeks, as I guess, a standalone API service as well as being a part of our new trademark application API. Then we'll get into I guess a bit of an update in terms of our delivery roadmap. We'll talk about how you guys can influence our current build. So, as you'll probably see from our next slide in the delivery roadmaps, basically we're working on a few different strains of API so that will be a combination of patents and trade mark services. And the MVP sort of things, which I'll get into a bit of detail on, will be, I guess a continuing pace of work into a completely, a service request API build. So it will be a minimal build at the start, and we'll be continually improving that as we go.

 

Then we'll talk about, again we'll have a quick poll about measuring our engagement with you guys. So we did that last time in terms of just asking a very high level question about how our engagement is going and how it's tracking. We wanna continue to improve our engagement with you guys. Then we'll talk about what's next from a reference group standpoint. I guess a rough date of when the next webinar will be, which will probably be August, early August. And then we'll do a bit of Q&A at the end of the day and unpack some of those questions, between probably myself and Casey.

 

Casey Martone, IP Australia

Yeah.

 

Josh Burns, IP Australia                       
So delivery roadmap that we've got up now for you guys. As you can probably see, the API foundation activities, a lot of internal technical work to enable some of those external APIs has been completed. We've now deployed patents, trade marks, and designs renewal APIs into production. So again, they're available via public test if you guys are interested. If you're not registered in the Mulesoft Any Point platform, please reach out to us and we can do that straight away. We've commenced our MVP or, I keep terming it MVP but it could be termed alpha prototype build, for national phase entry, trade mark new apps and patent exam request.

 

And as mentioned, we're close to externalising a goods and services API in test, that can be hit in an isolated fashion for next financial year, which is not far away. We're looking to commence the broader assignment/amendment suite in the patents and trade mark space. Exam responses, so that's gonna keep us fairly busy for the first part of the year but we'll also be still fleshing out the new trade marks API, the national phase entry API and the patent examination request API. So they're going to be continuing pieces of work as we get into new API instances. Another, I guess valuable API service that we're gonna be looking to start in the new fin year is what we've sort of terms unofficially as the notification API. This will essentially replace our current outbound correspondence service in the B2B space. So it'll allow people to switch off their MFT for B2B once it's fully delivered.

 

This notification API essentially will allow you guys to interact with us the way you want to. So whether that's through a structured format through Json XML or giving you the ability to pull down a PDF of correspondence that we're delivering to you for your clients. But we'll get into more detail about that in probably the next webinar, to get some requirements and some feedback from you guys about what you'd like to see in that space. So the last thing you guys will notice on the roadmap is that next financial year of 2021, we're gonna commence our designs and plan for just rise development. So our focus at the moment is on patents and trade mark services, and we will hit designs and PBR in that next financial year depending on how we're tracking.

 

 All right. API demonstrations. So I just, I've got a little bit of a lead in before Aidan sort of takes over here. But, I guess in terms of background for our smart trade mark search API, it's important to note that this reference group or this community regards significant interest initially about spinning up a version of trade mark search in an API style fashion. And I guess the importance of data verification was sort of he'd hoped was, at the reference groups, from a variety of you guys in this room. So, we spun up fairly quickly. It's in a public test space now. It's important to note also that you know it's not just gonna be trade marks. So we've got a redevelopment of our ADS platform occurring right now, which some of you might be involved in. Australian Design Search, sorry. Thank you Casey. I'm very acronym driven. So that, that's being redeveloped as we speak, which will enable us to then spin up an API version of, Australian Design Search in the near future. Now, we'll get back to you with some timing around that, but that will add to our delivery roadmap. Patents data. So AusPat isn't at the moment being redeveloped here internally. We are looking at that piece of work, but at the moment as it sits, we can't spin up an API easily, from AusPat. But there's some interim things that we're looking at from a technical standpoint that we might be able to do, in a lead up, in a lead up to a full redevelopment.

 

So, we're not closing the patents loop off. We hear that it's important from you guys and we're keen to find a solution in interim of spinning up an API. But that's something we'll talk to you guys about at the next webinar. In terms of smart trade mark search, the API in the public test at the moment enables users to retrieve the API rights data displayed on Australian trade mark search. The supported options currently are quick search, which returns the trade mark application or registration ID, and retrieval which returns the published data for a specific trade mark ID. We plan to improve and enhance functionality. So one of the examples that we've heard from you guys, in terms of a value standpoint is to have a trade mark update or the ability to search on updated trade marks. Which we're working on right now, so that should be something that we can release in the next few weeks. So we, again we will keep you up to date by the subscription list on when that might be available in test.

 

 What have I got next? Not too much other information before I hand over to Aidan. So again guys, we can have questions around the API demonstration for smart trade mark search, but we might leave it 'til Aidan's finished the demonstration. Then we'll unpack the questions as we go. So I'll hand over to Aidan now and he'll give you a demonstration about exactly what we've done in the trade mark search space. And at the end, when he's finished you can use your hand up, to ask any questions or flick any text questions through. Thanks Aidan

 

Aidan Whitehouse, IP Australia
Thank you. So, I'll first start off with Australian trade mark search. Awesome. Yeah. So I'll first start off with Australian trademark search. For any of you that have dealt with trade marks in Australia, you will have seen this website and you'll have most likely used it. So it's a very simple website, same as any search site. So if I search for Samsung I can get all of the results for Samsung. 
This initial page on this site is what has been transformed into an API. So, this box in the middle here, we've transformed into an API for machine to machine communication. So it'll help you integrate your systems and be able to get up to date trade mark data from IP Australia. So if I take a quick look over at our public portal, you can see we've got the IP right management B2B API and now we've also got the smart trade mark search API.

 

Once I go into that, it has a get on the IP identifier related to trademarks. This one is where you'll give a ID for a trade mark and you'll be able to get all of the relevant data that is publicly available on our Australian trade mark search website back in a nice, structured format. And so I will give a demo of that in a minute. The other option for this API currently is a quick search. So this replaces that or this is a machine to machine version of the search box on Australian trademark search. So you will give it details on what you wanna sort on, what type of filters you want and a basic query. And it'll give you back a list of trade mark IDs, that match that query. So if I jump over into postman, uh, which is one of our API testing tools that we use internally and is publicly available, I can hit the API which we've deployed to our public test environment. So you guys can use this  right now and start testing it and giving us feedback on what you guys would like. So the first thing that I'll do is I'll fire off a quick search against the API. So you can see here relating to the Any Point website, I'm hitting the quick search end point. And I've built a query around here so I'm sorting by number. I'm searching for any trade marks that are registered and are word marks and I'm searching for Samsung.

 

So if I send this request in, it quickly comes back with a list of, let's see, it comes back with a list of 412 trade mark IDs that match that search. So it comes back with a nice, structured list. These quick search doesn't give you the details of those trademarks. So this is only meant to be, to give you a rough estimate of how many or an exact estimate of how many trade marks match that search. And then you can go and find them individually at the search by ID to get the full list of details. That decision was made mostly because the amount of details that come back for each trade mark are very lengthy. So if I take this first trade mark that came back in this search and I pop over to the search by ID, and if I replace the existing ID that I've got there with the new ID, and hit search, once I send it in, it'll give me all of the details that are publicly available for this trade mark. So the renewal due date, the filing date, the owners, address for service and many, many more details.

 

So this result, this response here is an exact match for what you will get on Australian trade mark search, just built in a nice, structured form that machines can read, and developers will be used to using. So that initially wraps up the demonstration for this API. It's currently really simple to use. There's not too many end points on it. As Josh did hit on, we are looking at expanding the functionality. So one of the key bits of functionality that he was mentioning was searching by updated trade, searching by updates. So, if I was to search for, do this exact same search but, in the future use our refined search method, this count of 412 trademarks relating to Samsung that are registered, if I was searching for ones that now ma- or have been updated within this list in the last 10 days, it might drop down to say 20. And then you can use that to be more on top of when a trade mark has been updated and get more relevant details as you're going.

 

So you can automate that process on your side, and you can have the most up to date details about trade marks without having to continuously, manually do that.
 

Josh Burns, IP Australia
One other thing that, sorry Aidan for jumping in but-

 

Aidan Whitehouse, IP Australia
 All good.


Josh Burns, IP Australia                    

 ...the one thing that we probably should mention is our end performance. So this is something that this API is something that we've been, will be very popular with the IP profession, if not wider. Now we're wary about performance and the base tier at the moment that we've set in the public test space is 10 request per second. Now that may scale up. We're just sort of I guess monitoring the public test in the space that we've got and the performance that we're getting in that true quote I guess.

 

If we do change up, we will definitely be in contact and communication those base tiers. So, the entry point at the moment is 10 requests per second. So if you think this is too low, please let us know. Feedback would be great in terms of, depends on what size firm you are, what the use case is, that sort of thing.

 

But the feedback would be welcome, you know. We need some intel in terms of just pushing out the seams to our executive around, you know, where the work's going out performance wise, that sort of thing. So at the moment, 10 requests per second will be the base tier that we're starting with. Yeah.
 

Aidan Whitehouse, IP Australia       
Awesome.

 

Josh Burns, IP Australia 
Do we have any questions for Aidan while we've got him, about the demonstration? So you can either use your hand up.

 

Casey Martone, IP Australia
We do. So, Anna, I'm going to enable you to talk. So it will be a second. All right. Just got you there. Anna, you've got the floor. Anna? Let's see.

 

Josh Burns, IP Australia                      
We'll turn over and we can use the, the texts questions. So feel free to fire them through.

 

Casey Martone, IP Australia
 No, we can't see that. Okay, so that hasn't come up. Julie, would you like to ask a question? I'm just unmuting you now, Julie. Off you go. 
Julie? Can you hear us? And if you can, could you please talk?

 

Julie
I can hear you, but I didn't have a question.

 

Josh Burns, IP Australia  
Okay. All right, you didn't have a question?

 

Casey Martone, IP Australia
Oh sorry.

 

Josh Burns, IP Australia
We could hear you though which is good.

 

Casey Martone, IP Australia

And we could see that your hand was raised, so we apologise, Julie.

Josh Burns, IP Australia
Do we have any other, I guess general or technical questions around, the smart trade mark search API demonstration for Aidan?

 

Casey Martone, IP Australia
All right, we've got a couple come through
 via text. Let me read them out. How do we get access to the Mulesoft Any Point platform? Would you mind helping that one out?
 

Josh Burns, IP Australia
So, that's through our TDS inbox, guys. So again, the the address will be listed on our, I think it's our last slide so I'll reiterate that at that point. But it's
MDB-TDS@ipaustralia.gov.au. Again, apologies for the acronyms. 
What can happen is if you email that, with a request to access to Mulesoft, I can register, register you straight away and I'll flick you back your credentials and the important details that you'll need to access your account. That way once you register, you then have access to all of our technical docos, to our specs. You have access to our mocking services for the API instances we've published in test, and you can start, you know, testing against our public test or UAT environment here internally. So, all of those avenues are open, but please get in contact with us.

 

Casey Martone, IP Australia
Excellent, thanks Josh. So the next question we've got is from Dan. So, the question is around records return size limit for the search.

 

 Josh Burns, IP Australia
So my guess with that question would be around the quick search. Currently it does, limit it to 10,000 but it's a page-able result. So you'll be able to see all the results. You'll just have to page through them. So in one return page you'll I think be able to max out a 10,000. But you will be able to get all of them.

 

Casey Martone, IP Australia
Could I ask whether in the quick search we could have a combination of classes and registration number of the chosen trade mark?

 

 Josh Burns, IP Australia

That if there's interest in that, we can definitely look into that. I don't think it's been flagged internally at the moment.
 

Aidan Whitehouse, IP Australia
That's something we can document from 
this webinar and actually spin it up into another possible use case.

 

Josh Burns, IP Australia
Yeah. We, I can definitely see a use for it so we can definitely flag that and get thinking about that.

 

Aidan Whitehouse, IP Australia
So we'll, so in answer to that question we'll raise a item, from this webinar, with our technical team, and our vendors importantly about some, the possibility of including that functionality and we'll get back to you.

 

Casey Martone, IP Australia
Okay. Uh, the next question we have is, can this be used as a live data now?

 

Aidan Whitehouse, IP Australia
So, I should have mentioned earlier the existing API in our test environment should not be used for production systems. It's completely test data so there may be issues with it. Some of the data will be different to what you're experiencing in production. So don't use it for production data. 
However you can hit the API now and use it for testing. So live data that you're showing customers and using to make decisions, definitely not. But using it extensively to test your solutions and develop around, absolutely.

 

Josh Burns, IP Australia
Yeah, so reiterating that, you know, the data itself in our public test environment is not production. So it's not for commercial use, but it will give you good look and feel for how it's gonna work in, in a test environment for production. 
Now, the other thing I will mention there is the, the environment is driven, so it's published every 24 hours in the Australian trade mark search system. So it's not real time at this point. So the data that you're hitting, Aidan, in test is updated every 24 hours. So that's just a, another thing to, another, important note I guess. That could change in future but we'll leave that to the future.

 

Casey Martone, IP Australia
So one of the other questions we've got is any plans for the API matching advance search on the, web trade mark database or at least some criteria from this screen like status or owner?

 

Aidan Whitehouse, IP Australia
So in the future, I believe we are looking at advanced search. If there are key fields from advanced search that you would like speed tracked and brought into the quick search or, uh, built out, that you would find immense value in, and we've got multiple customers finding value in them, flag them and we can definitely look at them. Advanced search is, as it suggests, very advanced. So there's a lot to it.

 

So it would take quite a bit of effort from our end to fully-

 

Josh Burns, IP Australia
To support the whole.

 

Aidan Whitehouse, IP Australia
Yeah, to support the whole lot of it. But if there are key things that all of you are looking at, we can definitely prioritise and start developing around it.

 

Josh Burns, IP Australia
Yeah. So again, I'd say in that context, get in touch with us. We're always happy to do workshops individually, with our developers and we can unpack some of these, I guess some value points and actually prioritise the use cases. So we can actually deliver some value, early than trying to, like Aidan said, support a fairly complex sort of parameters in it.

 

Aidan Whitehouse, IP Australia
So yeah. We want the API to work for you guys. We don't want it to take ages to develop something that you guys aren't gonna use. 
So any feedback that you guys have, send us through and we'll prioritise based on the feedback that we have and we'll develop against that.

 

Casey Martone, IP Australia
Yeah. So we do have a question of when will this recording be available after the session and I can guarantee you that you will receive an email after this with a copy of everything that you've engaged with, throughout the session, which will include slides as well, and a short survey which obviously we use as a mechanism to understand your interaction with the project and your engagement level with the project. And it's your opportunity to give us feedback and make sure that we're on the right path that serves the most value to yourself and your organisation.

 

Right, yeah. There's just one. Let me just have a look. So, back to questions guys. If fetching details of every record from a list of results involves a separate API call, 10 calls per second would mean it would take 40 plus seconds to get all the resorts, results from the example that you provided with Samsung. Is that accurate?

 

Aidan Whitehouse, IP Australia

So the API itself is not meant to be a replacement for bulk data. That's one of the key things that we've gotta think of. So it's not meant to be able to search all two million trade marks and get all of the details from them and load them through. If you were to use it for that, there would be a performance hit of having to meet our SLAs and you would be making that conscious decision. There are also terms and conditions around the API, that, will most likely hit on that sorta thing. For the performance of the API, we are trying to focus on having that as streamlined as possible and have the API as quick as possible.

 

Having the results come back for the APIs in, or for each of the trademarks in the quick search, it was determined it was just gonna be too much of a response in one pay load, which is why we separated that out. So, at the moment you'll be able to get the, you'll be able to get the information that you want and you'll be able to get it quickly, if you're not using it for something like bulk data.

 

Casey Martone, IP Australia
I just have one more question. Obviously we've had a really good mix of both business and developers and techos in this webinar. 
We do have a few couple of questions coming about what is an API and I suppose, do you wanna give some context as to why we're going down this path? Just for anyone who might be new.
 

Aidan Whitehouse, IP Australia
Absolutely. So an API is an application programming interface. Essentially it's the new trend within the IT industry about how to develop solutions that work for customers, are quick, and the solutions are smaller so it makes overhead for developing and integrating with a lot less. So, the reason we've decided to go down this way, is so that we can develop quicker, we can develop smaller solutions.

 

Josh Burns, IP Australia
With value.

 

Aidan Whitehouse, IP Australia
And, yeah with value. We don't have to develop whole monolithic solution and ship it all in one hit to, which then has 90% functionality that you don't need when the 10% functionality that you wanted is, would've been easy to develop. We could've done that in a month or two months and got that out to you. Instead, old world, we would've taken a year to get something out to you. 
An API, specifically, is essentially just a small program that instead of having to install something and have something on the front end that you're going in and having a UI for, it's defined for machine to machine communication. So, there will be a URL that a machine will call and format a request to and send that in that way.

 

So, as a user, you won't necessarily be interacting with an API directly. You won't be writing your requests directly to it. There'll usually be a website or an application that's on the front of it.
 

Josh Burns, IP Australia
It's almost like the underlying engine 
that powers it. One important thing that, that we should note is, and Aidan's touched on it, it's a model solution but most software developers are really clued in with. The barrier is much lower for integration. So at the moment, our B2B platform, it's very complex. We use a proprietary software, a file transfer system. We haven't got a lot of control over the updates and enhancements to that software. It's a difficult place, uh, for us and the consumer.

 

Casey Martone, IP Australia
So one thing I suppose we would encourage, probably our business side of our reference group is that if you are looking at this project and you are seeing a long-term value for yourself or your firm, potentially looking to engage with someone from the software developer industry. Josh, what are the two industry associations that people could I suppose start there, they could kinda search for?

 

Josh Burns, IP Australia

Yeah. So, the two, I guess firms that we've gone down so far, was the Australian Computer Society, that has some links into who you could contact in the software develop- development community space for a bit of assistance on integrating with APIs and I guess delivering value for your business using this technology. The other one is ABSIA. I'm just trying to think of what the acronym is. They're, they're essentially a community of software developers that can sort of point you in the right direction.

 

But if you guys have any questions about how to contact the right people in the software development community, please come through us again, and we can point you in the right direction. You know, many of you guys in the, the larger firms will have on site developer skills, which is great. So if you guys have interest from a business perspective in this APIs, they will be more than capable of helping you understand how to integrate and build towards onboarding onto, using this API foundation essentially.

 

So I guess one thing that should be said is this API foundation that we're building, we've said this before, is not only to replace the, the current B2B solution, at the end of the day we will be delivering or developing a web UI that sits on top of these APIs. Now, that's again very early days for our planning. We're focused on the B2B suite at the moment. But there will be a user interface or several, that hook into our foundation APIs.

 

Casey Martone, IP Australia
And at the moment, many of, you would probably know that current, uh, way that we do that transaction activity through, uh, eServices. All right.

 

Josh Burns, IP Australia
It's not a great experience.

 

Casey Martone, IP Australia
No.

 

Josh Burns, IP Australia
Thanks Aidan. We appreciate it.

 

Casey Martone, IP Australia
Right. So, we've got obviously a little bit of a quick poll coming up now. As I mentioned before, one of the things that is really crucial for us to understand is, you know, are you guys happy with the way we're engaging with you? If so, great. If not, tell us why so we can actually up the ante and change the way that we do this. 
So I'm just going to launch that little poll there on the screen. I would be really appreciative if you could all just take just a moment to pop that in and we will continue. Josh has got a few more slides to present and then we'll close out today's session.

 

Okay, just a few more. Fabulous, all right. Thank you everyone. I can close that poll out now.
 

Josh Burns, IP Australia

 Thank you guys. So, just quickly I, I've got about three slides left. But I'll, I'll sort of get through them fairly quickly and we can sort of unpack some questions at the end. So upcoming API releases. So this is, I guess the slide that I wanted to talk to you guys about, the MVP or alpha prototype approach that we're taking. So as Aidan sort of said in the, in the trade mark search, instance where, you know, building and supporting a functionality for, something like advanced search is fairly difficult. The same could be said of something like a new trade mark application.

 

So what we're doing is, is I guess building in small chunks and trying to prioritise which features that you guys wanna see in our subsequent sprint build as we go. So, at the moment our focus is to release national phase entry for patent applications, new trade mark application API, patent examination request API, with an additional postponement of acceptance request, in the next few weeks.

 

So that will go to, that will be published in our Any Point platform, to a public test space. Now what I need to be clear about is the scope of each of these APIs in its initial version. So, national phase entry will only support valid national phase entry applications without attachment. So no English translations are able to be attached. No radical 1934 amendments. No early entry national phase entry applications and no additional requests on top of that national phase entry application IA exam requests or anything like that.

 

For patent examination request, we're only supporting full standard application exam requests. So that's for standard patents only, and full examinational requests only. We're not supporting attachments. So any supporting documentation. We're not supporting amendments, we're not supporting the global patent prosecution highway, additional requests or anything like that. It's very vanilla. That will be the initial scope and we'll build upon that.

 

For new trade mark applications, we're only supporting word and plain text marks initially. But you'll still have the ability to select goods and services from a pick list or construct your own, customised list of good and service. So, that will not include different trade mark coins or tops. Additional sprints that we're working on at the moment will include uploading attachments like images for a logo. We'll look at offering series and priority claims within that new trade mark application as we go.

 

So our sprint schedules at the moment are three weeks long, and we're trying to deliver as much value in those sprint schedules as possible. Now we understand that people will wanna see us support more before they start testing or going to production. But we're happy to work with you guys individually about what your MVP may be to go to production, so we can prioritise again what our next enhancements or features are.

 

So just to finish off in, in terms of those upcoming releases, our trade mark goods and services API. So this will be an instance that can be called upon in isolation, from the new trade mark application API. So this might be something that attorney financial professionals use to update the goods and services classification, that sorta stuff, in a simple way.

 

It could be for third party developers who want to create their own, new filing web UI and/or they've got an existing new filing web UI and they wanna call a goods and services API to help selection of those goods and services for a user. So that's something that's gonna be externalised very soon and it's something that could provide value in a variety of different ways.

 
So in terms of feedback and, and I guess this is the important part of all of these builds, we want you guys telling us what we should be building next. So if you do wanna have more influence, please contact us via our email address listed on the current slide, and we can, we can arrange workshops with our developers. We can prioritise, what is valuable for you guys, at the end of the day and we can start weaving those into our sprint schedules.

 

Casey Martone, IP Australia

And it's Josh who obviously manages that inbox, so you'll be talking with Josh directly.
 

Josh Burns, IP Australia
So next slide. So what's next? Importantly, as I said at the start of this webinar, the next webinar will be probably in August. At this time I haven't got a date, solidified at this point but we'll send out, an invitation fairly soon. As you can see, I've taken that the team are, are very busy working on a number of different streams, in the API space. So everything we've talked about today in the transactional space and even the searches space will be happening in the lead up to our next webinar.


So again, if you're interested in, in having some influence and being involved or being registered to the Mulesoft platform with us, please get in touch with me. We can do that straight away and in a very quick fashion, and we can have technical resources at our end ready to talk to your developers or give you a hand in, I guess locating, sufficient developers in the community that can help you. One other thing I do wanna touch on is, we'll be in touch via email in the next few couple of days I guess, in terms of our decommissioning approach in the B2B space. There's no panic here. There's support on going in the B2B channel currently. It's more specifically around what we offer in TDS and, and what sort of timeframe we're looking at, going down for decommissioning.

 

So, you guys on the subscription list or any existing customers will see some communication from us in that respect. That, it's mainly I guess the target again is existing B2B customers who are transacting with us via B2B right now, who it really impacts. We've got, on the slide here there's a couple of resources that are definitely handy points of information. So obviously, our email inbox that we shine up quite a few times. That's an important address for you guys to, to bookmark.

 

But we've got a couple of webpages that provide some information about our digital transformation at a wholistic level. They give you guys details about the webinars that are recorded. It also gives you understanding, I guess where we're going in a wholistic sense, in terms of digital transformation. So not just the API journey. We're looking at data journeys. We're looking at other valuable inputs that we might have going forward.

 

So, there's contact points in there. There's processes, so if you do want registration to, to Mulesoft, there's links there, enquiry forms that go straight to our inbox. So, please get in touch with us and we can help you out straight away. We might, what time is it? We've gone 40 minutes, so let's open the floor for some questions at I guess a program level. And we, we might go for another five minutes, Casey and then we'll-
 

Casey Martone, IP Australia
Yeah. Then we'll close it out.

 

Cool. So one of the questions we've got here is kind of what is the thinking around the system emailing PDF copies of the documents, we were streaming like the exam report-
 

Josh Burns, IP Australia
Yeah.

 

Casey Martone, IP Australia              
...to the end user rather than an email just saying to log into the eServices account to collect that information?

 

Josh Burns, IP Australia
Yeah, that's a really good question. Again, what we're calling loosely the notification API, the path we want to go down in that space is for you guys to tell us the way you want to interact with us. So if that is sending an email of an exam response or exam report, correspondence item, that's the way we want to go down. So there's a fair bit of work to do at our end in terms of allowing that path to happen. But we want it to be more interactive.

 

We wanna give you guys the ability to pull down a PDF and not have to log into a web interface to access that correspondence. We wanna give you guys the ability to pull an API to check for new correspondence that's been delivered throughout the day here at IP Australia. So once something's been processed in our systems and completed, if that correspondence is available, we want you guys to have the ability to search for it for any updates and pull that correspondence down in, in the format that you want. So that could be structured, that could be JSON, that you guys have been automatically classify at your end.

 

It could be a PDF version. We want you guys to draw off that interaction. So we wanna be flexible with how we do that. So that, again, speaks to that notification API that we're keen to start building in the next financial year.
 

Casey Martone, IP Australia  

Yep. So that's all of the questions that we've got come up, Josh. Thank you for hosting today's webinar. Thank you for, everyone, for attending. We hope that you found this valuable and as Josh has said many times, you are more than welcome to connect with us via our email address. And Josh will get back to you. He will do his best. He always gets back to people. He's very responsive.


So thank you again. A recording of these slides and a short survey will be available at the end and we will be in touch via our email group to alert you to the next webinar. Thanks again guys.
 

Josh Burns, IP Australia
Thank you guys.

 

Casey Martone, IP Australia  
Have a lovely afternoon. Bye bye.