ISO-31-1: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
(→‎Issues: A new design pattern?)
Line 18: Line 18:


===Issues===
===Issues===
* Raised By <cite>[http://microformats.org/discuss/mail/microformats-new/2008-August/001668.html Glenn Jones]</cite> on microformats new  
* Raised By <cite>[http://microformats.org/discuss/mail/microformats-new/2008-August/001668.html Glenn Jones]</cite> on microformats new <blockquote>Having different datatypes for a property of the same name is very problematic. Personally I would not like us to use ISO-8601 for hCalendar duration and ISO-31-1 for duration in hAudio. Some parsers do try to convert formats into datatypes this could become hellish if we use the same property names for different data formats.</blockquote>
<blockquote>Having different datatypes for a property of the same name is very
** Solution 1 Change <code>duration</code> to <code>interval</code>. [[User:WebOrganics|Martin McEvoy]] 14:48, 7 Aug 2008 (GMT)
problematic. Personally I would not like us to use ISO-8601 for
** Solution 2 — Keep the name, and allow all properties which take a duration as their value (across all microformats!) to use this pattern. It can become a standard microformats design pattern. [[User:TobyInk|TobyInk]] 12:35, 7 Aug 2008 (PDT)
hCalendar duration and ISO-31-1 for duration in hAudio. Some parsers do
try to convert formats into datatypes this could become hellish if we
use the same property names for different data formats.</blockquote>
*# Solution 1 Change <code>duration</code> to <code>interval</code>. [[User:WebOrganics|Martin McEvoy]] 14:48, 7 Aug 2008 (GMT)

Revision as of 19:35, 7 August 2008

ISO 31-1

This is a page for the study of ISO 31-1 which is the part of the international standard ISO 31 format for durations and intervals as discussed on microformats-new also outlined on datetime-design-pattern.

Sample markup

Proposed as a replacement or optimization of hAudio Duration expressed in ISO-31-1/ISQ format

<span class="duration">
 <span class="h">1</span>:
 <span class="min">3</span>:
 <span class="s">42</span>
</span> 

Issues

  • Raised By Glenn Jones on microformats new

    Having different datatypes for a property of the same name is very problematic. Personally I would not like us to use ISO-8601 for hCalendar duration and ISO-31-1 for duration in hAudio. Some parsers do try to convert formats into datatypes this could become hellish if we use the same property names for different data formats.

    • Solution 1 — Change duration to interval. Martin McEvoy 14:48, 7 Aug 2008 (GMT)
    • Solution 2 — Keep the name, and allow all properties which take a duration as their value (across all microformats!) to use this pattern. It can become a standard microformats design pattern. TobyInk 12:35, 7 Aug 2008 (PDT)