Last updated: 
22 October 2019

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

Josh, IP Australia                      

Hi guys. Thank you for coming along to our, I think it's our fourth TDS Reference Group Webinar. This is obviously our October version. We've got a bit of a smaller crowd today. I roughly about 10 attendees in today. Again, it's great to have you guys along. We've got a few things on the agenda today, a few demonstrations which will be of value hopefully, and some strategy pieces around providing some assistance to the small and medium firms in identifying and approaching the marketplace for a software vendor to help with integration.

Just while I've got you guys here, I'll just go through some housekeeping before we get to the agenda. So again, you guys have probably been in previous sessions and a little bit bold with this and know all this. But I'll just go through it for any new participants. Again, we're using GoToWebinar for today's session as mentioned in previous sessions.

Any questions, it's probably best left to our Q&A the end. However, for our demonstrations, once we get through the demos, we can sort of have any specific questions about those at that point. The webinar today should probably run for a roundabout 30 minutes. It's fairly quick today. We don't want to sort of burden you and waste your time. If you guys can't hear me or us throughout, please let us know. Today's webinar will be recorded as per usual. It's available on our website. But we'll also send an email out at the conclusion of today's event probably tomorrow, I dare say with the details.

All right, so on our agenda. Oh. Where are you on there? So last webinar, it was some time ago. It was in August roughly about eight weeks ago. So today, we want to focus on some demonstration. So again for you guys that were involved in the last webinar session in August, you remember our test lead, Cam.

He's running through a technical demonstration of trademark new application API. Now, for those that were involved in the last session, we did do a demonstration on trademark new application API. However it was limited and didn't actually have the customer creation component. So today, we want to sort of take you through that now that we've implemented at our customer and identity solution platform. Cam's also going to demonstrate time mark exam responses with amendments involved as one of KSAs in the trademark life cycle.

We'll also demonstrate trademark change agent. So we'll take you through a few value add demonstrations. After that, I'll run through a general program update, and take us through the delivery roadmap. So there's been some small changes there as we've mentioned before. It's dynamic. It's based on your feedback. So I'll take you through that. I'll take you through what's available in prod at the moment in the API space, what's in test, and what's underr current development and what's I guess set down for the future. So we've got a bit of an update around those things for you.

We were meant to have Claire who is our comms lead, talk about the guide to approaching software developers for small to medium firms. Claire's, unfortunately not in today. But Matt and I will run through that brief session. We'll touch on a few things that we've got planned in the scope of work for you guys. So we'd love some feedback on that. So when we get to that, we'll take you through the information. Again, we want to measure how engagement, how we're tracking with our engagement externally. So we'll have a very brief poll again, just so we're measuring that continually. We'll talk about what's next from a reference group perspective. We'll probably have one more this year in early December to wrap up the year. We'll obviously have based on the delivery road map, have a local deployment throughout at that time. So there'll be plenty to get through it at that session as well.

At the end, we'll do some Q&A. So that will be the time where people can ask questions about the program generally. All right. So as mentioned, we'll get into the API demonstration. So I'll just hand it over to Cam. Just while I'm handing over, I'll just speak. Give you a little intro. So again, Cam's our test lead. He's one of our technical gurus as part of that development team. So I mentioned cam took us through the trademark new application demo last time. Without that that critical component of applicant or customer creation. So Cam will show us through that stage as well as the attachment API and the fact that this instance of the API is actually in public tests right now. So it's active. We're expecting to deploy it to prod it in probably the next two to four weeks. Hopefully, sooner than than that.

So we'll keep you posted on when that is going to go to production. But in the meantime we'd love for you guys to get in there, and test it, and give us some feedback about how we've gone. I'll hand it over to Cam now. He can sort of take us through the demonstration. As I said, let's leave any questions that you guys have and until Cam's finished the demos. So up to, Cam, do you want to just do them based on each demo?


Cameron, IP Australia


Yeah. So either or, so if you've got a question kind of while I'm going through, yeah. The demo kind of go through the whole flow, the trademark in your application, then examination and responses amended addressed for service. So yeah, I guess feel free to chuck a question. I'll try and get to it either during the demo, if it would make sense or at the end there. So you guys probably, some of you who were on the last demo or the last webinar, I did all that on the trademark new apps.

As Josh said, we were missing the key component, which is probably you know, customer of applicants and agents. But we've now finished with our customer management solution for TDS. This is pretty much ready to go for testing. So first of all, I'll probably just start with just the basic trademark new app just to get everyone back across that in case there was any people who weren't here. So again, if you haven't seen this before, a tool I'm using is just called Postman.

It's just an API based testing tool. Obviously there's no UI for the TDS components. So the first thing I'll be doing is attaching a trademark representation using the attachment API. So here, you can see, I'm simply sending a JPEG image, which would be the trademark representation. If that's a sound file or whatever it may be, obviously the file would look a little different. We accept all of the variations of trademarks that you can currently do in production through TDS. So yeah, I'll send in a new transaction for the attachment there. So as you can see, it's responded. It's happy that I've sent the attachment into IPA. I've been given an attachment ID. This is probably the key four documents and attachments that you're sending through TDS. You return the key for that attachment. Then you would essentially paste that into your trademark new application payload.

So here, I've flicked across to a trademark's new application payload. As you can see, I've got things like goods and services in here, which you can have multiple of. I'm saying it's not a pick list trademark, it's a figurative mark. So an image you've got the usual things for a trademark new app. I'm passing that representation ID into the payload here. So that image I uploaded will be passed through to this endpoint here. Then I can post the trademark new application to IP Australia.

I'll send that now and hopefully, you'll see a response. Then I'll circle back to the new customer component, which is probably what everyone wants to see most. So as you can see, below and their response pay load, you've got your trademark new o application number. You've got your batch identifier there and whatever costs were associated with that type of mark. That obviously changes and fluctuates depending on if you've got a different goods and services or it's a series mark or something like that. But as I said before, we are supporting pretty much all of trademark new app now via Head Starts. But Josh can touch on that because that should be pretty much in the pipeline.

Just give me a second while like just try and jump onto the questions page. Just bear with me for a second. Awesome. Cool. So sorry about that. Just getting back to the demo. I will quickly jump through the customer stuff. So this is probably brand new for everyone. This is what we're calling essentially the customer API and our customer management platform, the TDS. It consists with essentially your own address book, that is an address book just for you or your clients. So for example, if I was a person submitting marks, I would be creating customers for my customers and then passing those through to IP Australia in the relevant pay load. So here, you've got the the end point for posting a customer to IP Australia. As you see here in the payload, it's obviously set up for an individual, which is myself, my details, my address, phone number and whatnot, this kind of stuff is all defined in the RAMIL for what's optional and what's mandatory in these fields.

But once you've covered the basics there, it's as simple as just posting that message to us. Again, you will be prompted in a very similar way to how the attachment API works. We'll respond with the details that you posted and provide you a customer ID, which is this identifier here. That is your unique key for that customer you've created. You can use that ID multiple times across as many SRs as you like. That's kind of the key you pass into your service request payload if that's for an amendment or a trademark or whatever it may be.


Josh, IP Australia

So one thing, sorry to jump in, Cam. One thing we'd like to do here guys is to encourage reuse of IDs. We are aware of duplicate data coming into our IP Australia. We certainly know our customer data traditionally has been a bit of a mess, but we want to put a line in the sand and start offering at customers the ability to reuse customer IDs where applicable. So that's something that we've been working on in this customer management solution. Sorry, Cam.


Cameron, IP Australia

You're all right. Yeah, that's pretty important to note there Josh has made. Obviously for your own ends record keeping, it's probably going to be better as well , if you're maintaining a unique key, which is probably really the driver for how this would work in a sense for our customers. While we're chatting on that, I'll quickly just jump into the get which might help people understand how this functionality would work.

Here I've got the end point for get, which is essentially asking, "Can I get all of my customers that I've created in the address book there?" So that customer I've just created would be in this list here. It's probably going to be a massive list because this is my test account. So just ignore the fact that that won't go on forever. But we also provide other search options. For example, searching by ID and by name against your ... What's important is it's your address book. So it's not an open public address book for anyone else to see. It's just customer-centric. So I will only ever see my customers that I've created and no one else would see those.


Josh, IP Australia

So just to touch on that, so what Cam is saying is spot on. In test, we don't have the searchability switched on. We're just getting some internal approval sorted over that stuff, you should see in the next few weeks.


Cameron, IP Australia

Yep. So yeah, so you can search, you can and what is switched on is getting your own contacts. That's fine. The searching functionality of searching your own contacts by name. That's not currently there. But yeah, we're looking at fixing that up soon.


Josh, IP Australia

But the critical part is you can create an applicant.


Cameron, IP Australia

Yep. And service, you can serve a service request there with those customers, which is probably the main thing.


Josh, IP Australia

One other thing to touch on. Sorry, Cam, I'm jumping a lot.


Cameron, IP Australia

Yeah, it's all good.


Josh, IP Australia

For the less technical audience here, it seems like there's quite a few steps here for a new application. Now they're basically micro services in the API space. So this is something that when integrated with your case management system, it's seamless right? So it's about how you build that engine underneath for your own UI, if that makes sense. So again, when we talk about the guide that we do a little later on today, I'll talk in a bit more detail about that and our plan to rebuild a web platform that would make more sense to business-focused people. But I just wanted to sort of catch people here and with the fact that our approach is a micro service based approach for API. So it's a bunch of components that we're speaking to for one submission.


Cameron, IP Australia

Yeah. So that's important to note as it looks like I'm probably clicking through about a hundred different things. In reality, it's just one thing that would happen from your end.


Josh, IP Australia

Importantly, you've got the flexibility of how to actually build that into your system.


Cameron, IP Australia

Yeah. So how this looks on your end is entirely up to you. Unfortunately, I'm constrained by not having my own case management system. So I have to use Postman and that's kind of the way the demo looks a little bit disjointed sometimes. But just getting back to the trademark and your application here, I've got the owner's bag here or array ... Sorry, I use the XML language. But I've got the array here for owners and it's asking for the identifier. That is the identifier that I just created for that customer. Here, you'll see the agent identifier. That would be your own identifier. If you leave that out of the payload, it will just default to you. There is obviously circumstances where you might be submitting something as the submitter of the transaction, but you may not want to act as the agent.

That's probably an edge case, but we do cater for that in any case. So as you can see, I've pasted it in my customer ID of the applicant that I would like to apply for this mark. Then I simply post that to IP Australia, which is ... I showed the exact same thing I showed before. It's probably not going to like it because I've reused the document that I used before which is a one use thing. But I can simply generate another one and I'll pass that back through for a success message there locally.

Cool. So I've got the into one response there. It's got the same details as before, the fee and the new application ID for the trademark I've just generated or the trademark request I've just generated. I'll just see if there's any questions on the new app stuff before I jump into ... No, we should be all good. Before I jumped into the next phase of the demo, which is around a trademark exam response and also trademarks address for service changes for changing the address for service to a new agent or for yourself essentially. This is also delivered for patents, but we'll just demo the trademark stuff today.

So I'll just jump across to my exam response first. Then we'll go through the address for service change, which they're both very simple requests. You'll see the end point here, which is the mark that you are trying to provide an exact response for and also the examination response endpoint. This is the simplest pilot example I've kind got to show. I thought I'd just use this one as an example, but we obviously support exam responses with address for, sorry, with changes to the customer, changes to the representative and any other changes to the goods and services or the kind of



Cameron, IP Australia

Or the reps or the biblio of the mark. So whilst this is just a simple free text response as you might've seen, if you guys, any of you guys use e-services currently, it's the same as that. You can simply put a free text response here or you can provide a file or a new representation or whatever is required for your exams or your particular exam response. Again, using Postman, there's not too much exciting to say.

It's just simply posting that response to IP Australia. As you can see, it's not coming back because I've already provided this response for this trademark. So if I change the free text to something else, it will pass that validation. I will be able to essentially have my response sent into IPA, and which would go then obviously to the trademark examination and down that path. So yeah, it's not too much exciting I guess in terms of looking at for this one. But it is a pretty common SR, it's high volume request.

It is a good value to most of our customers. It's a little bit slow today but there we go. So test has come back. Now, I've submitted my exam response. I've got my ID. It's just confirming us for that trademark and there's no fee payable obviously for this one.

That pretty much just brings me onto the last thing I'll have to show which is a changing of address for service to the submitter. Now just to bear in mind at the moment. The only thing we support in trying to adjust for service currently is to change the address for service for a mark to you. So we don't currently support right at this second I'm changing it to someone else, but we envisage that they should cover most of the use case of this SR and most people are just changing the mark to themselves so they can action a request a response.


Josh, IP Australia

But we really expand on it.


Cameron, IP Australia

Yeah. We will be delivering in the future just spread. So it's just not there currently, just as a note really. Again, I've just got my endpoint up here. This is probably something new which we haven't touched on previously is the patch request.

We're kind of using the standard API patents, sorry to be a little bit technical for the guys who maybe aren't across this stuff. Patch essentially just means a request to update or change as opposed to a post which is doing something new or a get, which is retrieving something. So we're doing a patch on the trademarks rolls endpoint. This is trademark OR key number one, which is a real trademark. I always use it when I'm testing because it's easy to remember, but you just simply post the request to that.

What's going to happen here is that it's going to be annoyed that I've already done this one this morning hopefully, this is a real mark and I'll ... Hold on two seconds while I grab another mark. Yeah. So what will essentially happen there is we will be just using your customer ID. So that is the person who is submitting the request to change the representative role to them. So that's why you're not seeing any details there about passing in any customer IDs. That's just a simply do you want to change the request, the representative? Yes. Then the request is sent through. So you'll see there. Again it's just the same response pattern, which is the batch ID, the trademark you've actioned, and if there was any fee payable. That kind of wraps up the kind of technical demo. But yeah. Just make sure there's no further questions.

But if there are any questions later, we don't have any currently. If you've got any questions, definitely feel free to either send them after the webinar or send them through to Josh or any of the kind of comps points you've got and we'll be happy to answer those technical questions.


Josh, IP Australia

We can also, I'm just wondering about Cam here. Cam's part of our development team obviously. Development team are always on hand for video conferences where we can do direct engagement around this stuff. So if you are developers, software developer resources are keen to sit down with members of our team and talk through some of the responses and how to call the APIs. We can certainly arrange those things. Again, like Cam said, touch base with us through our tedious inbox. We've got that address at the end of the slide back today or contact myself directly. We can arrange that sort of stuff. So thanks again, Cam.


Cameron, IP Australia

No worries.


Josh, IP Australia

Appreciate your time. All right, so next guys, we'll do a bit of a program update with a delivery roadmap update. So as I mentioned, it had slightly changed based on customer feedback around some of the priorities in terms of the SRs that we're covering. So I'll just cover a couple of things but I mean you should be able to see our new roadmap now which is on screen. So again it's quite busy. It covers a lot of different things including our proposed web build. But I'll just take you through some of the information here.

So what we've got currently active in production in terms of API instances are IP right renewals across the board. We've got patent exam requests, we've got a national phase entry for patents available. We've got requests for postponement of acceptance of patents available. We've got trademark exam response, API available. As cam just took us through, trademark and patent change agents to the submitter.

We've got trademark goods and services API as an isolated and API that's available. We've also got our Australian trademark search API which has been very popular. In terms of current development, we're sort of building up the remaining functionality for trademark. So that will include trademark headstart as Cam mentioned before. So we're right in the thick of the build at the moment for trademark headstart. That should be ready probably by the end of this sprint which is the end of next week. So again we're aiming on deploying that to test probably the next Friday or if not the following week. So that's something again that we see value in. We know a lot of the large, medium and small returning you can actually utilize trademark headstart in each services. It's not currently an offering in our legacy B2B platform.

So we say there's a value add for you guys to integrate with the other edge case that people may look at, trademark headstart and trademarking application API for is if you want to spin up your own UI for the general public in a more sort of automated hands off way of filing, which is already been achieved through some strategic firms. In terms of other development. We've got people with graphic amendments happening for patents and trademark, business lines. One of the big ones that we wanted to unveil probably next week is design search API. So we've been working on an IPO for ads as some of you may know as for a couple of weeks or a couple of sprints now. So we should be in a space to deliver that probably mid next week towards the end of next week in tests.

There'll be information in the Any Point MuleSoft Platform for people once that's deployed. So again, it'd be great for people to start testing this stuff and giving us feedback about it. Outside of that, in terms of the search system API space, we're going to get onto AusPat or Patents Search IPO in the not too distant future, probably in the next sprint or two. We're working with our vendor on that one as we speak. So there is planning on having, there is a plan I guess on having all of the major IP rights covered in the search API space within the next sort of I guess six to eight weeks.

In terms of soon to commence development, we're just starting the planning phase for a new correspondence API, which will be a Kate pace for existing B2B users but also potential integrators in this space. So the stage one of that will essentially be Jeff changing their delivery mechanism from proprietary Tipco MFT Software, the MFT transfer to an API channel. So the content of the PDFs won't change straight away. That's something that we'll work on in the future and hopefully, in the future we'll be out there, provide you with more structured responses as well.

But essentially, I guess the aim of the new correspondence IPR will be to in future, allow the customers to draw off the why they want to interact with us. So we want to be flexible about how you guys want to interact with our office. But we can talk, probably talk to that a little bit more. We probably have a showcase at the next webinar or on correspondence. But if anyone is interested in it prior to that in December a please reach out to us. That sort of brings us to so ... So we'll cover off the assignments and the amendments space for trademarks and patents.

We'll be looking at extensions of time in the next couple of sprints as well across patents and trademarks. We're then looking at a start on how designs are built. That's come up a little bit earlier. So we're a little bit ahead of where we thought we would be. So we're starting some discovery work on designs. Our agency's just gone through a design review project, which we're working closely with on some of the findings that they've sort of had with the design stakeholders. So whether that be attorney firms, sell filers, or the designs industry so we're taking all that relevant information that will account with without API build. You'll see on the delivery roadmap that we've got a web build, proposed web build in there as well. So we're at the stage at the moment of procuring a service design vendor to help us with some of the planning on what that actually looks like.

At the moment, we haven't got a affected or approved plan of what that web platform actually looks like. So obviously, part of the objective of this program was to really encourage other innovators outside of just us to look at building UIs for the general public, innovative type UIs that we're not necessarily known for. So that piece of work is just sort of ramping up at the moment and we'll keep you posted at the next webinar on where we're progressing with that.

All right. So just moving onto the next topic. So this is what I spoke about I guess at the agenda of today's session. So there was a question in the last webinar, and I'm not sure if the participant is here, but there was a question from small to medium or boutique attorney firm around whether or not IP Australia would be offering an integrated package for the smaller firms or the medium-sized firms who don't have developer support basically to integrate it for them, which is not something we can actually do technically.

But what we can do is provide you I guess a resource or a guide to provide you the information in terms of the skills that you need, the communities in terms of the market to approach. So identifying that market and how to reach out to these guys. So our comms team has sort of taken the lead on this strategy. We're going to develop a bit of a guide for those small to medium or boutique firms about how they should approach those skilled resources.

So we'd love your feedback on that. We're aware that the large firms do have the, do we have the benefit of onsite developers in the technical space, but we've taken the feedback onboard and we want to help. We want to help those guys that don't necessarily have those skills to identify them and give you the confidence or assurance I guess to go out and approach the market for the skills you might need. So the plan on that is to sort of get something out to you guys probably via email before our next webinar. We can sort of gather some feedback via our subscription list and give you a look at some of the drafts that we build.

All right, so the next topic is our poll. So I'll just hand it over to Matt who will run our poll. Again, we do this every webinar just to measure how our engagement is going. We want to make sure that we're doing it regularly enough that satisfies you guys. Like I said, I think I mentioned it when Cam did his demo, this is not the only engagement we do. So if you reach out to us, if you're interested in registering for the platform, the API platform please reach out. We can actually get in direct contact with you and your technical or business focused stakeholders and talk you through I guess defining the opportunity first of all and talk you through how do to integrate technically. So that's something that is always available, and we'll put up the inbox address at the end of today's session. So I'll just give you a minute to fill out that poll and we'll continue on.

Very good.

All right. Thank you very much. We'll just move onto the next slide. So what's next? So as I said, the next webinar is slated for December. We'll get you an exact date when we send out the conclusion. We'll wrap up an email of this session probably tomorrow ifq that comes to us. But what's next? I guess I've taken you through what's next in terms of the technical build and what we're doing in the strategy space for a guide for the small to medium firms. We've got detailed information about our program on our website.

So there's some links up on the current slide now that could be handy. The email address for our contact point for our program team is listed. Like I said, if you guys need anything, if you want us to speak to your executive or your partners about the value opportunity that the APIs bring, we'd be happy to get in front of those decision-makers. But also get in front of the technical resources in terms of assisting you guys with the build and the integration or open to a policy here. So please get in contact with us. If you haven't registered for the API platform. So the MuleSoft Any Point Portal, again, just reach out through that email address and we can register straight away. We can set up a session of talking through how do we hit those test end points and production end points, so please feel free to reach out.

All right. So last slide today guys is any question, questions that you guys have generally about the program, about the demos that Cam went through, anything you want to ask. So we'll just wait and see if any questions sort of come through. Again, if you want to wait and ask us offline, again that tedious inbox is probably the best place, best point of contact for us. I'll just give you guys a minute. If not questions come through, we'll wrap it up.

I should have mentioned there are instructions in terms of asking questions so you can type a question in. You can raise your hand, that sort of thing. So we've just had a question through from Checks. Are designs filing still on the roadmap? Yes. So designs, as I mentioned, we're a little bit ahead of where we thought we'd be, Checks. In terms of designs, we're starting that planning work now, that discovery phase now. Our first API instance for designs will be the new designs application. At the moment, I'm sort of looking at Cam here, but in terms of the timeframe, I'd say between the next four to eight weeks for designs. Probably closer to eight weeks.


Cameron, IP Australia

Who said?


Josh, IP Australia

No, no, designs in new app.


Cameron, IP Australia

Yeah. You'll probably look at, yeah, at least eight weeks I'd say. Probably into getting on the media now. Probably really start of the new year, probably start to see some functionalities delivered there. But we are looking at it currently as part of the build. So it's definitely, definitely on the way.


Josh, IP Australia

So we'll keep you posted on that one, Checks. But the designs build itself in the discovery phase has commenced when we actually deploy those is probably another thing, I'll probably go a bit ahead of myself there, but hopefully we'd have something sort of towards the end of November or early December. We'll see how we're going. But if you've got any feedback around it, we're happy to set up sessions with your design's subject matter experts to inform some of that discovery work that our business analysts are doing currently.


Cameron, IP Australia

I was going to say, sorry, just adding on to designs there. It's probably worth noting API has recently done the design review. So obviously, a lot of people had to see their own designs application process, should be noted that we are trying to take a lot of that feedback onboard. Whether that's what we're currently looking at in terms of how we'll be delivering designs new apps and what kind of values we can add there.


Josh, IP Australia

All right. We might wrap up. I don't want to sort of waste too much of your time. We've gone a little bit over, again my fault. So we'll wrap up today. As I said, our comms guys will send out a wrap up by email probably tomorrow with the recorded session, but also the information about next session. So we'll confirm a date for December. But again, I encourage you guys to get in contact with us directly. We're more than happy to help out and get in front of people at your firms to talk about what these APIs could do or answer any questions that you guys have technically. So thanks again for your time today. We really appreciate it. Thanks to the speaker. Well, thanks to Cam from our end. We'll see you guys soon.