Skip to content
Browse files

document metadata field name restrictions

  • Loading branch information...
1 parent bcdbabd commit c5301781e4ce11414242200f5ad04bd89cdc52e6 @xdg xdg committed Jul 14, 2011
Showing with 10 additions and 0 deletions.
  1. +2 −0 Changes
  2. +4 −0 lib/Metabase/Fact.pm
  3. +4 −0 lib/Metabase/Resource.pm
View
2 Changes
@@ -2,6 +2,8 @@ Revision history for Metabase-Fact
{{$NEXT}}
+ - Document limitations on content and resource metadata field names
+
0.019 2010-10-11 00:02:19 EST5EDT
- Fix failing t/profile.t for CPAN build paths with spaces (RT#59580)
View
4 lib/Metabase/Fact.pm
@@ -741,6 +741,10 @@ Here is a hypothetical example of C<content_metadata> for an image fact:
}
}
+Field names should be valid perl identifiers, consisting of alphanumeric
+characters or underscores. Hyphens and periods are allowed, but are not
+recommended.
+
=head2 content_metadata_types
B<optional>
View
4 lib/Metabase/Resource.pm
@@ -235,6 +235,10 @@ resource like 'metabase:user:ec2726a4-070c-11df-a2e0-0018f34ec37c':
}
}
+Field names should be valid perl identifiers, consisting of alphanumeric
+characters or underscores. Hyphens and periods are allowed, but are not
+recommended.
+
=head2 metadata_types
my $typemap = $resource->metadata_types;

0 comments on commit c530178

Please sign in to comment.
Something went wrong with that request. Please try again.