Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#441 fDecl doesn't allow att.datcat yet

GREEN
open-accepted
Piotr Banski
5(default)
2013-10-10
2012-09-20
Menzo Windhouwer
No

TEI P5 2.1.0 says at the end of section 18.3

"Whether at the level of feature-system declarations, feature- and feature-value libraries, or individual features, it is possible to align both feature names and their values with standardized external data category repositories such as ISOcat."

However, a feature declaration can not be associated with an ISOcat data category using @dcr:datcat yet, i.e., <fDecl> [1] doesn't yet include the att.datcat [2] attribute set which <f> [3] already does.

If <fDecl> would allow @dcr:datcat it becomes possible to declare all relationships with ISOcat data categories in a feature system declaration instead of doing so highly redundant in each feature instantiation.

[1] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fDecl.html
[2] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datcat.html
[3] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-f.html

Related

Bugs: #441

Discussion

<< < 1 2 3 4 (Page 4 of 4)
  • Piotr Banski
    Piotr Banski
    2013-09-06

    Your solution (d) seems the cleanest on the assumption that we want to continue mentioning selected attributes from other namespaces explicitly within the documentation.

    Let's talk about point (b) in the action items. We want fsDecl, fdecl, symbol and numeric there, I guess -- what else?

    (edit: I feel lost switching between straightforward datatyping and external semantics... string, binary, numeric -- do we want these? maybe at least experimentally? this is primarily a question to Menzo, I think)

     
    Last edit: Piotr Banski 2013-09-06
  • Laurent Romary
    Laurent Romary
    2013-09-06

    elementSpec, equiv, valDef, attDef

     
  • As in the FS instance @dcr:datcat or @dcr:valueDatcat is allowed on a <binary> and <string> as well, I would also allow @dcr:targetDatcat or @dcr:targetValueDatcat on them in the FSD.

     
  • Piotr Banski
    Piotr Banski
    2013-09-06

    Laurent says, "elementSpec, equiv, valDef, attDef". This is a bit a jump from the direct focus here, but I can understand the principle behind it. Except that we should probably divide this into {elementSpec, valDef, attDef} on one side, as the defining elements, and {equiv} on the other, as the referencing element that does a somewhat alternative job to the dcr:target* attributes.

    SO, again, to reference Lou's item "(b) someone to specify the elements which should be members of that class":

    • fsDecl, fDecl, symbol, string, binary, numeric
    • elementSpec, valDef, attDef

    Are we getting there?

     
  • Hi, All,

    Version 1.2 of the DC Reference schema is now available in HTML, RNG and RNC at isocat.org. This revision provides the targetDatcat and targetValueDatcat attributes (and elements).

    Best,

    Menzo

     
  • Piotr Banski
    Piotr Banski
    2013-10-10

    • labels: TEI: Definition of Elements/Attributes/Classes --> TEI: Definition of Elements/Attributes/Classes, LingSIG
    • Priority: 5 --> 1(low)
     
  • Hi Piotr,

    What does it mean that priority is lowered to 1? Will this feature be delayed (forever)? Is there anyway I can assist to get this implemented on the TEI side?

    Best,

    Menzo

     
    Last edit: Menzo Windhouwer 2013-10-10
  • Piotr Banski
    Piotr Banski
    2013-10-10

    • Priority: 1(low) --> 5(default)
     
  • Piotr Banski
    Piotr Banski
    2013-10-10

    Resetting the priority back to 5 -- for some reason, when you edit a ticket, the priority magically drops to the minimum unless you manually set it back to "5". I suspect a bug in the ticketing system. Thanks to Menzo for the catch (fortunately, I only modified some three tickets today!)

     
<< < 1 2 3 4 (Page 4 of 4)