[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Metadata Grouping <was: RE: [xliff] 1.2 to 2.0 Gaps and Proposals (metaData)>
At least be polite and wait until I leave the TC in December before asking Bryan for that ballot. I designed current metadata module (XML schema and documentation), not Bryan. Regards, Rodolfo -- From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King Ugly is in the eye of the beholder J. I think the below example is less readable and less structured, and using a <metagroup> is still a relatively simple XML structure. <mda:metadata> <meta type="previous-source" group=”properties”>hello world</meta> <meta type=”boundingbox” group=”screencapture”>20,20,10,15</meta> <meta type=”uri” group=”screencapture”>images\signup\login.jpg</meta> <meta type=”hash-id” group=”screencapture”>tc22457</meta> </mda:metadata> In any case, Bryan, as current owner of <mda:metadata>, do you feel we need to put this to electronic ballot at this point to choose between the three proposed implementations? 1. More than one <mda:metadata> with a name attribute at the extension point 2. One <mda:metadata> at the extension point with a <metagroup> element 3. One <mda:metadata> at the extension point with a group attribute on <meta> Thanks all for the discussion, Ryan From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Rodolfo M. Raya Still ugly. Add a “group” attribute to <meta> and you will be able to do what you want with a much simpler design. Regards, Rodolfo -- From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King We are primarily concerned with being able to group related pieces of metadata, so Fredrick’s alternative methods would give us the same result and allow us to keep one <metadata> at each extension point. We would prefer a more structured approach. How is this for example: <mda:metadata> <metagroup name=”properties”> </metagroup> <metagroup name=”screencapture”> <meta type=”uri”>images\signup\login.jpg</meta> <meta type=”hash-id”>tc22457</meta> </metagroup> Thanks, Ryan From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Estreen, Fredrik Hi Rodolfo, Ryan, I definitely see a value in being able to group the meta data. Both for display and processing purposes. For display it allows more natural names without breaking the ability to easily order / group values relating to each other. For processing it makes it easier to add/remove a set of metadata for a tool or tool feature. It also reduces the risk of name clashes for the key. I’m not convinced allowing multiple <metadata> elements at the same level is the direction to go tough. I can see two other solutions, either grouping the metadata items through a new element inside <metadata> or through an additional attribute on the <meta> element. Both solutions have pros and cons. Personally I prefer the more structured way with grouping by elements, but implementation wise it is probably easier to group by attributes. The later way also solves the issue with users that do not want groups, if the new attribute is optional and any <meta> without it is considered part of an anonymous group. Regards, Fredrik Estreen From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Rodolfo M. Raya Still a bad use case that doesn’t justify ruining a good design. Regards, Rodolfo -- From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King So that our original reason for proposing having more than one <mda:metadata> at the extension point does not get obfuscated in all of the replies and “see inlines”, here once again, is the use case for adding more than one <mda:metadata> per extension: Proposal 4: Add an optional name attribute on <notes> in core and <mds:metadata> module. We believe it will be typical for content providers to want to group their notes or metadata in meaningful ways. This might be done so that a certain number of notes or bits of metadata can be processed in the same way, or simply grouped and displayed together, such as in an editor UI. Here are some examples: <mda:metadata name=”properties”> </mda:metadata> <mda:metadata name=”screencapture”> <meta type=”uri”>images\signup\login.jpg</meta> <meta type=”hash-id”>tc22457</meta> As opposed to something less structured and more difficult to process: <mda:metadata> <meta type=”screencapture-boundingbox”>20,20,10,15</meta> <meta type=”screencapture-uri”>images\signup\login.jpg</meta> <meta type=”screencapture-hash-id”>tc22457</meta> </mda:metadata> Thanks, Ryan From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Rodolfo M. Raya Please do not ruin the design of the metadata module. Only one metadata element is intended to be allowed per extension point. Regards, Rodolfo
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]