authoringToolURI constraints

HaroldHallikainen commented 4 years ago

Issue 2: authoringToolURI constraints ST 2098-2 requires that authoringToolURI be a "Uniform Resource Identifier as defined by IETF RFC 2396 with the authority component being a DNS resolvable domain name," but not all URIs have an authority component, e.g. URNs, relative URIs, etc. It is not clear if ST 2098-2 means that authoringToolURI shall be: • any generic URI in absolute form, i.e. ://?; or • specifically HTTP URIs, i.e. http://example.com/hello In other words, are the following valid authoringToolURI values? https://example.com/hello ftp://example.com/hello urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 Also, IETF RFC 2396 is obsoleted and should be replaced by RFC 3986.

HaroldHallikainen commented 4 years ago

The goal here is to guarantee the uniqueness of the authroringToolURI. It seems that a resolvable domain name is required to guarantee uniqueness, but I am not expert on URIs.

mingyan-xperi commented 4 years ago

I will check with the engineer who originally raised the issue for further feedback.

===== Update: Having checked, here's a suggested text for group consideration.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:
- the authority component shall be present;
- the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035.

jpviollet commented 4 years ago

We're ok with Ming's proposal below:

============== The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:

the authority component shall be present;
the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035.

==============

HaroldHallikainen commented 4 years ago

We currently require the host subcomponent be registered to the authoring tool vendor. With the above wording, are people free to use any DNS fully qualified domain name, including one registered to someone else?

mingyan-xperi commented 4 years ago

We currently require the host subcomponent be registered to the authoring tool vendor.

Yes, this was missed.

Suggest to simply add this existing requirement to proposal, as below.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:
- the authority component shall be present;
- the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035;
- the host subcomponent shall be a domain name registered to the authoring tool vendor to prevent duplication between tool identifiers provided by different vendors.

mingyan-xperi commented 4 years ago

@RogerDressler Hi, Roger

Following up on my TODO item from meeting yesterday, here are the normative refs for the 2 IETF RFC documents

IETF RFC 3986, "Uniform Resource Identifier (URI): Generic Syntax", January 2005 (url: https://tools.ietf.org/html/rfc3986 ) IETF RFC 1035, "Domain names - implementation and specification", November 1987 (url: https://tools.ietf.org/html/rfc1035 )

As for formatting, replacing hyphens with bullet points makes them look better, I think. ie.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:

the authority component shall be present;
the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035;
the host subcomponent shall be a domain name registered to the authoring tool vendor to prevent duplication between tool identifiers provided by different vendors.

HaroldHallikainen commented 4 years ago

I do not yet see these changes in the document (new normative references and changing dashes to bullets). Should we complete a review on the assumption these changes will be made?

Thanks!

Harold

@RogerDressler Hi, Roger

Following up on my TODO item from meeting yesterday, here are the normative refs for the 2 IETF RFC documents

IETF RFC 3986, "Uniform Resource Identifier (URI): Generic Syntax", January 2005 (url: https://tools.ietf.org/html/rfc3986 ) IETF RFC 1035, "Domain names - implementation and specification", November 1987 (url: https://tools.ietf.org/html/rfc1035 )

As for formatting, replacing hyphens with bullet points makes them look better, I think. ie.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:

the authority component shall be present;

the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035;

the host subcomponent shall be a domain name registered to the authoring tool vendor to prevent duplication between tool identifiers provided by different vendors.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-698188317

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

RogerDressler commented 4 years ago

Hi Harold,

I would say yes -- these changes were made. I believe JP and/or you wanted to review other areas of the text before triggering the more formal review, so I was waiting for any feedback before uploading again.

--Roger

On Fri, Oct 2, 2020 at 2:05 PM Harold Hallikainen notifications@github.com wrote:

I do not yet see these changes in the document (new normative references and changing dashes to bullets). Should we complete a review on the assumption these changes will be made?

Thanks!

Harold

@RogerDressler Hi, Roger

Following up on my TODO item from meeting yesterday, here are the normative refs for the 2 IETF RFC documents

IETF RFC 3986, "Uniform Resource Identifier (URI): Generic Syntax", January 2005 (url: https://tools.ietf.org/html/rfc3986 ) IETF RFC 1035, "Domain names - implementation and specification", November 1987 (url: https://tools.ietf.org/html/rfc1035 )

As for formatting, replacing hyphens with bullet points makes them look better, I think. ie.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:

the authority component shall be present;

the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035;

the host subcomponent shall be a domain name registered to the authoring tool vendor to prevent duplication between tool identifiers provided by different vendors.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-698188317

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SMPTE/st2098-2/issues/5#issuecomment-702957345, or unsubscribe https://github.com/notifications/unsubscribe-auth/APZHCZFJCBI5G4H472YLA3DSIY6ARANCNFSM4O65PLOA .

HaroldHallikainen commented 4 years ago

Thanks! I'll review this weekend.

Harold

Hi Harold,

I would say yes -- these changes were made. I believe JP and/or you wanted to review other areas of the text before triggering the more formal review, so I was waiting for any feedback before uploading again.

--Roger

On Fri, Oct 2, 2020 at 2:05 PM Harold Hallikainen notifications@github.com wrote:

I do not yet see these changes in the document (new normative references and changing dashes to bullets). Should we complete a review on the assumption these changes will be made?

Thanks!

Harold

@RogerDressler Hi, Roger

Following up on my TODO item from meeting yesterday, here are the normative refs for the 2 IETF RFC documents

IETF RFC 3986, "Uniform Resource Identifier (URI): Generic Syntax", January 2005 (url: https://tools.ietf.org/html/rfc3986 ) IETF RFC 1035, "Domain names - implementation and specification", November 1987 (url: https://tools.ietf.org/html/rfc1035 )

As for formatting, replacing hyphens with bullet points makes them look better, I think. ie.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:

the authority component shall be present;

the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035;

the host subcomponent shall be a domain name registered to the authoring tool vendor to prevent duplication between tool identifiers provided by different vendors.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-698188317

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

â You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SMPTE/st2098-2/issues/5#issuecomment-702957345, or unsubscribe https://github.com/notifications/unsubscribe-auth/APZHCZFJCBI5G4H472YLA3DSIY6ARANCNFSM4O65PLOA .

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-703000316

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

HaroldHallikainen commented 4 years ago

I'm reviewing the document and want to compare it with issue resolution. Is there a way to get GitHub to show an expanded view of all issues that I can print? I'm able to do that with Bugzilla, but can't figure out how to do it with GitHub.

THANKS!

Harold

Hi Harold,

I would say yes -- these changes were made. I believe JP and/or you wanted to review other areas of the text before triggering the more formal review, so I was waiting for any feedback before uploading again.

--Roger

On Fri, Oct 2, 2020 at 2:05 PM Harold Hallikainen notifications@github.com wrote:

I do not yet see these changes in the document (new normative references and changing dashes to bullets). Should we complete a review on the assumption these changes will be made?

Thanks!

Harold

@RogerDressler Hi, Roger

Following up on my TODO item from meeting yesterday, here are the normative refs for the 2 IETF RFC documents

IETF RFC 3986, "Uniform Resource Identifier (URI): Generic Syntax", January 2005 (url: https://tools.ietf.org/html/rfc3986 ) IETF RFC 1035, "Domain names - implementation and specification", November 1987 (url: https://tools.ietf.org/html/rfc1035 )

As for formatting, replacing hyphens with bullet points makes them look better, I think. ie.

The authoringToolURI shall be a Uniform Resource Identifier as defined by IETF RFC 3986 with the following constraints:

the authority component shall be present;

the host subcomponent shall be a DNS fully qualified domain name as specified in IETF RFC 1035;

the host subcomponent shall be a domain name registered to the authoring tool vendor to prevent duplication between tool identifiers provided by different vendors.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-698188317

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

â You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SMPTE/st2098-2/issues/5#issuecomment-702957345, or unsubscribe https://github.com/notifications/unsubscribe-auth/APZHCZFJCBI5G4H472YLA3DSIY6ARANCNFSM4O65PLOA .

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-703000316

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

mingyan-xperi commented 4 years ago

@HaroldHallikainen No, not sure how to do it, or if that's even possible with GitHub.

HaroldHallikainen commented 4 years ago

Thanks! I really like working with paper. With Bugzilla, I'm able to print out a single document that lists every bug and the discussion about it. I can then mark that up as I review the document.

Meanwhile, I've read through the latest draft and tried to compare that with what's in Github.

Thanks!

Harold

@HaroldHallikainen No, not sure how to do it, or if that's even possible with GitHub.

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/SMPTE/st2098-2/issues/5#issuecomment-703701797

-- FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone.

SMPTE / st2098-2

authoringToolURI constraints #5