cc-devel AT lists.ibiblio.org
Subject: Developer discussion for Creative Commons technology and tools
List archive
Re: [cc-devel] Legal code and technical implementation: your input wanted
- From: "yangzi2008"<yangzi2008 AT 163.com>
- To: "Mike Linksvayer"<ml AT gondwanaland.com>, "Kat Walsh"<kat AT creativecommons.org>
- Cc: "cc-devel AT lists.ibiblio.org" <cc-devel AT lists.ibiblio.org>
- Subject: Re: [cc-devel] Legal code and technical implementation: your input wanted
- Date: Fri, 19 Apr 2013 00:35:34 +0800
2013-04-19
发件人:Mike Linksvayer
<ml AT gondwanaland.com>
发送时间:2013-04-19 00:32
主题:Re: [cc-devel] Legal code and
technical implementation: your input wanted
收件人:"Kat
Walsh"<kat AT creativecommons.org>
抄送:"cc-devel AT lists.ibiblio.org"<cc-devel AT lists.ibiblio.org>
On Wed, Apr 17, 2013 at 3:57 PM, Kat Walsh <kat AT creativecommons.org> wrote:
> If we were to do this, the legal code would be maintained in a separate file
> from the HTML, in a format that maintained all of the essential information.
> For example, formatting such as bold or italic text that has legal
> significance, section headings, etc., would all be considered essential and
> part of the legal code itself. This legal code file would likely be
> maintained using Markdown[1], or something similar to it.
>
> The web page with the licenses would be generated from this legal code file,
> by converting it to HTML and adding non-legal code formatting, text, and
> navigational elements. However, since the legal code file would not have to
> be touched, it would be impossible to accidentally make a change to the
> legal code itself by changing other elements of the page.
I may have suggested something like this long ago, but I'd probably
stick to HTML as the canonical version now. That canonical HTML should
be as minimal as possible, just including enough structure and
annotation to make it possible for external CSS and _javascript_ to make
look pretty and dynamically add further annotation in a variety of
contexts, and for plain text to be generated without manual post
processing.
Mike
_______________________________________________
cc-devel mailing list
cc-devel AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/cc-devel |
-
Re: [cc-devel] Legal code and technical implementation: your input wanted
, (continued)
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Dan Mills, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Maarten Zeinstra, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Maarten Zeinstra, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Dan Mills, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Dan Mills, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Maarten Zeinstra, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Dan Mills, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Diane Peters, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Maarten Zeinstra, 04/22/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, yangzi2008, 04/18/2013
-
Re: [cc-devel] Legal code and technical implementation: your input wanted,
Nathan Yergler, 04/18/2013
-
Re: [cc-devel] Legal code and technical implementation: your input wanted,
Dan Mills, 04/18/2013
-
Re: [cc-devel] Legal code and technical implementation: your input wanted,
Maarten Zeinstra, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Dan Mills, 04/18/2013
- Re: [cc-devel] Legal code and technical implementation: your input wanted, Nathan Yergler, 04/18/2013
-
Re: [cc-devel] Legal code and technical implementation: your input wanted,
Maarten Zeinstra, 04/18/2013
-
Re: [cc-devel] Legal code and technical implementation: your input wanted,
Dan Mills, 04/18/2013
Archive powered by MHonArc 2.6.24.