Project

Profile

Help

Bug #4519

closed

Schema for SCM files does not allow @dmk attribute

Added by Michael Kay almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Schema-Aware processing
Sprint/Milestone:
-
Start date:
2020-04-14
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
10, 9.9
Fix Committed on Branch:
10, 9.9
Fixed in Maintenance Release:
Platforms:

Description

An SCM file compiled with a schema processor under a license file containing a "developer master key" will have an @dmk attribute on the top-level scm:schema element. The schema for SCM does not allow this attribute.

Actions #1

Updated by Michael Kay almost 4 years ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 10, 9.9 added

Fix committed to repo/samples/scm (which is not versioned); the fix will be picked up when the saxon-resources download is rebuilt.

Actions #2

Updated by Debbie Lockett almost 4 years ago

Fix copied to samples/scm under 9.9 and 10 branches.

Actions #3

Updated by O'Neil Delpratt almost 4 years ago

  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.1 added

Bug fix committed in the Saxon 10.1 maintenance release.

Actions #4

Updated by O'Neil Delpratt over 3 years ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 10.2, 9.9.1.8 added
  • Fixed in Maintenance Release deleted (10.1)

Bug fix applied on the Saxon 9.9.1.8 maintenance release.

Please register to edit this issue

Also available in: Atom PDF