Ticket #10 (enhancement)

Opened 3 years ago

Last modified 2 years ago

Don't include templess version in namespace

Status: closed (fixed)

Reported by: oefe Assigned to: somebody
Priority: highest Milestone: 4 - Finalization
Component: component2 Version: 2.0
Severity: major Keywords:
Cc:

Including the templess version in the namespace is probably a bad idea. Each time you increment the version, users will have to change the namespace declarations in all their templates (unless you check for and process templess attributes from all previously used namespaces as well). If you want to know the version of the templess spec against a given template is written, using a t:version attribute might work better.

Change History

02/02/06 01:03:23: Modified by johnny

  • status changed from new to closed.
  • resolution set to fixed.

Great tip, I would say, I sorta adopted the version number from the w3 without thinking about it much, your description makes a lot of sense. For now I've decided not to demand a version string anywhere, btw, since I don't expect the schema to change at all anymore.

I've decided that this would be a good moment to change the host name, too, so the namespace has now become 'http://johnnydebris.net/xmlns/templess'.

Accepted and resolved rightaway... ;)

See changeset [31].

07/03/06 09:18:09: Modified by anonymous

  • severity changed from major to normal.
  • component changed from component1 to component2.
  • priority changed from normal to highest.
  • version set to 2.0.
  • milestone changed from 2 - Cleanup and solidity to 1 - Feature completeness.
  • type changed from defect to enhancement.

07/04/06 09:35:01: Modified by anonymous

  • severity changed from normal to trivial.
  • component changed from component2 to component1.
  • priority changed from highest to low.
  • version changed from 2.0 to 1.0.
  • milestone deleted.
  • type changed from enhancement to task.

07/07/06 21:48:34: Modified by anonymous

  • severity changed from trivial to major.
  • component changed from component1 to component2.
  • priority changed from low to highest.
  • version changed from 1.0 to 2.0.
  • milestone set to 4 - Finalization.
  • type changed from task to enhancement.