[media-types] Re: [IANA #1420197] application/vnd.pp .systemverify+xml registration request

> Published specification: The format will be described by an XSD.

Could the XSD be linked to in this registration?  If not, will there be a URL in the content that can be dereferenced to access the XSD e.g. schemaLocation? If yes, how would someone creating a "systemverify" document know that they have to provide a schemaLocaltion?

I'm just trying to make sure that there is some way to discover this XSD.

Darrel
________________________________
From: Amanda Baber via RT <[email protected]>
Sent: Monday, June 2, 2025 12:23 PM
Cc: Darrel Miller <[email protected]>; [email protected] <[email protected]>
Subject: [IANA #1420197] application/vnd.pp.systemverify+xml registration request

Hi Darrel,

Can you review this one by June 16th?

thanks,
Amanda

=====

Name: Graham Leggett

Email: [email protected]

Media type name: application

Media subtype name: vnd.pp.systemverify+xml

Required parameters: N/A

Optional parameters: N/A

Encoding considerations: binary

Security considerations: The systemverify format describes the requirements of a
software system, and contains no active elements or
elements by reference. The intention is to support XML
signatures so that the entity publishing the requirements
can be strongly identified. As an XML format, security
considerations described by RFC7303 section 10 apply.

Interoperability considerations: The XML in the format is namespaced to allow future
extension of the format.

Published specification: The format will be described by an XSD.

Applications which use this media: System Verify application, a tool that can compare a defined set of requirements with what is actually installed.

Fragment identifier considerations: Fragments would be handled as per XHTML.

Restrictions on usage: None.

Provisional registration? (standards tree only): No

Additional information:

1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): systemverify
4. Macintosh file type code: none
5. Object Identifiers: none

General Comments:

Person to contact for further information:

1. Name: Graham Leggett
2. Email: [email protected]

Intended usage: COMMON

Used as a document format that can describe the requirements of
a software system. This can be used by tools that compare the
requirements of a system to what is actually installed.

Author/Change controller: Graham Leggett

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]