summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2010-04-06 14:05:00 -0400
committerJoey Hess <joey@gnu.kitenet.net>2010-04-06 14:05:00 -0400
commit33d934b5ca1666bfe3f9fa3004ad7d31c38c69c1 (patch)
tree024302148ebe96e862cb9103552ef0342e1f1de7
parentc87ddb6908485fecff9c516223ca0b2973df88f6 (diff)
comment
-rw-r--r--doc/forum/an_alternative_approach_to_structured_data.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/forum/an_alternative_approach_to_structured_data.mdwn b/doc/forum/an_alternative_approach_to_structured_data.mdwn
index 045bfd7aa..06c82337a 100644
--- a/doc/forum/an_alternative_approach_to_structured_data.mdwn
+++ b/doc/forum/an_alternative_approach_to_structured_data.mdwn
@@ -18,6 +18,10 @@ I think it could be really powerful and useful, especially if it becomes part of
> It looks like an interesting idea. I don't have time right now to look at it in depth, but it looks interesting. -- [[Will]]
+> I agree such a separation makes some sense. But note that the discussion on [[todo/structured_page_data]]
+> talks about associating data types with fields for a good reason: It's hard to later develop a good UI for
+> querying or modifying a page's data if all the data has an implicit type "string". --[[Joey]]
+
## Second Pass
I have written additional plugins which integrate with the [[plugins/contrib/field]] plugin to both set and get structured page data.