Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

need "isCodeComponent" attribute #8

Closed
reschke opened this issue Jan 24, 2017 · 6 comments
Closed

need "isCodeComponent" attribute #8

reschke opened this issue Jan 24, 2017 · 6 comments

Comments

@reschke
Copy link
Contributor

reschke commented Jan 24, 2017

(from https://tools.ietf.org/tools/xml2rfc/trac/ticket/322)

There should be a way to mark artwork/sourcecode to contain a "code component" in the sense of <​https://www.ietf.org/iesg/statement/copyright.html>, as proposed in <​https://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext-rfc2629.artwork>.

@paulehoffman
Copy link
Contributor

This should be in both <artwork> and <sourcecode>. However, this feature should first be discussed in the places that deal with IPR issues.

@levkowetz
Copy link
Contributor

Letting <artwork/> and <sourcecode/> render without and with <CODE STARTS>, respectively, would have the advantage of being both intuitive and providing an option to avoid the <CODE STARTS> delimiter if explicitly not wanted. If it is imperative to be able to use <sourcecode/> without the delimiter, we could add a flag to disable the rendering of the delimiter instead. Having a flag to enable the delimiter within artwork seems like overdoing things a bit -- I'd prefer to leave artwork without that option, since it seems so intuitive to couple it to <sourcecode/>.

@paulehoffman
Copy link
Contributor

The recent discussion on the list shows that is useful for many things that do not want inserted, and that has certain legal meanings. Thus, I'm going to close this.

@reschke
Copy link
Contributor Author

reschke commented Oct 4, 2018

I don't understand this answer.

@paulehoffman
Copy link
Contributor

That's good, because my answer was wrong. I misunderstood the request here. Reopening, and this issue should come to the list at some point.

@paulehoffman paulehoffman reopened this Oct 4, 2018
@reschke
Copy link
Contributor Author

reschke commented Feb 27, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants