|
|
Jim Luth
Encoder spec is literally ready for release, right? It's gone through it's 90 day cycle of review and we're we'd like to publish it.
0:11:24.330 --> 0:11:28.290
Jim Luth
And the in theory, we'd like to publish it with the with the new status code.
0:11:29.600 --> 0:11:34.670
Jim Luth
And I guess Randy was about to explain to us how much work that is.
0:11:54.380 --> 0:11:55.190
Jim Luth
Well then it's.
0:11:35.900 --> 0:11:55.620
Randy Armstrong (OPC)
Well, it's the the point is we set up this process. We don't, we don't simply Willy nilly put new normative files into Git and publish them. We we have a process and and the process is a rata errata publish.
0:11:56.50 --> 0:12:6.530
Jim Luth
Yeah, but there's no. Yeah. OK, but yeah. OK. So, yeah, an unrelated. Well, again, we don't do errata anymore. So that that kind of doesn't make sense, but.
0:12:8.610 --> 0:12:9.360
Jim Luth
Yeah, unless we're.
0:12:6.190 --> 0:12:10.420
Paul Hunkar (OPC)
Unless it's going back to 104, which this doesn't need to.
0:12:10.380 --> 0:12:11.330
Jim Luth
The new staff.
0:12:8.850 --> 0:12:23.160
Randy Armstrong (OPC)
Ohh, right. OK, OK. Ohh OK. OK, well, maybe, maybe we need to have a new we. Maybe we should be discussing. What will our process be for updating the normative files in part 6 between releases of Part 6.
0:12:24.790 --> 0:12:28.580
Karl Deiretsbacher (OPC)
And it is it. Is it really required to change the node set?
0:12:29.370 --> 0:12:30.360
Jim Luth
No, I don't think so.
0:12:34.390 --> 0:12:34.780
Karl Deiretsbacher (OPC)
Yeah.
0:12:34.530 --> 0:12:35.570
Jim Luth
Yeah, right. Right.
0:12:36.940 --> 0:12:37.270
Jim Luth
Yeah.
0:12:29.430 --> 0:12:42.420
Randy Armstrong (OPC)
Well, no. The what? What I'm saying is, is that there's a whole bunch of normative files which are, which are penises and part 6. And all of these files are covered under the same process, one of which is the list of status codes.
0:12:42.660 --> 0:12:42.950
Jim Luth
Right.
0:12:42.720 --> 0:12:55.430
Karl Deiretsbacher (OPC)
Yes, I understand the the question is, I mean we we also also said that companion specs can also require new status codes and I mean.
0:12:54.80 --> 0:12:58.710
Randy Armstrong (OPC)
And that's all we that all in the past, that's always been done with an update to Part 6.
0:13:1.760 --> 0:13:2.70
Randy Armstrong (OPC)
So.
0:12:58.300 --> 0:13:3.240
Karl Deiretsbacher (OPC)
And I understand yes. But is, is that really necessary?
0:13:6.560 --> 0:13:6.930
Karl Deiretsbacher (OPC)
Yeah.
0:13:10.10 --> 0:13:10.440
Karl Deiretsbacher (OPC)
Umm.
0:13:3.760 --> 0:13:13.370
Randy Armstrong (OPC)
Well, again, it's up to us to decide on process my my only argument is we should have a process and stick to it and don't make exceptions every time. It's convenient.
0:13:13.830 --> 0:13:15.320
Karl Deiretsbacher (OPC)
No, no, I agree.
0:13:16.150 --> 0:13:16.590
Paul Hunkar (OPC)
Well.
0:13:15.680 --> 0:13:20.70
Volkmann, Frank (DI TI SR)
My assumption was that we have said XLS file because.
0:13:21.120 --> 0:13:26.90
Volkmann, Frank (DI TI SR)
Starts with. The codes come more frequently than specifications.
0:13:26.870 --> 0:13:27.170
Jim Luth
Umm.
0:13:27.20 --> 0:13:40.830
Randy Armstrong (OPC)
No, it's it's more of a case of the it's there because it's a, it's a, it's a computer readable, it's a computer readable form for the status codes. It's. I don't think it has anything to do with the frequency of updates.
0:13:42.650 --> 0:13:47.420
Karl Deiretsbacher (OPC)
But not not all status codes are in part 4, right?
0:13:48.90 --> 0:13:48.430
Paul Hunkar (OPC)
No.
0:13:54.930 --> 0:13:55.930
Karl Deiretsbacher (OPC)
Right, right.
0:14:2.170 --> 0:14:2.480
Jim Luth
Umm.
0:14:13.360 --> 0:14:13.640
Karl Deiretsbacher (OPC)
Umm.
0:13:48.360 --> 0:14:17.920
Randy Armstrong (OPC)
No, no, but the the, the the status codes include all the status codes. So even if FDI added status codes that was an update to Part 6, again it's the issue is given the fact we're not doing errata anymore, what process do we wanna put in place for updating the normative files to part six that allows us to release updates to these files between releases of Part 6. So we decide on a process we follow that process and all is good.
0:14:20.200 --> 0:14:33.70
Jim Luth
Right. Well, you we were using the the ERRATA because we already had that document that was frequently published to to push out to tell people, hey, we again we added new status codes to.
0:14:35.290 --> 0:14:35.620
Paul Hunkar (OPC)
To.
0:14:36.120 --> 0:14:44.440
Jim Luth
To to the files whatever right? That along with the other document stuff, right. So the Randy's got a good point. We don't have a, we don't have a way to do this right now that's formal.
0:14:51.420 --> 0:14:51.840
Randy Armstrong (OPC)
Yeah.
0:14:44.890 --> 0:15:8.920
Paul Hunkar (OPC)
Since there isn't a document for for these additional files, I mean Part 6 just has a reference, right? It's not a. No details on it. Maybe we should just be publishing and errata for those those files when they get updated. So just a special doc that's in a router doc for for those files looks like a normal rated doc and it's just for.
0:15:10.50 --> 0:15:11.740
Jim Luth
Or or is there just a train?
0:15:10.130 --> 0:15:12.360
Paul Hunkar (OPC)
The the reference files.
0:15:17.30 --> 0:15:17.350
Jim Luth
Hmm.
0:15:22.190 --> 0:15:22.380
Paul Hunkar (OPC)
OK.
0:15:22.460 --> 0:15:22.990
Paul Hunkar (OPC)
Yes, Sir.
0:15:10.740 --> 0:15:41.110
Randy Armstrong (OPC)
Well, it's it's it's things gets more complicated because we don't version these files individually, we version them, we version them with the Part 6 and in fact the new the new links we've all set up with the new links we've set up with with saying, OK, you've got the node set and here's where you go get the node set. And here's where you go get the supplementary files and you go to GitHub with A tag. And that tag has embedded within the version of the document that defined those supplementary files.
0:15:41.790 --> 0:15:42.620
Randy Armstrong (OPC)
So.
0:15:43.60 --> 0:15:46.450
Paul Hunkar (OPC)
Where we can't release extra versions of those. Not anymore.
0:15:44.970 --> 0:15:51.900
Randy Armstrong (OPC)
Well, no, we we if we do, we have to come up with a with a process. That's what I'm saying. It's we have we have to.
0:15:50.590 --> 0:15:56.580
Jim Luth
Well, well, yeah, right. But the process. But I guess what Paul's getting at the process could be simply moving the tag.
0:16:3.510 --> 0:16:3.780
Paul Hunkar (OPC)
Yeah.
0:15:57.260 --> 0:16:12.470
Jim Luth
Right. I mean if you wanted to make it as simple as possible, you you wouldn't change you would you would silently move the tag to the newer file and and basically somebody would then have the the new status code right now. Again, the problem is the question.
0:16:11.0 --> 0:16:23.620
Randy Armstrong (OPC)
Yes, that would that. That's that, that that's that's a that's a valid thing to do. And then we could have a secondary tag indicating that this was a. This was a update on such and such a date or something like that.
0:16:24.70 --> 0:16:26.350
Jim Luth
Yeah, right. Yeah. So like I said.
0:16:25.560 --> 0:16:28.390
Randy Armstrong (OPC)
So there's there's a record of the fact that it moved.
0:16:28.720 --> 0:16:41.350
Jim Luth
Move right and and then again. I think some of the problem is that like you just said, these are computer readable files. We don't have the equivalent of of a header or comments in these files. Can we put a change log in?
0:16:40.370 --> 0:16:43.220
Randy Armstrong (OPC)
It's CS, it's a, it's a CSV file.
0:16:43.530 --> 0:16:54.310
Jim Luth
Yeah. So you can. Yeah, right. I guess that's what I'm guessing. So you really can't, right. We can't have comments at the top that say, you know, On this date I added this new status code or anything like that, right? So.
0:16:54.230 --> 0:16:54.480
Randy Armstrong (OPC)
No.
0:16:55.240 --> 0:16:58.540
Jim Luth
Yeah. Then then, then the document. What we're doing.
0:17:2.360 --> 0:17:3.810
Jim Luth
Yeah, basically what?
0:16:56.810 --> 0:17:4.590
Paul Hunkar (OPC)
Other the docs in Git right? So we could put a comment into Git right? And the check in comment.
0:17:5.140 --> 0:17:21.940
Jim Luth
Yeah, but that's yeah. And that's I think that's that. That's kind of where we're where we're heading on this moves the tag create. Any other comment there's you know convention you want to sort of record what you're doing and why and what the change is and not that you can't do dips easily nothing and get.
0:17:22.730 --> 0:17:31.940
Randy Armstrong (OPC)
Well, no, no. If we do, if we move the tag, the comment has to be meaningful. It has to refer to a mantis item. A mantis issue. Yeah, yeah.
0:17:29.480 --> 0:17:41.460
Jim Luth
Yeah, sure. Yeah. Yeah. Right there. Yeah. All that right. Yeah. To make it that be the process, I would think we want to at least reserve the right to do something as simple and as quick as that. It's funny, it's my guess.
0:17:47.800 --> 0:17:48.90
Jim Luth
Do.
0:17:41.0 --> 0:17:48.470
Randy Armstrong (OPC)
Yeah. No. Yeah, I I, I don't know, oppose it. As long as, as long as we. We agreed on this is the way we're gonna do it moving forward.
0:17:48.780 --> 0:17:51.50
Jim Luth
Yeah, yeah, yeah. No, I think, yeah.
0:17:53.90 --> 0:17:53.320
Jim Luth
You know.
0:17:49.790 --> 0:17:53.820
Paul Hunkar (OPC)
And and we write it down somewhere. Probably but.
0:17:55.310 --> 0:17:58.180
Paul Hunkar (OPC)
Even if it's just in the meeting minutes today that you're.
0:18:0.510 --> 0:18:11.270
Randy Armstrong (OPC)
Well, no, this probably this, this, this maintenance thing probably should go into part 6 so 10503 as a sort of a general guidance on updating these normative files.
0:18:12.290 --> 0:18:12.600
Jim Luth
Mm-hmm.
0:18:12.90 --> 0:18:17.650
Paul Hunkar (OPC)
We're gonna note above the files that the the files may be updated between releases of this spec.
0:18:16.980 --> 0:18:18.490
Jim Luth
Listen, right?
0:18:20.340 --> 0:18:20.690
Jim Luth
That.
0:18:19.40 --> 0:18:21.480
Paul Hunkar (OPC)
And that the label will just change.
0:18:31.660 --> 0:18:32.710
Paul Hunkar (OPC)
And won't be different.
0:18:22.370 --> 0:18:36.560
Jim Luth
Yeah, at the same link it's so forth, right. So you you so you don't assume that you know, so you can't make the assumption that if you got the file once you if you go back and hit the link again and it won't be different, right. So that would be the note I would put in the part 6.
0:18:37.70 --> 0:18:37.440
Paul Hunkar (OPC)
Yeah.
0:18:38.310 --> 0:18:40.100
Jim Luth
But other than that, yeah.
0:18:41.430 --> 0:18:51.810
Jim Luth
Yeah. And again, we have to be careful. We wouldn't want to do this slipstream thing from many things, but, you know, adding a single status code or even a set of status codes.
0:18:52.750 --> 0:18:55.70
Jim Luth
It can't mess anybody up per se.
0:18:56.350 --> 0:18:58.20
Jim Luth
I guess the issue becomes.
0:18:59.690 --> 0:19:0.770
Jim Luth
It's maybe.
0:19:12.650 --> 0:19:14.350
Jim Luth
One right with no.
0:18:59.890 --> 0:19:14.680
Randy Armstrong (OPC)
Well, no, but the the the point is, is that you could end up having an argument because 11 product has suggested the original one. Another one suggested the updated one, and they're both both insisted.
0:19:14.840 --> 0:19:16.510
Randy Armstrong (OPC)
In both insisting they.
0:19:15.810 --> 0:19:21.740
Jim Luth
They had the latest one. Yeah. Right. Yeah, yeah, I know. That's fair. Yeah. Maybe we would. Do we need to think about this?
0:19:25.100 --> 0:19:25.410
Paul Hunkar (OPC)
Well.
0:19:24.870 --> 0:19:27.0
Jim Luth
Yeah, I thought we had. I thought it is.
0:19:35.730 --> 0:19:37.180
Jim Luth
Yeah, right. But it's still.
0:19:38.430 --> 0:19:38.760
Jim Luth
Yeah.
0:19:44.270 --> 0:19:45.580
Jim Luth
No, we don't allow them.
0:19:45.930 --> 0:19:48.180
Randy Armstrong (OPC)
No. Yeah. No. Yeah, it's.
0:19:26.380 --> 0:19:48.390
Paul Hunkar (OPC)
Adding error codes though, though what you're missing. If you ingested it and you don't get it is you still have the code. Just don't have the description for it. Alright, so if you have it ingested and and you have to be prepared for vendor defined error codes and other things too. So no, that's true. You're right. They have to be.
0:19:49.40 --> 0:19:50.420
Jim Luth
It's kind of a big, I mean.
0:19:59.120 --> 0:19:59.670
Paul Hunkar (OPC)
OK.
0:20:0.720 --> 0:20:2.630
Jim Luth
Umm so.
0:20:3.830 --> 0:20:4.910
Jim Luth
I thought in part.
0:20:5.990 --> 0:20:18.620
Jim Luth
What I thought in part 6 the we had two references to files, one that's supposed to be the latest that that compatible with this version and one that's locked to a version in my dreaming that.
0:20:19.850 --> 0:20:25.220
Jim Luth
I thought I thought it was more a little more complicated than just the file link in Part 6.
0:20:28.910 --> 0:20:30.10
Jim Luth
Andy, do you remember?
0:20:50.980 --> 0:20:54.430
Jim Luth
I said to get you to everything I say, right?
0:20:30.490 --> 0:20:59.100
Randy Armstrong (OPC)
Ohh yeah. Well, no, we we we're changing how this is all working because we're integrating it in with the online reference. So what now what's now gonna happen is there's there's basically gonna be 2 links, one link to the node set and one link that will download the node set one link to the and one link to the GitHub tag that will download and and I'll get you everything and the link to the GitHub tag will.
0:21:1.570 --> 0:21:2.420
Randy Armstrong (OPC)
Well.
0:21:6.610 --> 0:21:7.720
Randy Armstrong (OPC)
And I was gonna say.
0:21:9.270 --> 0:21:10.180
Randy Armstrong (OPC)
Yeah, it's just sort of.
0:21:9.380 --> 0:21:14.260
Jim Luth
So it's almost like we need. We need. Yeah, but again, I'm almost thinking we need we need.
0:21:15.390 --> 0:21:19.80
Jim Luth
We we need to kind of two tags when when you when you put out.
0:21:19.970 --> 0:21:21.250
Jim Luth
You have a sort of a.
0:21:22.80 --> 0:21:25.690
Jim Luth
Version dependent tag. You don't think of it as date.
0:21:24.410 --> 0:21:44.150
Randy Armstrong (OPC)
Oh no, but that but this is already taken care of. You have a version to you have a link that will give you the latest version whatever it is. And then you'll have another link that will give you the specific GitHub we'll give you. Basically what happens is all these links go to the online reference and the online reference uses its database to figure out what you really want it to get.
0:21:44.660 --> 0:21:45.370
Jim Luth
OK.
0:21:45.430 --> 0:21:56.590
Randy Armstrong (OPC)
And and then and then it gives it back to you. So we don't need to, we don't need to worry about having all these permutations and combinations because everything everything happens automatically right now.
0:21:57.610 --> 0:22:4.30
Paul Hunkar (OPC)
Yeah, OK, I that explains then the problem I'm having with the mdis reference that you gave me because it doesn't work.
0:22:4.590 --> 0:22:7.470
Randy Armstrong (OPC)
OK. Well, we need to figure out what's wrong with that MDIS refer.
0:22:6.720 --> 0:22:8.550
Paul Hunkar (OPC)
Yeah. So it's yeah.
0:22:14.350 --> 0:22:14.700
Jim Luth
But.
0:22:10.430 --> 0:22:15.210
Paul Hunkar (OPC)
OK, I didn't write. Things weren't going to get directly. They're going to the online.
0:22:15.930 --> 0:22:16.650
Paul Hunkar (OPC)
Reference.
0:22:15.920 --> 0:22:20.390
Jim Luth
But what? I'm yeah, well, what I'm concerned about Randy, is that.
0:22:21.520 --> 0:22:29.480
Jim Luth
So if if we have the policy where the the latest one gets you to the latest one, and certainly you can go there any day and get the latest stuff.
0:22:31.570 --> 0:22:47.530
Jim Luth
At some point I wanna know which versions I have and and what the real tag is for those. In other words, A tag that isn't gonna change and then if if I have two tags that point to the same one then it's fine it it it says the latest it is.
0:22:53.450 --> 0:22:53.770
Jim Luth
Right.
0:22:56.610 --> 0:22:56.880
Jim Luth
Right.
0:22:47.0 --> 0:23:1.210
Randy Armstrong (OPC)
Well, I'll I'll up until the discussion today. There was a single permanent tag that would never move. So you would release the spec, you put a permanent tag in there and the and the and the link would take you to that tag forever and ever.
0:22:59.620 --> 0:23:15.80
Jim Luth
Yeah, yeah. And and that right and from a Lincoln from the spec, I don't I don't wanna change that linkage to the spec. What what I'm what I'm basically saying is if I've landed on the linkage from the spec to the what clearly is the latest version that goes with my spec version.
0:23:15.980 --> 0:23:25.300
Jim Luth
I want to be able to see what are the older versions that used to be at that tag and when they were and be able to compare them.
0:23:32.340 --> 0:23:32.850
Jim Luth
OK.
0:23:25.550 --> 0:23:39.10
Randy Armstrong (OPC)
Well, that, that's that kind of stuff you have to. We're kind of deferring to the GitHub versioning mechanism that that this is this is not something that we want. We should we shouldn't have to do a bunch of a bunch of stuff they.
0:23:39.90 --> 0:23:39.470
Randy Armstrong (OPC)
Yeah.
0:23:50.80 --> 0:23:50.460
Randy Armstrong (OPC)
Yeah.
0:23:37.770 --> 0:23:53.450
Jim Luth
Yeah, right. As long, right? So is it the point is it? And you're saying it it, it should be fairly obvious if I were to then find the file I wanted then and view the history of it, you could see when when it was changed and what the diffs were and matter what, when.
0:23:51.540 --> 0:23:56.990
Randy Armstrong (OPC)
Yes, and and and and you would see a history of tags applied to the file in that kind of thing.
0:23:56.430 --> 0:24:18.640
Jim Luth
File. Right. OK. So so then we probably have all of all that we need, I think like I said then, I would suggest we just in part six when we get around to it in the next version we we basically warn people that this is the case, right that the that the tag is always for the latest and the there could be you know.
0:24:24.930 --> 0:24:25.450
Jim Luth
Yeah, but.
0:24:18.60 --> 0:24:30.70
Randy Armstrong (OPC)
Well, no, the tag is not for the latest. The tag is. The tag is for the version that's released with the specification, the latest is. The latest is basically the latest, the latest version in GitHub.
0:24:32.190 --> 0:24:35.60
Jim Luth
OK, so the unreleased stuff.
0:24:36.90 --> 0:24:36.310
Jim Luth
On.
0:24:38.140 --> 0:24:38.410
Jim Luth
I know.
0:24:35.870 --> 0:24:47.540
Randy Armstrong (OPC)
Well, actually actually no, because we got two, we got two repositories. We've got one repository that has unreleased stuff and we've got one repository that only has release stuff and.
0:24:46.810 --> 0:24:47.800
Jim Luth
OK, good.
0:24:47.730 --> 0:25:14.580
Randy Armstrong (OPC)
And and so. So basically what will happen is, well, actually no, the way it's set up now, you'll always go to the latest thing. So if we release 1.053, then you'll you'll link to 1.053 when we release 1.054, then you will link to the tag for 1.054. So basically it's always taking you to A tag that is the latest version for the specification in question.
0:25:15.990 --> 0:25:16.250
Randy Armstrong (OPC)
Yeah.
0:25:14.130 --> 0:25:22.670
Jim Luth
For the specification, but now we're talking about within the specification tag that isn't changing. There may be changes to files.
0:25:24.90 --> 0:25:25.570
Jim Luth
That that's what we're talking about.
0:25:27.210 --> 0:25:34.720
Randy Armstrong (OPC)
No. When saying is is, if you put A tag, you're not changing any files. If you change files, that should be a new tag.
0:25:37.770 --> 0:25:38.240
Jim Luth
So.
0:25:37.450 --> 0:25:39.810
Paul Hunkar (OPC)
But the spec has a reference to A tag.
0:25:40.610 --> 0:25:52.210
Randy Armstrong (OPC)
The spec has a reference to A tag, but the spec has a reference that will take you to the original 1 so but the but the version independent one will take you to the latest. So what we could do?
0:25:54.250 --> 0:25:54.780
Randy Armstrong (OPC)
You.
0:25:51.300 --> 0:25:58.880
Paul Hunkar (OPC)
But the latest, latest, even if it's, you know, 102103104, it would take you to 104 or whatever, right?
0:25:58.210 --> 0:25:59.720
Randy Armstrong (OPC)
Yeah, yeah, yeah, yes.
0:26:0.150 --> 0:26:0.510
Paul Hunkar (OPC)
OK.
0:26:1.70 --> 0:26:31.200
Randy Armstrong (OPC)
Yeah, that's that's well, I could put special logic in for the 104 series and the 105 series, but that's that's a separate discussion right now. It's just gonna take you to the 1:05, no matter what version of UA you're dealing with. But what we could do is we could instead of trying to do these silent updates, we could introduce sort of letter versions. So we have A tag and then the original tag and then we put an A after that tag to indicate that it was modified. And then.
0:26:31.610 --> 0:26:48.250
Randy Armstrong (OPC)
And then what will happen is if that version is still the latest, then the redirect will take you to the A version. So you'll have a slightly different tag to indicate that something changed, but the redirect to the latest will still take you to that.
0:26:48.940 --> 0:26:52.350
Jim Luth
Take it to the and then the visa B. It'll take you to the B and so forth.
0:26:52.480 --> 0:27:2.310
Randy Armstrong (OPC)
Is it about what will happen is as soon as as soon as that that is superseded by the next version of the spec, then you'll be taken to the next version. The spec so 1.0345.
0:27:0.850 --> 0:27:9.0
Jim Luth
Ohh sure, yeah, yeah, I understand right. All moves first. Yeah. So you're basically talking about this a point version or, you know, a patch version or something, right.
0:27:9.290 --> 0:27:23.900
Randy Armstrong (OPC)
Yeah, well, yeah. So we could, we could talk about this and say this is an exception for this that we could say that the letter, the letter extensions only apply to changes to normative files that had no impact on the specification text.
0:27:24.740 --> 0:27:25.230
Randy Armstrong (OPC)
Yes.
0:27:27.220 --> 0:27:28.280
Randy Armstrong (OPC)
Yeah. Yeah, so.
0:27:34.950 --> 0:27:35.370
Randy Armstrong (OPC)
Yes.
0:27:22.620 --> 0:27:37.540
Jim Luth
It's on the specification, right? Yeah, this is what I'm. Yeah. And this is what I'm getting at. So. So if I see this, I know what it is. And I know how to find the older ones by their tags, and then I can do diffs and and get to see what games and all that. OK.
0:27:38.300 --> 0:27:41.740
Jim Luth
That that seems reasonable, at least to have the capability of doing that.
0:27:44.340 --> 0:27:58.630
Jim Luth
So the plan then would be to put this new code in the file and give it an A and make sure that this file is now the one that you get to from following the links from even the.
0:28:7.580 --> 0:28:10.550
Jim Luth
To do the work. Yeah. Yeah, I understand. Yeah. Yeah.
0:28:11.910 --> 0:28:13.390
Jim Luth
That's right, right. Yeah.
0:28:24.210 --> 0:28:25.240
Jim Luth
Yes, we go, yeah.
0:28:26.760 --> 0:28:27.100
Jim Luth
Right.
0:27:57.880 --> 0:28:28.210
Randy Armstrong (OPC)
Well, will the beauty, the beauty of it if we do it the way I'm proposing it, I'm proposing it. We're basically relying on relying on the online reference database to do the redirect. Yeah, to do the work that this spec won't change. So you'll have the version specific link you'll basically say click on this link to get the latest, you get the version associated with this version of the specification. If we've released an A version, then the online reference will redirect you to the A version instead of the original version.
0:28:28.390 --> 0:28:31.480
Randy Armstrong (OPC)
But the original tag will still be there and.
0:28:36.830 --> 0:28:37.200
Jim Luth
Right.
0:28:41.750 --> 0:28:42.520
Jim Luth
Teacher.
0:28:32.400 --> 0:28:43.760
Randy Armstrong (OPC)
And so, but the A will indicate that, hey, this is changed slightly and then we simply document document with the Convention of using the ABC to indicate. Yeah.
0:28:43.810 --> 0:28:50.370
Jim Luth
Yeah, right. That's what I said. So the only thing eventually will change is will give some hints and part 6 to tell people this is what's gonna happen, right?
0:28:50.470 --> 0:28:50.920
Randy Armstrong (OPC)
Yes.
0:28:51.130 --> 0:28:53.180
Jim Luth
So yeah, OK, I I'm OK with that.
0:28:54.270 --> 0:28:57.690
Jim Luth
Because that, like I said, by doing that and doing this, you know?
0:28:58.370 --> 0:29:0.930
Jim Luth
Now we can we can release the.
0:29:1.910 --> 0:29:3.100
Jim Luth
The this.
0:29:10.370 --> 0:29:10.830
Randy Armstrong (OPC)
Yeah.
0:29:4.360 --> 0:29:18.690
Jim Luth
Companion spec. With this new code in it and in theory the links will all work and and everything. Will you know by the time somebody has this new spec and goes to get the files, they'll find the code is there, right?
0:29:19.20 --> 0:29:29.650
Randy Armstrong (OPC)
Yeah, unfortunately what's happened is that the is. It is that there's gonna be a bit of a lag because we have to update. We have to release 1.03 before all of the links will be updated.
0:29:31.250 --> 0:29:31.850
Jim Luth
Anyway.
0:29:31.250 --> 0:29:35.600
Randy Armstrong (OPC)
Right now the old links don't support this kind of flexibility that I'm talking about.
0:29:36.190 --> 0:29:36.620
Jim Luth
I see.
0:29:37.660 --> 0:29:38.130
Jim Luth
OK.
0:29:41.250 --> 0:29:43.150
Jim Luth
So yeah, I guess that becomes a.
0:29:47.390 --> 0:29:48.310
Jim Luth
Yeah, interesting.
0:29:49.150 --> 0:29:56.500
Jim Luth
But you could. Yeah. OK, the links won't be correct, but you could put in. You could put in. You could put the A.
0:29:57.140 --> 0:30:1.400
Jim Luth
Tag on the new file and put it in the release of the story.
0:30:1.450 --> 0:30:6.370
Randy Armstrong (OPC)
I've been GitHub will be will be will be fine. We can do that immediately but the.
0:30:12.610 --> 0:30:14.310
Paul Hunkar (OPC)
Mantis issue, yeah.
0:30:4.0 --> 0:30:23.830
Jim Luth
Will be fine from and so right? So right there's a right. So it at worst comes to worst. We put a note in in the in the Profinite encoder fact to say ohh. You know this will all get fixed up later. But for now make sure you you go to this tag to get the the you know the the the the.
0:30:23.400 --> 0:30:31.870
Randy Armstrong (OPC)
Well, no. Well, with the PROFINET, I can give them the correct online reference link that will take them to the versions that specific tag.
0:30:34.230 --> 0:30:35.610
Paul Hunkar (OPC)
They wouldn't even put it in there.
0:30:35.970 --> 0:30:37.670
Randy Armstrong (OPC)
OK. Yeah.
0:30:32.760 --> 0:30:41.920
Jim Luth
Yeah, but normally they wouldn't even have that in their in their document. I'm saying this is a special note thing to say. You know, for now, make sure you in order to get the latest.
0:30:42.560 --> 0:30:43.690
Jim Luth
Umm, you know?
0:30:49.40 --> 0:30:49.480
Paul Hunkar (OPC)
Like.
0:30:52.910 --> 0:30:54.580
Paul Hunkar (OPC)
They can delete from the spec.
0:30:44.900 --> 0:31:2.770
Jim Luth
Error code list that's required by this spec. Please use this link right so you will give them a link, but it's it's something that eventually they you know they can believe. Yeah. Use this one until there's something until it's, you know, 1.0503 or beyond and then use the regular.
0:31:3.490 --> 0:31:3.710
Randy Armstrong (OPC)
Umm.
0:31:3.910 --> 0:31:8.80
Jim Luth
Like or whatever it's again, they they they can put in something like that, that.
0:31:8.760 --> 0:31:17.10
Jim Luth
At least gets people to the right point for today and and tell them how they know when to get some, when, when it's been superseded. Basically, right? Yeah.
0:31:15.670 --> 0:31:21.280
Paul Hunkar (OPC)
The did they submit text for this thing on what we want it to say to for their code?
0:31:23.840 --> 0:31:24.160
Jim Luth
Yeah.
0:31:26.540 --> 0:31:28.540
Paul Hunkar (OPC)
There is. It's on the screen.
0:31:27.470 --> 0:31:28.880
Jim Luth
Yeah, that's we're looking at.
0:31:30.900 --> 0:31:32.430
Jim Luth
Yeah. Can you see the screen on me?
0:31:34.420 --> 0:31:34.680
Jim Luth
Yeah.
0:31:22.160 --> 0:31:39.410
Randy Armstrong (OPC)
Well, OK, there. There needs to be a mantis issue put against part six that says exactly exactly what text put in. And the second thing is we need a mantis issue against Part 6 to to update the update. The basically document everything that we just discussed today.
0:31:39.780 --> 0:31:40.690
Jim Luth
Yeah. OK.
0:31:42.510 --> 0:31:48.140
Paul Hunkar (OPC)
So this is the thing, the request operation is not allowed because the node is not locked by the application.
0:31:49.630 --> 0:31:52.140
Paul Hunkar (OPC)
I would get rid of the by the application.
0:31:54.850 --> 0:32:1.390
Paul Hunkar (OPC)
Because I don't know if we wanna limit it to to that that just say it's not locked.
0:32:5.940 --> 0:32:6.950
Jim Luth
Yeah. And imagine.
0:32:5.890 --> 0:32:7.430
Paul Hunkar (OPC)
Makes it a little more generic.
0:32:7.820 --> 0:32:11.930
Jim Luth
Well, and I'm not sure I mean and even the reference to the node maybe a little bit.
0:32:17.950 --> 0:32:18.760
Paul Hunkar (OPC)
Yeah, yeah.
0:32:13.840 --> 0:32:24.580
Jim Luth
You you don't know what the request was and whether a node was was referenced request. So yeah, I I I don't. I'm not sure where this came from.
0:32:22.960 --> 0:32:34.960
Paul Hunkar (OPC)
How about the operation? The requested operation is not allowed because no lock was was or the because it was not because no lock exists.
0:32:38.760 --> 0:32:39.550
Haage, Ulrich (DI FA SEA R&D-AT STI)
Uh, yes.
0:32:42.0 --> 0:32:42.390
Paul Hunkar (OPC)
Yeah.
0:32:43.100 --> 0:32:43.430
Paul Hunkar (OPC)
Yeah.
0:32:43.30 --> 0:32:43.460
Jim Luth
Yeah.
0:32:39.630 --> 0:32:43.570
Haage, Ulrich (DI FA SEA R&D-AT STI)
Yeah, I'm may. I interrupt one moment.
0:32:44.390 --> 0:32:51.440
Haage, Ulrich (DI FA SEA R&D-AT STI)
Yeah, I I have merely adapted the description of the bad locked so.
0:32:59.250 --> 0:32:59.580
Haage, Ulrich (DI FA SEA R&D-AT STI)
Umm.
0:32:51.480 --> 0:33:2.890
Jim Luth
Ohh, interesting. OK. Yes, that's that is significant then. So yeah, if bad lock refers to a node and everything else then then then I would agree then that it doesn't make sense.
0:33:4.780 --> 0:33:5.90
Jim Luth
Yeah.
0:33:5.790 --> 0:33:8.690
Paul Hunkar (OPC)
This bad luck still say that, OK.
0:33:10.440 --> 0:33:10.990
Haage, Ulrich (DI FA SEA R&D-AT STI)
Yeah.
0:33:10.290 --> 0:33:13.360
Karl Deiretsbacher (OPC)
Well, the lock the lock is on a node.
0:33:14.710 --> 0:33:23.700
Jim Luth
It is unknown, right? But the operation may be somewhat disjoint from the node, but that's I guess you're you have to know enough about that. The lock is certainly on the node.
0:33:24.400 --> 0:33:24.870
Karl Deiretsbacher (OPC)
Yeah.
0:33:25.480 --> 0:33:25.930
Jim Luth
So.
0:33:27.120 --> 0:33:27.510
Jim Luth
Yeah.
0:33:27.120 --> 0:33:31.270
Haage, Ulrich (DI FA SEA R&D-AT STI)
It it is, it is as general as it can be, I think.
0:33:31.590 --> 0:33:31.990
Jim Luth
Umm.
0:33:31.980 --> 0:33:36.870
Paul Hunkar (OPC)
Why I think you can get rid of by the application and it doesn't hurt anything, right?
0:33:40.840 --> 0:33:43.730
Jim Luth
Or by the requester or something, right?
0:33:43.210 --> 0:33:44.570
Paul Hunkar (OPC)
Yeah, by the requester.
0:33:45.0 --> 0:33:46.130
Karl Deiretsbacher (OPC)
Yeah, that's true.
0:33:49.370 --> 0:33:50.380
Paul Hunkar (OPC)
I like that better.
0:33:53.700 --> 0:33:56.820
Haage, Ulrich (DI FA SEA R&D-AT STI)
OK, I'm I.
0:33:55.940 --> 0:33:59.610
Paul Hunkar (OPC)
But we can edit the gym, can edit the, add a note to the.
0:34:0.430 --> 0:34:5.190
Paul Hunkar (OPC)
Yes, it up on the screen. He can add a note to the issue and then assign it to Randy.
0:34:5.960 --> 0:34:6.790
Paul Hunkar (OPC)
And then.
0:34:8.210 --> 0:34:10.460
Paul Hunkar (OPC)
Who's gonna enter the issue for? Um.
0:34:13.900 --> 0:34:15.220
Paul Hunkar (OPC)
Updating the process.
0:34:13.680 --> 0:34:17.900
Karl Deiretsbacher (OPC)
Yeah, I can. I can make it to. I can make a duplicate for part 100.
0:34:19.680 --> 0:34:24.770
Randy Armstrong (OPC)
Well, no. The other issues apart 6 update because we need to document this process in part 6.
0:34:26.140 --> 0:34:27.560
Karl Deiretsbacher (OPC)
Oh, this one? Yeah.
0:34:29.620 --> 0:34:33.270
Randy Armstrong (OPC)
The all the discussions today need to be put into an mantis issue.
0:34:52.410 --> 0:34:53.120
Jim Luth
OK.
0:34:54.120 --> 0:34:58.510
Randy Armstrong (OPC)
So you can cut and paste, you can cut and paste the meeting minutes into the mantis issue. |
