Create new att.source and include att.written and att.placement in it

[sabineseifert]

and also added note to description of att.placement concerning its use.

An 'good' example gently guiding the use of place in e.g. div is still missing.

[ebeshero]

@sabineseifert About this, I was just re-reading our minutes from Buenos Aires. It seems we were going to move the classes att.written and att.placement into a new class called att.source. And we left some guidance about parallel cases to help with this. Take a look (you can find the discussion in the F2F minutes by searching for @place on the posted minutes on the website.)

[sabineseifert]

This PR was tied to #2551 but is now tied to #2550.

What I did:

• created new class att.source -- Please review carefully what might be missing/wrong here. (E.g. is there an xml:id needed in <classSpec>, like xml:id="class-attr-source"?)
• added att.written and att.placement to new att.source (both as discussed at F2F in October 2024)
• added a remark to att.placement as discussed in Council meeting 2024-09-03 (in relation to Allow @place in <div>  #2551)

What I did not:

• not yet added att.source to att.global.rendition (see Allow @place in <div>  #2551)

[sydb]

@sabineseifert — I presume this should currently be considered a DRAFT pull request, yes?

Although you have created att.source, you have not added it to the Guidelines. It needs to be included in the list at #DSTECAT in Source/Guidelines/en/ST-Infrastructure.xml. (Starts on line ~864.) Adding it is trivially easy. Adding it in the right place can sometimes be tricky.

As for @xml:id on <classSpec>, we use it about ½ the time. Will look in a moment at how often we reference it, but I suspect it is very rarely.

Could someone remind me why we are calling this new class “att.source” — seems confusingly close to att.global.source. Maybe att.renditionLike, att.styleLike, att.sourceDetails, att.specificRendition, or some such?

[sydb]

Of the just over 100 @xml:id attributes we have on the over 200 <classSpec>s in the Guidelines source, exactly 0 of them are referenced.

[sabineseifert]

Good idea to mark this as a draft PR which I just did!

I looked at the ST-Infrastructure.xml and must confess that I wouldn't know where to add it. But before, we need to settle the question of the name anyway: att.source.rendition and att.source were proposed at the F2F in October 2024). And: the parallel case model.phrase and model.limitedPhrase might help with naming and defining the new class. But I think we did not finish discussing the name.

And concerning the 0 references to the over 100 @xml:ids: We probably should not keep on going adding these but we perhaps should not delete the already existing ones?

Thanks, @sydb, for looking into this!

[sydb]

I am ducking the name issue for the moment, mostly because I do not really know what to call this thing.

But as for where in ST the <xi:include href="../../Specs/att.WHATEVER.xml"/> goes, it should be inserted somewhere between lines 864 and 929. As for where within that list, the only requirement (IIRC) is that an attribute class which has a <memberOf key="DUCK"> has to be after the <xi:include href="../../Specs/att.DUCK.xml"/>. Thus those includes that refer to classes do NOT have a <memberOf> can go anywhere, and we generally list them alphabetically.

About ½ of our attribute classes are a member of some other class. But of course, an average by accident roughly ½ of those should be in the correct order without intervention. I am working on re-organizing that list and commenting it better, but will not get to check anything in for hours, I am sure.

As for adding @xml:id to <classSpec> — I do not think it matters.