On 6 June 2018 at 16:11, Ben Craig <ben.craig_at_[hidden]> wrote:
> I’ve heard some off-list questions about what wg21 can and cannot do,
> particularly when it comes to things regarding package management. I’m
> hoping to get some clarifications here.
>
>
>
> Does wg21 (and SG15) have the authority to produce a specification for a
> package / dependency manager?
>
>
>
> What if the package manager isn’t just a C++ package / dependency manager,
> but a general purpose package / dependency manager?
>


My understanding is that all International Standards produced by ISO
(this is not specific to WG21) specifies interfaces, nomenclatures,
basically common specifications of "normal" values and behaviour of a
system or product, etc.
So if my understanding is correct, an "interface" of a build system,
or at least the description and name of it's operations
could be specified.
A specific implementation could not be an International Standard.

That being said, I'm not a specialist, maybe I'm missing something.
>From what I read on the wikipedia page[1], it's not 100% clear what an
International Standard might or not specify,
but it's clearly just a document.

A. Joël Lamotte

[1] https://en.wikipedia.org/wiki/International_Organization_for_Standardization

>
>
> (BIG NOTE: I am not asking if wg21 and sg15 have the time or the
> willingness. I’m just asking if it is allowable. I don’t expect the time
> or willingness questions to be answerable on the mailing lists.)
>
>
>
> Here’s a relevant note from the ISO Code of Conduct (
> https://www.iso.org/files/live/sites/isoorg/files/publications/en/pub100397.pdf
> )
>
> “Agree to a clear purpose and scope: We are committed to having a clear
> purpose, scope, objectives and plan to ensure the timely development of
> International Standards.”
>
>
>
> Do we need to agree somewhere as to what the scope of wg21 is, or has that
> scope been agreed upon and set in a standing document somewhere?
>
>