You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ossie.apache.org by "rostislavosvald-ataccama (via GitHub)" <gi...@apache.org> on 2026/10/22 13:27:03 UTC
[PR] feat(core): register ATACCAMA as a well-known vendor [ossie]
rostislavosvald-ataccama opened a new pull request, #629:
URL: https://github.com/apache/ossie/pull/629
The Ataccama converter in apache/ossie-converters tags its custom extensions with the ATACCAMA vendor name, which needs to be available on OssieVendor before the converter can resolve it against this package.
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
## Summary
This PR adds `ATACCAMA` among known vendors to the python models and to the specification examples. We are in process of introducing Ataccama convertor, which will expose its custom extension.
## Related Issues
None
## Checklist
### Specification
- [x] Spec changes are included in `core-spec/` and follow the existing structure
- [ ] Spec changes have been discussed on the mailing list or in a linked issue
- [x] Breaking changes to the spec are clearly called out in the summary
### Ontology
N/A
### Converters
- [ ] Spec or ontology changes that affect converters have a matching issue or PR in [apache/ossie-converters](https://github.com/apache/ossie-converters)
Convertor PR will be created soon, however there is a light dependency on the model change.
### Validation
N/A
### Documentation
N/A: some vendors are mentioned in the docs, but there doesn't seem to be a need to enumerate all
### Examples
- [x] `examples/` are added or updated for any new spec constructs (no new constructs)
### Tests
- [x] All existing tests pass (`pytest` / CI green)
- [x] New functionality is covered by tests (N/A)
### Compliance
- [x] ASF license headers are present on all new source files (no new files)
- [x] No third-party dependencies are added without PMC/IPMC approval (none added)
- [x] If third-party source code is vendored/copied (not just declared as a dependency), `NOTICE` and/or `LICENSE` have been updated per [ASF policy](https://infra.apache.org/licensing-howto.html) (no such code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(core): register ATACCAMA as a well-known vendor [ossie]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #629:
URL: https://github.com/apache/ossie/pull/629#issuecomment-6348598501
Thank you for your first contribution to Apache Ossie (incubating)!
A committer will review your PR. In the meantime, please ensure:
- All CI checks pass
- ASF license headers are present on new source files
- Tests cover new functionality
No ICLA is required to contribute. If you are elected as a committer in the future, you will need an [Individual Contributor License Agreement (ICLA)](https://www.apache.org/licenses/contributor-agreements.html) on file with the ASF.
**Questions?** Ask in the PR comments or join us on [Slack](https://join.slack.com/t/apache-ossie/shared_invite/zt-4drnzih1v-T0tcnaZZoLlddLh_plY~bw).
We appreciate your contribution!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(python): add ATACCAMA to OssieVendor [ossie]
Posted by "rostislavosvald-ataccama (via GitHub)" <gi...@apache.org>.
rostislavosvald-ataccama commented on PR #629:
URL: https://github.com/apache/ossie/pull/629#issuecomment-6361133668
> > > fyi: in #617, we're aiming to remove specific vendor examples from the core spec into an extensions folder. this means that new vendors can register as a known-constant without the usual 7 day DISCUSS period on the mailing list before merging.
> > > If you scope the change to just models.py, I can fold your vendor registration into 617 and get this merged today
> >
> >
> > @christianeu-db Yes that would be great, thank you. Is there something you need from me for this?
>
> @rostislavosvald-ataccama just scope the PR down to the models.py change and revert the rest. I'll add | `ATACCAMA` | Ataccama-specific attributes to the new table in #617
@christianeu-db Updated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(core): register ATACCAMA as a well-known vendor [ossie]
Posted by "christianeu-db (via GitHub)" <gi...@apache.org>.
christianeu-db commented on PR #629:
URL: https://github.com/apache/ossie/pull/629#issuecomment-6360070733
> > fyi: in #617, we're aiming to remove specific vendor examples from the core spec into an extensions folder. this means that new vendors can register as a known-constant without the usual 7 day DISCUSS period on the mailing list before merging.
> > If you scope the change to just models.py, I can fold your vendor registration into 617 and get this merged today
>
> @christianeu-db Yes that would be great, thank you. Is there something you need from me for this?
@rostislavosvald-ataccama just scope the PR down to the models.py change and revert the rest. I'll add | `ATACCAMA` | Ataccama-specific attributes to the new table in #617
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(python): add ATACCAMA to OssieVendor [ossie]
Posted by "christianeu-db (via GitHub)" <gi...@apache.org>.
christianeu-db merged PR #629:
URL: https://github.com/apache/ossie/pull/629
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(core): register ATACCAMA as a well-known vendor [ossie]
Posted by "rostislavosvald-ataccama (via GitHub)" <gi...@apache.org>.
rostislavosvald-ataccama commented on PR #629:
URL: https://github.com/apache/ossie/pull/629#issuecomment-6359943246
> fyi: in #617, we're aiming to remove specific vendor examples from the core spec into an extensions folder. this means that new vendors can register as a known-constant without the usual 7 day DISCUSS period on the mailing list before merging.
>
> If you scope the change to just models.py, I can fold your vendor registration into 617 and get this merged today
@christianeu-db Yes that would be great, thank you. Is there something you need from me for this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org