Section title and contents mismatch on "Complex Language Markup"

[shigeya]

The current discussion in 10.2 Complex Language Markup is discouraging to use of markup languages capable of containing executable scripts for complex language markup and not providing advice on how to markup.

If the language we need is security considerations, this section should be moved to the appropriate section to discourage this type of markup language.

If the description we need is how to implement complex language markup, we need to provide actual advice on how.

[iherman]

The issue was discussed in a meeting on 2023-08-23

• no resolutions were taken

View the transcript

3.1. Section title and contents mismatch on "Complex Language Markup" (issue vc-data-model#1254)

See github issue vc-data-model#1254.

Sebastian Crane: Is this considered important enough to be its own bullet point in security considerations or is it best practice to just know it?

Manu Sporny: I would suggest 'Post-CR' for this issue. I don't think we should add normative text to the specification about this issue.

Sebastian Crane: I would like to agree with Manu and have the extra justification for post-PR is that this can be said about anything in RDF; we can put any content anywhere and it's up to implementers to be careful in what they pass in what security context they want to.

[iherman]

The issue was discussed in a meeting on 2023-09-06

• no resolutions were taken

View the transcript

4.1. Section title and contents mismatch on "Complex Language Markup" (issue vc-data-model#1254)

See github issue vc-data-model#1254.

Sebastian Crane: this one is going well and almost done, maybe today, will move on to the other issue assigned to me soon.

Manu Sporny: my one thought on 1254 is that internationalization guidance (w3c-wide) is being updated lately, and i don't know if you want that in your PR or in a separate one.

Sebastian Crane: actually I think the PR was only mentioning @language in reference to security of LD documents.

Manu Sporny: Great, that sounds like it's not an issue then, Sebastian! :).

Sebastian Crane: so not related I don't think.

[seabass-labrax]

I'm going to be pretty occupied from now until Easter with other open source projects, so unfortunately it might be a little while before I can get to this issue. If someone else would like to take this that would be great, and I can provide a review :)

[iherman]

The issue was discussed in a meeting on 2024-02-21

• no resolutions were taken

View the transcript

4.1. Section title and contents mismatch on "Complex Language Markup" (issue vc-data-model#1254)

See github issue vc-data-model#1254.

Manu Sporny: This text is in the internationalization write-up.
… I think it's fine where it is.

Ivan Herman: +1 to manu.

Manu Sporny: It doesn't need to be in the Security Considerations.
… I think we should mark the issue pending close.

Brent Zundel: Any objections to that?
… No objections.

[shigeya]

I read the document through yesterday (I will provide some minor feedback later). On the read yesterday, I was puzzled by the title "Complex language markup." (Note: I think JSON-LD language markup is already complex)

Now, I think it is unnecessary to move the security consideration section (since it's already in the internationalization section), but I want the title to be adjusted to something like "Multilingual string with HTML processor," to reflect the actual discussion in the section.

[iherman]

The issue was discussed in a meeting on 2024-03-06

• no resolutions were taken

View the transcript

2.4. Section title and contents mismatch on "Complex Language Markup" (issue vc-data-model#1254)

See github issue vc-data-model#1254.

Brent Zundel: 1254 is about complex language markup.
… this was pending close.
… we got a comment that if the title is adjusted, that would better apply or reflect the content.
… sounds like a simple change.

Manu Sporny: I'll take it.
… and just try to work with title, since Sebastian's no longer with us.
… I'll provide a PR and we can talk about it there.

[iherman]

The issue was discussed in a meeting on 2024-03-13

• no resolutions were taken

View the transcript

4.1. Section title and contents mismatch on "Complex Language Markup" (issue vc-data-model#1254)

See github issue vc-data-model#1254.

Manu Sporny: I'll continue to work on this.

[msporny]

PR #1463 has been raised to address this issue. This issue will be closed once PR #1463 has been merged.

[iherman]

The issue was discussed in a meeting on 2024-03-27

• no resolutions were taken

View the transcript

3.4. Section title and contents mismatch on "Complex Language Markup" (issue vc-data-model#1254)

See github issue vc-data-model#1254.

See github pull request vc-data-model#1463.

Brent Zundel: this PR can be merged by the end of this week.

[brentzundel]

PR #1463 has been merged, closing this issue as is has been addressed.